IT Management

What Is Co-Managed IT? A Practical Guide for Firms With Internal IT Staff

What is co-managed IT? A plain guide to splitting work between internal IT staff and an MSP: who owns what, shared tools, when it works, pitfalls and setup.

By Boston IT Services Group · Published November 14, 2026 · Updated November 14, 2026 · 8 min read

In short

Co-managed IT is an arrangement where a business keeps its own IT staff and brings in a managed service provider to share the work, usually by supplying tools, security operations, after-hours coverage, specialist skills or project capacity. The two sides agree in writing who owns each task. This guide explains common responsibility splits, how tools like RMM, PSA and documentation are shared, when the model works, and the pitfalls to avoid.

What is co-managed IT? It is an arrangement where your business keeps its own IT staff and hires a managed service provider (MSP) to share the work. The provider typically supplies monitoring and security tools, overflow and after-hours help desk, specialist engineers or project capacity, while your internal team keeps the areas it knows best. Both sides agree in writing who owns each task.

This guide is for owners deciding whether co-managed IT services make sense, and for internal IT staff who want to know what they would be signing up for. We will cover how responsibilities usually split, how tools get shared, when the model works and where it goes wrong.

What is co-managed IT used for? Why firms choose the model

In our view, co-managed IT fits best in firms of roughly 40 to 200 people that have one to three IT staff. Those people are usually good at their jobs and badly overloaded. Common triggers:

  • The IT manager spends all day on password resets and printer tickets, so projects and security work never happen.
  • The firm needs security operations (24/7 alert monitoring, vulnerability management) that a small team cannot staff.
  • A compliance requirement, cyber insurance renewal or client audit asks for controls and evidence the team cannot produce alone.
  • A big project, like a Microsoft 365 tenant migration, a new office or a firewall replacement, needs more hands for a few months.
  • The firm is worried about what happens when its one IT person goes on vacation, or leaves.

The co-managed IT model addresses all of these without asking the firm to give up internal staff who know its people, software and history.

Co-managed IT vs fully managed

Fully managed IT Co-managed IT
Internal IT staff Usually none One or more, retained
Provider's scope Everything in the agreed service Only what is assigned to it
Day-to-day user relationship Provider's help desk Often internal staff, with provider backup
Tools Provider's stack Usually provider's stack, shared with internal staff
Setup effort Moderate Higher, because responsibilities and access must be split
Best for Firms without IT staff Firms with IT staff who need tools, depth or coverage

If you are still deciding whether to have internal IT at all, start with our comparison of managed IT vs break fix vs in-house.

Common co-managed IT responsibilities: a sample split

The single most useful document in a co-managed relationship is a responsibility matrix. Many teams use a RACI format: Responsible (does the work), Accountable (owns the outcome and signs off), Consulted, Informed. Below is a common starting point. Yours will differ, and that is the point of writing it down.

Area Internal IT MSP
Tier 1 help desk during business hours R, A C (overflow)
After-hours and weekend help desk I R
Onsite user support and hardware swaps R, A C
Line-of-business applications R, A C
User onboarding and offboarding R, A R (account tasks via ticket)
Patching of workstations and servers A, C R
Monitoring and alerting (RMM) I R
Endpoint detection and response alerts I R
Backup monitoring and restore tests A R
Firewall, switch and WiFi configuration C R
Microsoft 365 security configuration A R
Vendor management (ISP, copier, software vendors) R, A C
IT budget and roadmap R, A C
Security policies and compliance evidence A R
Major projects A R

A few patterns show up in most firms. Internal staff keep the people-facing work and the business knowledge. The provider takes the work that needs tools, round-the-clock staffing or deep specialty. Internal IT, or an executive above it, stays accountable for decisions that affect the business, like the budget and which risks to accept.

Sharing tools: RMM, PSA and documentation

Tool sharing is where co-managed arrangements succeed or fail, so get specific.

RMM (remote monitoring and management) is the agent on every device that reports health, deploys patches and allows remote access. In most co-managed setups the provider supplies the RMM and gives internal staff their own named accounts with appropriate permissions. Avoid running two RMM agents on the same machines; they fight over patching and remote control.

PSA (professional services automation) is the ticketing system. Decide early whether internal staff work tickets in the provider's PSA, or whether the two systems integrate. One queue with clear assignment beats two queues and an email chain.

Documentation covers network diagrams, passwords, configurations, vendor contacts and procedures. Put it in one shared platform that both teams use. Write into the contract that the documentation belongs to you and that you can export it at any time.

Security tools (EDR, email filtering, SIEM or log monitoring) are usually provided and operated by the MSP, with internal staff given visibility into alerts and reports.

Security rules for shared access

A co-managed setup gives an outside company privileged access to your systems. Treat that seriously. The joint advisory Protecting Against Cyber Threats to Managed Service Providers and their Customers, published May 11, 2022 by CISA, NSA, the FBI and cybersecurity agencies in the UK, Australia, Canada and New Zealand, recommends that MSP customers, among other things:

  • require multi-factor authentication on all MSP accounts that access their environment
  • apply least privilege, so MSP accounts reach only the systems the MSP manages
  • keep MSP accounts out of internal administrator groups, audit their use, and disable them when not in use or when a contract ends
  • make sure contracts spell out who owns hardening, detection and incident response
  • understand exactly which security services the MSP provides and how and when it will notify them of incidents

The advisory also says MSPs should retain their most important logs for at least six months and should not reuse admin credentials across customers. CISA's separate Risk Considerations for Managed Service Provider Customers is worth handing to whoever negotiates the contract.

