Microsoft 365 service paths
Compare the three Microsoft 365 service paths.
Choose the help your organization needs now. Start with licensing and onboarding, strengthen security and access, or get ongoing Microsoft 365 administration and support. We confirm scope, responsibilities, timing, and price with you before work starts.
This page shows who each service is for, what is usually included, what is not included, and what you need to provide. It is not a quote, order, or authorization to change a Microsoft 365 environment.
At a glance
Start with the problem you need to solve.
Each path can be used on its own. Setup, migration, and ongoing support are optional assistance, included only when agreed in your scope. We confirm the work after reviewing your current setup, priorities, and responsibilities.
01
Essentials
Microsoft 365 setup help for organizations sorting out licensing, onboarding, administrative ownership, or migration readiness.
Your starting deliverable
A licensing and onboarding plan that assigns responsibilities and sets the next steps.
- License-fit recommendation.
- User onboarding and offboarding plan.
- Administrative ownership and handoff checklist.
Full scope, exclusions and responsibilities
Best for
Organizations preparing for Microsoft 365, cleaning up an existing setup, adding users, planning a migration, or clarifying who owns day-to-day administration.
Typical deliverables
- License-fit recommendation based on approved user roles and business needs.
- User onboarding and offboarding plan.
- Administrative ownership and handoff checklist.
- Migration readiness notes and sequencing when migration is in scope.
- Plain-English decision summary and next-step plan.
Key boundaries
- No automatic license purchase, order, or tenant change.
- Migration execution, device management, advanced security remediation, and ongoing support require an approved scope.
- Microsoft availability, license terms, and pricing remain subject to Microsoft terms and the final quote.
How the work usually starts
A defined licensing, onboarding, or planning project.
Ongoing administration
Handoff guidance unless separately scoped.
Human approval
Required before quotes, orders, migration work, or changes.
Buyer responsibilities
- Provide accurate user counts and high-level role categories.
- Identify authorized decision makers and tenant administrators.
- Approve the quote, timeline, access method, and proposed changes before work begins.
02
Secure Work
A security-focused Microsoft 365 path for organizations that need clearer identity, email, sharing, collaboration, device, and access-control decisions.
Your starting deliverable
A prioritized security baseline and implementation plan tied to the approved Microsoft 365 scope.
- Microsoft security-product fit recommendation.
- Identity, email, sharing, and access-control review.
- Prioritized implementation or remediation plan.
Full scope, exclusions and responsibilities
Best for
Organizations that have Microsoft 365 in place but need a stronger security baseline, clearer administrative ownership, or a prioritized remediation sequence.
Typical deliverables
- Identity and multifactor-authentication baseline direction.
- Email, sharing, collaboration, device, and access-control review.
- Microsoft security-product fit recommendation.
- Prioritized implementation or remediation plan.
- Administrative ownership and approval checkpoints.
Key boundaries
- This service path is not a compliance certification, penetration test, security operations center, or incident-response service.
- No configuration change occurs without authorized review and approval.
- A security baseline reduces avoidable exposure but does not guarantee that incidents cannot occur.
How the work usually starts
A focused security review followed by an approved implementation plan.
Ongoing administration
Not included unless the approved scope adds it.
Human approval
Required before configuration or remediation work.
Buyer responsibilities
- Identify authorized administrators and business decision makers.
- Confirm acceptable business disruption, sequencing, and user communication.
- Review and approve the prioritized plan before implementation begins.
03
Managed Microsoft 365
An ongoing Microsoft 365 administration and support path for organizations that want direct help coordinating approved changes and routine platform needs.
Your starting deliverable
A documented support plan with named contacts, request channels, boundaries, and service expectations.
- Approved user and license changes.
- Issue triage and support coordination.
- Periodic configuration and optimization review.
Full scope, exclusions and responsibilities
Best for
Organizations without dedicated Microsoft 365 administration capacity, or teams that want a named advisor to coordinate approved changes and ongoing support.
Typical deliverables
- Named business and technical contacts.
- Approved user, license, and administrative changes.
- Issue triage and coordination with the appropriate support path.
- Periodic configuration and optimization review.
- Documented request, approval, and escalation expectations.
Key boundaries
- Service hours, response expectations, covered requests, and exclusions are stated in the approved agreement.
- The public offer does not promise 24/7 emergency response, unlimited support, or incident-response services.
- Microsoft and other third-party service availability remains outside ISD Logic control.
How the work usually starts
An ongoing support agreement with named contacts and clear request rules.
Ongoing administration
Core purpose of the service path.
Human approval
Required through authorized requestors and the agreed change process.
Buyer responsibilities
- Maintain a current list of authorized requestors and approvers.
- Use the agreed support and change-request channels.
- Provide timely approvals and business context for requested changes.
Human approval: Quotes, orders, access and changes are reviewed before work begins. Microsoft availability, license terms, and pricing remain subject to Microsoft terms and the final quote.
What happens next
Four steps before work starts.
- 01
Choose a likely path
Use this comparison or the browser-only Service Fit check to identify the best place to begin.
- 02
Confirm the current state
Discuss firm type, user range, Microsoft 365 status, the result you want, and high-level constraints through an appropriate channel.
- 03
Approve the scope
Review deliverables, exclusions, buyer responsibilities, timing, pricing, access boundaries, and change approvals.
- 04
Deliver and review
Complete only the approved work, confirm handoff or ongoing support expectations, and document the next decision.
Service FAQ
Questions to settle before work begins.
How do we know which service path fits?
Start with the primary business need. Essentials focuses on licensing and onboarding, Secure Work focuses on security and access, and Managed Microsoft 365 focuses on ongoing administration and support. Service Fit can provide a simple starting point.
Are licenses purchased automatically?
No. The public site does not place orders. License recommendations, procurement route, Microsoft terms, and pricing are reviewed before a quote or order is approved.
Who controls the Microsoft 365 tenant?
Authorized administrators, ownership responsibilities, delegated access, and change approvals are documented before access is granted or work begins. A public inquiry is never treated as authorization.
Can email or file migration be included?
Yes, when migration is included in an approved scope. Discovery, readiness, responsibilities, sequencing, data boundaries, and rollback considerations are confirmed first.
Does Secure Work certify compliance?
No. Secure Work provides Microsoft 365 security direction and scoped implementation support. It is not a legal opinion, regulatory determination, compliance certification, penetration test, or guarantee against incidents.
Does Managed Microsoft 365 include emergency or unlimited support?
No public promise is made for 24/7 emergency response or unlimited support. Covered requests, service hours, response expectations, escalation, and exclusions are stated in the approved agreement.
What should we share through the public form?
Share only business-level context such as firm type, approximate user range, current Microsoft 365 status, and the result you want. Do not submit credentials, client matters, patient information, financial records, payment information, or other confidential details.
Choose the next conversation
Not sure where to start?
Use the browser-only fit check to narrow the choice, or begin a business-level conversation if you already know the result you need.