Agree which day-to-day work we will own
A managed service starts with a defined environment and a named set of responsibilities. Your proposal identifies the users, devices, tenants and sites covered, the support hours and the work that remains with your team or another supplier.
Business support
Monitoring, patching, service tickets and escalation for the systems named in your scope.
Microsoft administration
Microsoft 365 tenant operations, account lifecycle, access changes and license hygiene where included.
Devices and endpoints
Windows and mobile-device support, Intune management and Autopilot provisioning where agreed.
Security and recovery responsibilities
Name who approves identity changes, handles alerts, maintains backups and owns recovery work before operations begin.
An onboarding process built around approved access
- Discover the environment. Review users, devices, tenants, licenses, sites and the current ticket pattern.
- Write the scope. Agree included workloads, hours, remote or on-site needs, recovery responsibilities and separately quoted projects.
- Prepare operations. Arrange privileged access through an approved process, then set up the agreed monitoring, ticketing and documentation. Do not send passwords through the enquiry form or email.
- Operate and review. Track the agreed work through service reporting, open risks, license reviews and a short roadmap. Record changes to the scope.
Know what the proposal will document
- Workloads, users and sites in scope.
- Support hours, severity definitions, response targets and escalation contacts.
- Who authorizes changes to identity, email and devices.
- Security, backup and recovery responsibilities.
- Recurring administration, subscription costs and separate projects.
- Service reporting and procedures your team can retain.
Choose managed or co-managed support
A managed engagement assigns CloudTechForce the agreed day-to-day responsibilities. A co-managed engagement supports your existing IT team with a written split of work, including Level 3 Microsoft 365 and Azure escalation. A migration or major redesign is scoped as a project with acceptance checks.
Questions buyers ask
What is included in managed IT support?
The written scope identifies the users, systems, monitoring, patching, tickets and administration included. It also names support hours, security and recovery duties, and projects or subscriptions quoted separately.
Does monitoring mean every support request is handled around the clock?
Monitoring coverage and support response are separate parts of the agreement. The portfolio publishes 24/7/365 NOC monitoring; your proposal defines the monitored workloads, severity levels, support hours and response targets.
Can you work with our internal IT staff?
Yes. Co-managed support can assign Level 3 Microsoft 365, Entra ID, Intune, Exchange and Azure work to CloudTechForce while your team keeps the agreed day-to-day responsibilities and change approvals.
How is managed IT priced?
We review the environment and work to be covered before proposing a price. User and device counts, workloads, coverage and existing responsibilities inform the scope. Subscriptions, cloud usage and project work are identified separately.
Related services
Request a managed IT proposal
Share your users, devices, sites, current support arrangements and the work you need covered. Access is arranged separately through an approved process.
Remote delivery across the United States and Canada. Hours, price, on-site exceptions and recovery responsibilities are confirmed in your written proposal.
Updated October 15, 2026. Monitoring, support response and project work have distinct scopes. Capability and credential information · Company details.