Guide G1 Microsoft 365
Separate the Microsoft 365 symptom from the responsibility behind it.
Mail, Teams, identity, permissions, devices, and security controls can produce similar complaints while requiring very different ownership. This guide helps a small business or internal team choose the first useful conversation without pretending that a directory can diagnose the tenant.
G1 · Entry 01 Three different jobs
Start with the work that must be owned.
SharePoint, Teams, and Exchange sharing sprawl is a common version of this: see the collaboration-governance guide.
Restore a person’s workflow
Use day-to-day support when a user cannot sign in, send mail, join a meeting, reach a file, or complete a known task. The opening brief should name the affected person, application, error, timing, and attempted steps.
Own recurring tenant health
Use ongoing care when licensing, onboarding, permissions, service changes, lifecycle work, or administration lacks a dependable owner. A recurring operating model matters more than one symptom.
Answer a bounded control question
Use specialist work when leadership needs an independent review, hardening priorities, or a decision about specific Microsoft 365 controls. Define the environment, question, constraints, and expected artifact. Endpoint protection, phishing, and incident-response readiness are broader than tenant hardening - see the email security and incident response guide.
G1 · Entry 02 Decision matrix
What should the first provider be accountable for?
A useful route is defined by responsibility and evidence-not by the product name alone.
| Observed need | Best first route | Useful evidence | Boundary |
|---|---|---|---|
| A person is blocked now | Support | User, app, error, timing | Does not establish recurring ownership |
| Changes and lifecycle tasks recur | Ongoing care | Tenant scope, task list, current owners | Not a substitute for a defined assessment |
| Leadership needs priorities or a decision | Specialist review | Question, controls, stakeholders, deliverable | Not emergency incident response |
G1 · Entry 03 Prepare the brief
Bring enough context to avoid a generic discovery call.
- Which tenant, business area, and people are in scope?
- Is the need immediate, recurring, or decision-based?
- Who currently owns licensing, identity, permissions, and changes?
- What observable outcome would make the first step useful?
- Which constraints or dependencies are already known?
- Keep passwords, recovery codes, tokens, and private access out of the brief.
G1 Next
Compare the category before choosing a destination.
The disclosed directory includes support, recurring-care, and specialist doors with different language and audience contexts. Listings are owned brands, not independent recommendations.