People and access
Day-to-day support, onboarding, offboarding, account changes, and access work that begins with the person and their role.
- User support
- Joiner and leaver coordination
- Account and access changes
Managed services
Support, devices, Microsoft 365, and vendors - managed as one service.
Support, maintenance, Microsoft 365, and vendor coordination work together, with one team keeping track of all of it - not separate services with separate contacts.
- People and access
- Devices and workplace
- Microsoft 365
- Ownership and follow-through
Coverage is confirmed through discovery and written scope.
Four coverage areas
Where the monthly service actually does its work.
Devices and workplace
The upkeep around supported computers and the working environment, connected to how and where the team works.
- Device health context
- Patch and maintenance planning
- Workplace issue coordination
Microsoft 365
Tenant administration and hygiene handled as part of the same service, not a separate, disconnected task.
- Licensing context
- Identity and account hygiene
- Mail and collaboration administration
Ownership and follow-through
Vendors, changes, maintenance, and business decisions stay assigned to someone instead of becoming loose ends.
- Responsibility map
- Material change notes
- Recurring review and follow-up
Scope boundaries
Clear boundaries are part of a well-run service.
Supported users, devices, tenants, applications, locations, maintenance activities, and escalation contacts are documented together. Large projects, specialized compliance work, and third-party remediation may need separate planning.
Recurring service direction
User support, supported-device upkeep, Microsoft 365 administration, account changes, vendor coordination, and recurring review can sit inside the managed scope when confirmed in writing. Everyday Teams and SharePoint use is part of that Microsoft 365 administration - see Teams and SharePoint management.
Separate project work
Large migrations, office moves, platform replacements, remediation programs, and major deployments may need a separate plan, price, timeline, and acceptance criteria. See IT projects and office moves for how that separate plan actually comes together.
Specialist responsibility
Line-of-business applications, telecom services, compliance opinions, physical cabling, and manufacturer warranty work may remain with specialist providers while managed IT coordinates the handoff.
Commercial and business decisions
Leadership retains budget authority, policy choices, risk acceptance, and approval for material change. Technical advice should make those decisions clearer, not quietly make them on the company’s behalf.
Before signing
Ask a proposal to spell out these details.
- Which users, devices, tenants, locations, and applications are supported?
- Where do employees start, and how are vendor handoffs coordinated?
- Which maintenance and security-baseline activities recur?
- What requires business authorization or a separate project?
- How are open decisions and recurring concerns reviewed?
Representative recurring outputs
Depending on written scope, a recurring service relationship may make these items visible:
- supported-user, device, application, and vendor ownership changes;
- joiner/leaver actions and access exceptions requiring authorization - see the new-hire and departure checklist;
- maintenance completed, deferred, or blocked by a dependency;
- repeated support friction worth addressing beyond the individual request;
- material Microsoft 365 or vendor changes and the decisions they create.
These are illustrative service outputs, not a promise of a particular report format, frequency, or automated dashboard.
Where the model helps
Common situations call for a different mix of work.
A growing team without internal IT
Employee support, account changes, device upkeep, Microsoft 365, and vendor coordination need one recurring owner while leadership retains approvals.
An internal IT lead with an execution gap
A co-managed scope can add selected support or maintenance capacity without displacing architecture and priority ownership.
A company preparing to change providers
Transition work first needs an access, vendor, dependency, and open-work inventory; optimization follows after stable ownership.
See how that mix changes for professional services firms and nonprofit organizations.
Next
See how the work continues month to month.
Reach the team
Tell us what needs an owner
Share your team size, current support setup, and the responsibilities you want clarified. We will use that to figure out whether an MSP introduction makes sense.
Online requests are not available right now. No message is sent from this page.