Adding a managed service provider to an internal IT team sounds simple until someone asks who actually owns the patching schedule. Co-managed IT services are a customized service model that combines the convenience of internal IT with the expertise of an MSP, and the customization is the whole point. The provider does not take over your department, and your team does not quietly become a group of ticket reviewers. You decide which responsibilities stay inside and which leave the building, then you write that decision down.
That written decision is where most co-managed relationships succeed or fall apart. This guide covers how to define the split, which work belongs where, and how to keep handoffs from becoming the place where important tasks disappear.
What co-managed IT services mean in practice
Co-managed IT is an IT management service model that lets businesses and administrators customize which IT services to keep in-house and which to hand to a provider. That is different from fully outsourced IT, where the MSP handles the entire operation and your internal staff, if any, mostly coordinate vendors.
Providers on the co-managed side typically offer a broad menu of services, letting each organization pick and choose based on its own requirements. A three-person IT department drowning in password resets can buy help desk coverage. A lean team with compliance deadlines can buy security monitoring and audit support while keeping day-to-day systems work internal. A single IT manager at a growing company can keep architecture decisions and buy after-hours coverage, patching at scale, and specialist depth.
The consistent thread is shared workload. Co-managed services exist to relieve pressure on internal teams so those teams can spend more time on strategic work, which is usually what they were hired to do in the first place.
The split should follow ownership, not preference
Teams tend to divide work by what feels comfortable. The internal staff keeps everything they already know how to do, and the MSP gets everything nobody enjoys. That arrangement feels natural on day one and creates gaps by month three. A better approach is to sort work by who can be accountable for the outcome, not who finds the task interesting.
Work that usually belongs inside
Internal staff hold context that no provider can replicate quickly: how the business actually operates, which systems support revenue, which department will complain loudest, and why a particular process exists. Keep the following inside where capacity allows:
- Business relationship work, including sitting with department heads to understand priorities and pain points
- Line-of-business application decisions and vendor relationships tied to a specific operational workflow
- Day-to-day user support when the internal team has the bandwidth and proximity to handle it well
- Architecture and roadmap input, particularly where the business strategy is still forming
Work that usually belongs with the provider
Other responsibilities reward depth, scale, and round-the-clock coverage. An internal team of two or three people cannot reasonably staff a night shift or maintain current expertise across every security tool in the stack. Providers commonly back up internal teams with after-hours coverage, specialist depth, patching at scale, and 24×7 security monitoring. Consider handing over:
- After-hours and weekend coverage, so incidents do not wait for Monday morning
- Patching and update management across a large device fleet
- Specialist security operations, including monitoring, threat detection, and response
- Vulnerability scanning and the reporting that follows it
- Backup and disaster recovery monitoring with someone watching the alerts
- Compliance evidence collection for frameworks your organization is held to

A responsibility matrix you can actually use
The table below is a starting point, not a verdict. Adjust each row to match your team’s capacity, then confirm the final version with your provider in writing. Where a row has two owners, name a single accountable party anyway, because shared accountability without a named lead is how tasks go quiet.
| Workstream | Common internal role | Common provider role | Failure risk if unclear |
|---|---|---|---|
| Help desk tiers | Handles business-critical and executive requests, triages context | Front-line ticket volume, after-hours queue | Users submit twice or wait for a team that assumed the ticket was already handled |
| Device and server management | Approves changes, owns standards | Executes patching, monitoring, and maintenance windows | Patches get deferred indefinitely on both sides |
| Microsoft 365 administration | Sets policy and licensing direction | Day-to-day administration and configuration hardening | Configurations drift away from policy |
| Backup and disaster recovery | Defines recovery priorities for business systems | Monitors jobs, tests restores, reports results | Backups run but restores are never tested |
| Security monitoring | Receives escalations, makes business decisions on containment | Continuous monitoring, alert triage, response support | Alerts route to a mailbox nobody watches |
| Vulnerability management | Prioritizes remediation against business impact | Scans, reports, tracks remediation progress | Scan reports pile up with no owner for fixes |
| Compliance and audit | Owns the control narrative and approves evidence | Provides evidence, documentation, and control operation support | Evidence requests arrive late and incomplete |
| Procurement | Approves budget and vendor relationships | Quotes, orders, and tracks hardware and licensing | Duplicate purchases and unmanaged assets |
How to decide where the line sits
For each workstream, ask a small set of questions. The answers point to an owner faster than a debate over job descriptions.
- Can this be done during business hours only, or does it need coverage overnight and on weekends?
- Does it require knowledge of how your business earns money, or knowledge of a technical system?
- How quickly does the skill go stale? Fast-moving security tooling rewards a specialist.
- If this task is missed for a week, who notices first and what breaks?
- Who can produce documentation or evidence if an auditor asks?
Answer those five questions for patching, for security monitoring, and for user support, and the pattern becomes obvious. Coverage and depth tend to leave the building. Context and judgment tend to stay.
Where handoffs break, and how to prevent it
Most co-managed friction is not caused by bad service. It is caused by boundaries that were never operationalized. Three fixes prevent most of it.
One ticket system, one source of truth
If your internal team tracks work in one tool and the provider tracks work in another, nobody can see the full history of a problem. Agree on where tickets live, how they get routed between teams, and who closes them. A user should never have to explain the same issue twice because two systems disagreed.
Named escalation paths
Write down who the provider calls at 2 a.m. and who your team calls when a vendor response stalls. A named person on each side, with a backup, turns an ambiguous handoff into a phone call.
Change approval that does not add days
Providers make changes on your systems, so someone internal needs to approve anything material. Keep the approval list short and pre-approved categories broad, or routine maintenance will stall behind a weekly meeting.

