Co-managed IT is an arrangement where your internal IT person or team keeps ownership of your technology and a managed service provider (MSP) adds the coverage, tools and specialist skills they cannot supply alone. Your team stays the authority on your business systems and priorities. The MSP takes on defined, repeatable work such as help desk overflow, patching, monitoring, backups and after-hours coverage. A written responsibility matrix says exactly who does what.
It is the most common arrangement we run in our managed IT services, because most growing companies already have someone in IT who knows the business well but cannot be on call every night, an expert in every system and on vacation at the same time. This guide covers what usually moves to the MSP, what stays in-house, how to share tools and admin access safely, how escalation works, and how to scope and contract it.
Key takeaways
- Co-managed IT extends your IT team rather than replacing it. Your team keeps ownership of priorities, business applications and risk decisions.
- Put a responsibility (RACI-style) matrix in writing at onboarding. Problems tend to start where a task has no owner.
- Give the MSP named, MFA-protected accounts limited to the systems it manages. Do not add MSP accounts to your internal administrator groups.
- Use one ticketing system and one documentation set so both teams see the same history.
- Scope the contract around coverage hours, priority definitions, response targets, change approval and exit terms, not just a list of tools.
What co-managed IT is, and what it is not
In a fully managed arrangement, the provider acts as your entire IT function. In a project engagement, it delivers one defined piece of work and leaves. Co-managed sits between them: an ongoing partnership where both teams work in the same environment every day, with the split of duties agreed in advance.
Co-managed IT is not a staffing agency placing a contractor under your IT manager, and it is not a vendor you call only when something breaks. The MSP brings its own processes, tooling and bench of technicians. Your internal team directs priorities and handles work that depends on knowing the business, such as the quirks of your ERP, the shop floor schedule or which executive needs white-glove support.
Signs you need co-managed IT
- Your IT person is the only one who knows how things work, and nobody covers when they are sick or on vacation.
- Tickets pile up during busy periods and strategic projects keep slipping.
- Nobody watches security alerts at night or on weekends.
- Patching, backup checks and restore testing happen when there is time, which means rarely.
- A cyber insurance application or customer security questionnaire asked about controls you cannot show evidence for.
- You are adding a new office, migrating to the cloud or rolling out new devices, and the internal team cannot do that and run daily support at once.
- Your IT lead spends more time on password resets than on planning.
Who does what: a sample responsibility matrix
A RACI matrix lists each task and marks who is Responsible (does the work), Accountable (owns the outcome and signs off), Consulted (gives input before) and Informed (told after). The split below is a common starting point, not a rule. Every company adjusts it to its own team.
| Task | Internal IT | MSP | Business leadership |
|---|---|---|---|
| Tier 1 help desk (password resets, how-to questions, routine requests) | A | R | I |
| Line-of-business application support (ERP, CRM, industry software) | R, A | C | I |
| Operating system and third-party patching | A | R | I |
| Endpoint and mobile device management policies | A | R | I |
| 24/7 monitoring and alert triage | I | R, A | I |
| Backups and documented restore testing | A | R | I |
| Network and firewall changes | A | R | I |
| New hire and departing employee account changes | A | R | C (HR request) |
| Vendor, carrier and license management | R, A | C | I |
| Security policies and risk acceptance | R | C | A |
| IT budget and roadmap | R | C | A |
| Documentation and asset inventory | A | R | I |
Two rules keep the matrix useful. Every task gets exactly one “A,” and the matrix is reviewed whenever your team, your systems or the contract change. If you have no one in-house to own security policy, a virtual CISO can fill that seat alongside the co-managed team.
Shared tools and admin access rules
Co-managed IT means two teams hold privileged access to the same systems. That is useful and also risky, because attackers target managed service providers to reach their customers. A 2022 joint advisory from US, UK, Australian, Canadian and New Zealand cyber agencies sets out practical controls for MSP customers. Several of them translate directly into co-managed access rules:
- Named accounts with MFA. Every MSP technician uses an individual account protected by multi-factor authentication. No shared logins between teams.
- Least privilege. MSP accounts reach only the systems the MSP manages. The advisory says customers should ensure MSP accounts are not assigned to internal administrator groups.
- Time-limited elevation. Where possible, admin rights are granted for a task and expire, instead of standing all the time.
- Logging. Admin activity by both teams is logged. The advisory recommends storing your most important logs for at least six months.
- Account removal at contract end. The advisory warns that disabling MSP accounts can be overlooked when a contract terminates. Put removal steps in the exit plan.
- Agreed tool ownership. Decide who licenses and owns each tool (remote management, endpoint security, backup, documentation). If the MSP owns a tool, make sure your team keeps read access and gets the data back at exit.
- One ticket system, one documentation set. Both teams log work in the same place, so nothing is fixed twice or lost between systems.
Escalation that works in both directions
In co-managed IT, escalation runs both ways. The MSP escalates to your team when an issue touches a business system or needs a decision. Your team escalates to the MSP when it needs specialist depth, extra hands or after-hours coverage.
- Define priorities once. Use one set of priority levels (for example, critical, high, normal, low) with plain examples for each, shared by both teams.
- Name contacts and backups. List who the MSP calls on your side for each type of issue, including after hours, and who your team calls at the MSP.
- Set decision rights. Write down what the MSP may do on its own (restart a service, isolate an infected laptop) and what needs approval (taking a server offline during business hours).
- Agree on handoffs. When a ticket moves between teams, the ticket says why, what was tried and who owns it now.
- Review monthly. Look at escalations, missed targets and recurring issues, and adjust the matrix.
How to scope and contract co-managed IT
A co-managed agreement should describe the working relationship, not just the tools. Use this checklist when you scope it:
- A current inventory of users, devices, servers, cloud services and locations.
- The responsibility matrix attached to the contract.
- Coverage hours: business hours, a hybrid with continuous monitoring, or 24/7/365.
- Priority definitions and target response times for each level, written into the agreement.
- Change management: who approves changes, maintenance windows and how emergencies are handled.
- Access rules: named accounts, MFA, least privilege and logging, as described above.
- Security duties: who monitors alerts, who responds to incidents and whether incident response is included or separate.
- Reporting: what you receive each month, such as ticket trends, patch status and backup results.
- Project work: how work outside the regular scope is quoted and approved.
- Exit terms: return of documentation, credentials and data, and removal of MSP access.
Some industries have rules about overseeing providers. For example, the FTC Safeguards Rule requires covered financial institutions to select service providers capable of maintaining appropriate safeguards, require those safeguards by contract and periodically assess them (16 CFR 314.4(f)). This is general information, not legal advice. Confirm the rules for your industry with counsel.
Common mistakes to avoid
- Vague scope. “MSP handles security” means different things to each side. Name the tasks.
- Two ticket systems. Work done in one is invisible to the other, and problems repeat.
- Treating the MSP as overflow only. If the MSP only gets the tickets nobody wants, you lose the value of its monitoring and automation.
- No exit plan. Without one, tools, documentation and access can be hard to untangle later.
- Never revisiting the matrix. Teams change, and an outdated matrix is worse than none.
For a broader look at how managed IT and security fit together for smaller companies, see our post on managed IT support and small business security.
How Honeybadger Solutions helps
Co-managed is the most common arrangement we run in our managed IT services. We extend your internal team with tools, coverage and specialist depth, under a responsibility matrix written down at onboarding. Onboarding runs in five phases (discover, assess, deploy, stabilize and optimize), with named owners at each phase. You choose business-hours (8/5) coverage, a hybrid of continuous monitoring with a business-hours service desk, or a 24/7/365 staffed operation, and the team, tools and processes stay the same.
The work can include a staffed IT help desk, Microsoft 365 and Google Workspace administration, endpoint and mobile device management, network management, identity and access, managed backup with documented restore testing, and governance, risk and compliance support. We are vendor-neutral, and the work is delivered remotely by our own team for clients across the US and internationally. Response targets and reporting are written into your service agreement, and quotes are written and given before any work starts. To add co-managed support to your IT team, request co-managed IT online.
Frequently asked questions
What is the difference between co-managed IT and fully managed IT?
With fully managed IT, the provider acts as your entire IT and security function. With co-managed IT, your internal team keeps ownership and directs priorities, and the provider takes defined tasks under a written responsibility matrix.
Will co-managed IT replace our IT staff?
No. The point is to extend your team, not replace it. Your staff keep the work that depends on knowing the business, and the provider takes repeatable work, monitoring and after-hours coverage so your team has time for projects.
Who owns the tools in a co-managed arrangement?
That is agreed in the contract. Some tools belong to you and some to the provider. Whatever the split, make sure your team has access to the data and documentation and gets it back if the contract ends.
How should we give an MSP admin access safely?
Use named accounts with MFA for each technician, limit access to the systems the MSP manages, keep MSP accounts out of your internal administrator groups and log all admin activity. Remove access promptly when a technician leaves or the contract ends.
How long does it take to set up co-managed IT?
It depends on the size and complexity of your environment. Expect a discovery and assessment period before tools are deployed, then a stabilization period while both teams settle into the matrix and escalation paths.
Sources: Joint advisory AA22-131A, Protecting Against Cyber Threats to MSPs and their Customers (CISA, NSA, FBI, NCSC-UK, ACSC, CCCS, NCSC-NZ, 2022), eCFR, 16 CFR 314.4 (FTC Safeguards Rule elements)
