01
Essentials
Primary need
Licensing, onboarding, administrative ownership, and migration readiness.
Typical output
A practical licensing and onboarding plan with clear responsibilities and next steps.
Review EssentialsMicrosoft 365 service paths
Compare the three Microsoft 365 service paths.
Start with licensing and onboarding, strengthen security and access, or establish ongoing administration and support. Every engagement is confirmed through a human-reviewed scope before work begins.
This page explains typical fit, deliverables, boundaries, and buyer responsibilities. It is not a quote, order, or authorization to change a Microsoft 365 environment.
At a glance
Choose the service path around the outcome you need now.
The three paths can stand alone or form a sequence. The final scope depends on the current environment, authorized priorities, and the responsibilities accepted by both parties.
02
Secure Work
Primary need
Identity, email, sharing, collaboration, device, and access-control direction.
Typical output
A prioritized security baseline and implementation plan tied to the approved Microsoft 365 scope.
Review Secure Work03
Managed Practice
Primary need
Ongoing administration, approved changes, support coordination, and periodic review.
Typical output
A documented operating relationship with named contacts, boundaries, and support expectations.
Review Managed PracticeComparison
How the service paths differ.
| Decision area | Essentials | Secure Work | Managed Practice |
|---|---|---|---|
| Best starting point when | Licensing, onboarding, ownership, or migration planning is unclear. | Identity, email, sharing, devices, or access controls need a stronger baseline. | The firm needs ongoing help administering Microsoft 365 and coordinating approved changes. |
| Typical engagement motion | Defined setup or planning engagement. | Security-focused review and scoped implementation plan. | Ongoing operating scope with documented contacts and expectations. |
| Ongoing administration | Handoff guidance unless separately scoped. | Not included unless the approved scope adds it. | Core purpose of the service path. |
| Human approval | Required before quotes, orders, migration work, or changes. | Required before configuration or remediation work. | Required through authorized requestors and the agreed change process. |
Service path 01
Essentials
A practical Microsoft 365 foundation for firms that need clearer licensing, onboarding, administrative ownership, or migration readiness.
Licensing and onboarding
Best for
Firms 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.
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.
Service path 02
Secure Work
A security-focused Microsoft 365 path for firms that need clearer identity, email, sharing, collaboration, device, and access-control decisions.
Security and access
Best for
Firms 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.
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.
Service path 03
Managed Practice
An ongoing Microsoft 365 administration and support path for firms that want accountable help coordinating approved changes and routine platform needs.
Administration and support
Best for
Firms 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.
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.
What happens next
A controlled path from interest to approved work.
- 01
Choose a likely path
Use this comparison or the browser-only Service Fit check to identify a preliminary starting point.
- 02
Confirm the current state
Discuss firm type, user range, Microsoft 365 status, desired outcome, 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 Practice focuses on ongoing administration and support. Service Fit can provide a preliminary 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 Practice 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 desired outcome. Do not submit credentials, client matters, patient information, financial records, payment information, or other confidential details.
Choose the next conversation
Start with Service Fit or speak with ISD Logic.
Use the browser-only fit check when the service path is unclear, or begin a public-safe conversation when the likely outcome is already known.