Build a simple operating rhythm
Co-managed relationships drift when nobody reviews them. A light cadence keeps the split honest without adding meetings for the sake of meetings.
- Weekly: review open tickets crossing both teams, outstanding escalations, and anything waiting on approval
- Monthly: review service performance, patching completion, security alerts, and backup results
- Quarterly: revisit the responsibility matrix against actual capacity and business changes
- Annually: test recovery, review compliance evidence, and update the plan
The quarterly review matters most. Teams grow, projects end, and a split that fit last year may no longer match staffing or risk. Adjusting the matrix before a problem appears is far easier than renegotiating after an outage.
Match the split to your starting point
Different internal teams need different versions of co-management, and the same organization may need a different version two years from now.
A small business with no dedicated IT staff
There is often a single person who handles technology alongside another job. In that scenario the provider carries nearly everything operational, while the internal contact keeps vendor relationships and budget authority. This sits close to fully managed, with a knowledgeable internal point of contact who understands the business.
A team of two to five
This is the classic co-managed profile. Internal staff keep user support, business systems, and architecture, while the provider absorbs after-hours coverage, patching at scale, security monitoring, and specialist depth. The internal team becomes the translator between business needs and technical execution.
A mature team facing compliance pressure
Here the internal team may keep nearly all operations and bring in a provider for security operations, audit evidence, and specialist work such as virtual CISO support. The value is depth and independent verification, not headcount relief.

Write the split into the agreement
A responsibility matrix is only useful if the contract reflects it. Confirm that the service agreement names which party performs each workstream, what response times apply, who owns documentation and credentials, how disputes get escalated, and what happens to data and accounts if the relationship ends. Also confirm whether compliance support is included or billed separately, since audit season is the wrong time to discover a gap in scope.
Get the final split reviewed by both the provider’s delivery lead and your own team before the contract is signed. The people doing the work will spot overlaps that a sales conversation missed.
Co-managed IT services work best when the division of labor is deliberate, documented, and reviewed on a schedule. Define ownership by coverage, depth, and business context, name one accountable party per workstream, and revisit the arrangement as your team changes. The model gives you flexibility, but only if you use it intentionally.
Frequently Asked Questions
How is co-managed IT different from fully managed IT?
Co-managed IT services partner your internal IT team with an MSP to share responsibilities, while fully outsourced IT means the MSP handles the entire operation. In a co-managed arrangement you choose which services stay in-house and which move to the provider, and you keep internal staff who understand the business context.
Can we start small and expand the scope later?
Yes. Co-managed providers typically offer a broad menu of services, letting organizations pick and choose based on individual requirements. Many begin with a single gap such as after-hours coverage or security monitoring, then expand once the handoffs and escalation paths are proven in practice.
Should our internal team keep the help desk?
Keep it if the team has the bandwidth and proximity to respond well, and route volume or after-hours tickets to the provider. What matters is that users know where to submit requests and that both teams can see the same ticket history, so nothing gets handled twice or dropped.
Who owns security in a co-managed model?
Ownership stays with your organization, while the provider operates much of the work. A common split gives the MSP continuous monitoring, alert triage, vulnerability scanning, and response support, while internal staff make containment decisions, prioritize remediation against business impact, and approve policy changes.
How often should we review the arrangement?
Review open cross-team tickets weekly, service performance and backup results monthly, and the full responsibility matrix quarterly. The quarterly pass is where you catch a split that no longer matches your staffing, your project load, or your compliance obligations before it turns into an incident.