In a co-managed environment this has a practical implication: every person on both teams gets a named account. No shared "msp-admin" login. When someone leaves either team, their access goes the same day.

When co-managed IT works well

  • Internal IT staff want the help and helped choose the provider. If the IT manager sees the MSP as a threat, the arrangement will be miserable for everyone.
  • Responsibilities are written down and reviewed at least quarterly.
  • Both teams use the same ticketing queue or a working integration, and the same documentation.
  • There is one escalation path for outages and security incidents, rehearsed in advance.
  • Leadership judges the arrangement on outcomes such as patch compliance, backup success, ticket times and project delivery, with cost as one input among several.

Common pitfalls

Gray areas. "The MSP handles security" means nothing. Does that include reviewing sign-in alerts at 2 a.m.? Responding to a phishing report? Rebuilding a compromised laptop? If it is not in the matrix, assume neither side will do it.

Finger-pointing during outages. Agree who leads incident response, and who calls whom, before the first outage, not during it.

Duplicate tools. Two antivirus products, two RMM agents or two backup systems cost money and create conflicts.

Undocumented changes. If the provider changes a firewall rule and internal IT does not know, the next troubleshooting session starts from a wrong picture. All changes go through a ticket.

Lock-in. If the provider owns every tool and all the documentation, leaving becomes painful. Settle data ownership, export and transition help in the contract.

Scope creep without a conversation. Internal staff quietly push more and more work to the provider, or the reverse. Review the split regularly and adjust the agreement openly.

How to tell whether co-managed IT is working

Six months in, you should be able to answer "is this helping?" with numbers rather than impressions. These are the measures we would put on the table at a quarterly review:

Measure What good looks like Who reports it
Patch compliance across workstations and servers A high, steady percentage, with exceptions explained MSP
Backup success and restore tests Every protected system backing up, and a documented restore test each quarter MSP
Security alerts Alerts triaged within the agreed time, with a short write-up of anything real MSP
Ticket volume and resolution time Internal staff handling fewer routine tickets than before Both
Project delivery Projects on the roadmap actually getting finished Both
Internal IT time on planned work More hours on projects and business systems, fewer on firefighting Internal IT
Open items in the responsibility matrix Gray areas shrinking over time Both

The last two rows are the ones owners tend to skip, and they say the most. If your internal IT lead is still spending most of the week on password resets after six months, the arrangement is not doing its job, whatever the dashboards say.

It is also worth asking your internal staff directly, without the provider in the room, whether the partnership is making their work easier. Their answer will tell you more than any report.

How to set up co-managed IT services

  1. Inventory what your internal team does today and where it is short on time, tools or skills.
  2. Decide what you want to hand off and what you want to keep. Start narrow if you are unsure; you can expand later.
  3. Draft the responsibility matrix with your internal IT staff, then review it with the provider.
  4. Agree on tools: whose RMM, PSA, documentation platform and security stack, and who pays for licenses.
  5. Set up named accounts with MFA and least privilege for every provider engineer.
  6. Define escalation and incident response contacts, response expectations and after-hours procedures.
  7. Run an onboarding period of 30 to 90 days: deploy agents, document the environment, fix urgent gaps.
  8. Hold a monthly operations review at first, then quarterly, and adjust the matrix as needed.

When you interview providers, use the questions in our guide on how to choose a managed service provider, and ask specifically how many co-managed relationships they support and how they handle disagreements with internal staff.

Our IT outsourcing and co-managed IT page explains how we work alongside internal teams, and our IT help desk and cybersecurity services cover two of the areas on the MSP side of the sample matrix above. A good first step is sitting down with your IT lead and filling in the matrix above with your own names. The gaps you find will tell you what to ask a provider for.

Frequently asked questions

What is co-managed IT in simple terms?

Co-managed IT means your internal IT person or team and an outside managed service provider share responsibility for your technology. Internal staff usually keep user relationships, business applications and onsite work. The provider adds monitoring and security tools, a help desk for overflow or after hours, specialist engineers and project capacity. A written responsibility matrix says who does what.

What is the difference between co-managed IT and fully managed IT?

With fully managed IT, the provider is responsible for the whole agreed scope and you usually have no IT staff of your own. With co-managed IT, you keep internal staff and the provider covers only the areas you assign to it. Co-managed agreements need more upfront work on responsibilities, access and escalation, because two teams touch the same systems.

Will co-managed IT replace our internal IT person?

It should not, and a provider that pitches it that way is selling something else. The point of co-managed IT is to make your internal staff more effective: taking routine tickets, patching and monitoring off their plate, covering vacations and nights, and adding skills such as security or cloud engineering. Internal staff stay the people who know your business best.

Who owns the tools and documentation in a co-managed setup?

That depends on the contract, so settle it before you start. Often the provider licenses the RMM, PSA and security tools and gives your staff accounts, while documentation lives in a shared platform. Make sure the agreement says you own your documentation, passwords and configuration records and can export them if the relationship ends.

How much do co-managed IT services cost?

Pricing usually depends on which responsibilities the provider takes on, how many users and devices are covered, and which tools it supplies. A tools-and-security-only arrangement generally costs less than one that includes full help desk coverage. Ask for a quote that lists each responsibility and tool, so you can compare it with the cost of doing that work internally.

Sources and references

  1. CISA, NSA, FBI and international partners: Protecting Against Cyber Threats to Managed Service Providers and their Customers (AA22-131A, May 11, 2022)
  2. CISA Insights: Risk Considerations for Managed Service Provider Customers

Talk to a Boston IT engineer

Tell us what is slowing your team down. We will review your current setup and send back a plain-English plan with priorities, at no cost.