trio.so
MSP

Co-Managed IT: How Internal IT and an MSP Share One Console

Co-managed IT explained: who does what, how to split roles between internal IT and an MSP, and how to give both access to one device console.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

Co-managed IT is a service model where a company keeps its own IT staff and also hires a managed service provider (MSP) to share the work. Internal IT keeps the work that depends on knowing the business. The MSP takes the tasks that need extra hands, tooling that runs outside office hours or skills the team lacks. The model only works when both sides agree who does what, and when both can see and change the same devices.

If you are internal IT sizing up an MSP, or an MSP pitching to a company that already has IT staff, start with the responsibility table and the section on shared console access.

What co-managed IT means

Datto describes co-managed IT as a model that combines an internal IT department with an MSP, where the two teams "divide their roles and responsibilities based on technology, skill gaps or expertise" (Datto, June 2023). Co-managed IT services are the same arrangement sold as a contract: the MSP agrees to a defined list of services and the internal team covers the rest.

Two points set it apart from other setups. The MSP's duties are limited to what the agreement lists, so anything not written down stays with internal IT. And internal IT stays in charge of the relationship with the business: the MSP supports the team, it does not replace it.

Co-managed IT vs managed IT vs in-house

In-house ITFully managed ITCo-managed IT
Who runs ITYour own staffThe MSPYour staff and the MSP, by agreement
Who answers usersYour help deskThe MSP's help deskEither, depending on the split
Who owns strategyYour IT leadMostly the MSPYour IT lead
Works best whenYou have enough people and skillsYou have little or no IT staffYou have a team that is stretched or missing skills

For the MSP side of the picture, see our guide to managed IT services.

How to split responsibilities between internal IT and an MSP

There is no standard split. Providers describe the same pattern, though: the MSP takes infrastructure and routine work, and internal IT keeps end-user support and anything specific to the business. VC3 puts it this way: the MSP will "monitor, maintain, and patch your server and network," which "frees up your internal IT experts to focus on supporting your end users" (VC3, September 2021). Datto notes that some companies outsource only the help desk, and others only network and security monitoring.

A starting point to adjust, not a rule:

TaskUsually internal ITUsually the MSP
Onboarding and offboarding peopleDecides who gets what accessRuns the steps if asked
First-line help deskCommon when the team is big enoughCommon for after-hours and overflow
Device enrollment and policiesSets the standardApplies and maintains it
PatchingApproves exceptionsRuns the schedule and reports
Security monitoringOwns risk decisionsWatches and escalates, if the contract includes it
Vendor and budget decisionsOwnsAdvises

This table is our judgment from how these agreements are usually written, not a figure from a survey. Whatever you choose, write it down per task, and name one owner for each.

The co-managed IT model in practice: handoffs and escalation

Most friction comes from the gaps between the two teams, not from the split itself. Three things to agree before the contract starts:

  • Who takes a ticket first. Decide whether users go to internal IT or the MSP, and what moves to the other side and when.
  • What counts as an escalation. For example: anything affecting more than one team, anything outside the internal team's skills, anything that needs a change window.
  • Who approves changes. If the MSP can change a policy on every laptop, say who signs off first.

Write these down in the agreement. Review them every quarter, because the split that fit a 60 person company will not fit a 200 person one.

Sharing one console: roles and access

The tooling question is the one most guides skip. If internal IT and the MSP each use their own device management tool, devices end up with two sets of policies and nobody knows which one applied. The cleaner setup is one console both teams sign in to, with access set per person.

trio.so is a device management console for Windows, macOS, Linux, iOS and Android. In trio.so, IT staff sign in with built-in or custom roles. That lets you give the MSP's technicians the access their part of the work needs and keep other settings with your own team. For an MSP that serves many companies, trio.so manages several client companies from one console, with each client's devices, users and policies kept separate. You can export the console's member list to CSV (name, email, status, roles and last-active date), which makes a quarterly access review a short job: check that every MSP technician still working with you is on the list, and remove those who are not.

Questions to settle for any shared console, whichever tool you use:

  • Who can change policies, and who can only view devices?
  • Does each MSP technician have their own sign in, or do they share one? (Their own.)
  • What happens to access when a technician leaves the MSP?
  • Can you see what the MSP changed, and when?

When co-managed IT fits and when it does not

It fits when you have a small team that cannot cover every hour or every skill, when you have projects that would stall without extra capacity, or when you want the MSP's tools without giving up control. It fits less well when there is no internal IT lead to own the relationship, because then the MSP fills the gap and you are paying for fully managed IT but expecting a shared setup. It also fits poorly when the MSP will not agree to written scope.

Sources vary on cost, and several MSP pages quote savings without showing where the figure comes from, so treat any such number as a sales claim until the provider shows its basis.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Get Ahead of the Curve

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Don't let inefficiencies hold you back.

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently asked questions

Co-managed IT is a model where a company's own IT staff and an MSP share responsibility for IT, split by task, skill or hours. The company keeps control of strategy and the MSP handles the agreed services.

In managed IT the MSP takes over IT operations. In co-managed IT your team stays in place and the MSP covers part of the work, limited to the services in the contract.

Companies that already have IT staff but not enough capacity or skills to cover everything. Companies with no IT staff usually need fully managed IT instead.

It lists the services the MSP provides, who answers users first, how issues escalate, who approves changes, and which tools and access each side gets. Anything not listed stays with internal IT.

Internal IT usually handles end-user support and business-specific work. The MSP handles routine maintenance, patching and monitoring, and takes overflow. Both work from shared tools and an agreed escalation path.

It depends on the provider and the scope, and MSPs usually quote per user or per device. Plans start at $5 per device. See pricing. Give internal IT and your MSP one console, with access set per person. Start free trialBook a demo 14-day free trial. No credit card required. If you run an MSP, see the multi-client MSP console or the partner program.

Related

From the blog

The related industry news, interviews, technologies, and resources.