For a Microsoft-heavy small business, the choice is not simply whether to outsource the helpdesk. It is who owns the work when a laptop fails, a user leaves, a security alert arrives, or an application vendor stops responding.
Co-managed IT divides that work between your employees and a provider. Fully managed IT assigns the provider the agreed day-to-day operating responsibility. Neither removes your responsibility to approve access, spending, business priorities, and acceptable risk.
Choose based on capacity and ownership
Scroll horizontally to compare all columns.
| Decision | Co-managed can fit when… | Fully managed can fit when… |
|---|---|---|
| Internal capacity | A named IT employee has time to own the retained work | IT is handled informally or the internal team needs to focus elsewhere |
| Business applications | Internal specialists should retain application knowledge | A provider can coordinate support with named application owners and vendors |
| Change decisions | Internal IT can review and coordinate changes | Leadership needs a provider to prepare and execute an agreed change plan |
| Coverage gaps | The provider fills explicitly defined escalation or absence gaps | One operator is needed across most routine responsibilities |
| Accountability | Both parties can use the same queue and responsibility map | Handoffs between several operators are creating unresolved work |
Choose neither model until you can name an owner and backup for every critical responsibility. A small internal team may run an excellent co-managed arrangement. A larger company may still need fully managed operations for a particular business unit.
Write the responsibility map before comparing prices
This is an illustrative division of work, not a Monster MSP package or contract. “Provider” means the party assigned that responsibility in the agreement.
Scroll horizontally to compare all columns.
| Work | Example co-managed arrangement | Example fully managed arrangement | Business responsibility retained |
|---|---|---|---|
| User support | Internal IT handles intake; provider owns agreed escalations | Provider handles intake and resolution within scope | Report impact and approve exceptions |
| Joiners and leavers | HR authorizes; internal IT executes; provider verifies agreed controls | HR authorizes; provider executes and records completion | Approve identity, access, and departure timing |
| Device standards | Internal IT approves standards; provider deploys agreed policies | Provider maintains approved standards and deployment | Approve spend and application requirements |
| Security alerts | Provider triages covered alerts; internal owner coordinates business decisions | Provider coordinates the agreed response process | Authorize disruptive actions and outside assistance |
| Application incidents | Internal application owner leads; provider supports identity/network checks | Provider coordinates vendors; application owner validates results | Retain application/process ownership |
| Roadmap and budget | Internal IT leads with provider input | Provider prepares recommendations with leadership | Decide priorities and funding |
Keep one accountable operator for each task even when several people contribute. “Shared” without a named lead is a gap, not a responsibility assignment.
A practical example
Consider a hypothetical 45-person professional-services business with one IT generalist. That employee knows the case-management application, manages office moves, and supports leadership, but device maintenance and Microsoft 365 administration keep slipping.
A co-managed scope could assign device-policy maintenance, agreed Microsoft administration, and second-line support to the provider. The generalist retains application ownership and project coordination. Both parties use one escalation record, and a named business manager approves disruptive changes.
If the generalist leaves, the arrangement should not silently become fully managed. Reassign intake, approvals, documentation ownership, and vendor coordination explicitly, then revise coverage and price. A different label alone does not transfer those responsibilities.
Avoid the four common ownership gaps
Scroll horizontally to compare all columns.
| Gap | Control to put in writing |
|---|---|
| A ticket passes between teams | One lead keeps the ticket until another owner accepts it |
| The only knowledgeable person is absent | Named backup, accessible documentation, and tested access |
| Both teams change the same policy | Named policy owner, change record, and agreed approval path |
| An alert arrives outside staffed hours | Defined monitoring, notification, escalation, and response coverage |
Monitoring software running overnight is not evidence that a person is investigating every alert. Ask specifically which hours and actions the agreement covers.
Checklist for changing support models
- List recurring work, open issues, vendors, and systems—not just employee count.
- Identify retained responsibilities and the actual time available to perform them.
- Transfer documentation through an approved secure channel; keep the business in control of its accounts.
- Agree intake, escalation, access approvals, change authority, and absence coverage.
- Test one new-user request, one support escalation, and one simulated service disruption.
- Review unresolved handoffs before declaring the new model operational.
These are readiness gates, not a fixed implementation schedule. Access restrictions, incomplete records, and provider notice periods can change the timeline.
Common questions
Is co-managed IT always cheaper?
No. Compare provider fees plus the internal time and tools you retain. A smaller provider scope can still leave expensive coordination or uncovered work inside the business. Use the managed IT pricing worksheet to compare equivalent responsibilities.
Can fully managed IT work alongside an internal employee?
Yes. The employee may own business applications, strategy, or projects while a provider owns the agreed operations. The responsibility map matters more than the label.
Decide what your team should keep
Bring a list of current responsibilities, recurring delays, and internal capacity to an initial conversation. Do not send credentials or tenant exports through the form.
Request a Free Initial Assessment to discuss the ownership gaps. For delivery scope, explore SMB IT services.