Register / 02 Routes
Start with the outcome that must be owned first. A present blocker, recurring environment care, a defined specialist question, and partner fulfilment require different opening briefs.
Entry 01 Route finder
Entry 02 The four comparisons
Route Blocked now
For: access, accounts, mail, Teams, devices, files, and practical user issues.
Not for: automatically turning one ticket into a security review or management agreement.
Bring: who is affected, the tool, when work stopped, and what has been tried.
M365 Desk - EN ↗Aide Informatique - FR ↗Route Ongoing IT
For: tenant management, lifecycle tasks, recurring hygiene, managed IT, and coordination.
Not for: a one-time issue with no ongoing responsibility.
Bring: environment in scope, current owners, repeated friction, and expected cadence.
M365 Care - EN ↗PME Soutien - FR ↗Route M365 and security
For: posture review, hardening, a decision, advisory, or a scoped project.
Not for: vague fear-based “security” without a question or environment in scope.
Bring: decision, scope, constraints, stakeholders, and useful deliverable.
Secure M365 - EN + FR option ↗IT White Glove Canada - EN/FR ↗Route Partner fulfilment
For: agencies, consultants, VARs, and IT practices seeking delivery capacity.
Not for: direct end-client help desk requests.
Bring: partner role, service boundary, client-facing model, and handoff expectations.
Whitelabel MSP - EN ↗MSP Whitelabel Canada - EN/FR ↗Entry 03 Route examples
Real situations often cross categories. Sequencing prevents an urgent ticket from swallowing the longer-term decision.
First: day-to-day support restores access. Then: if onboarding repeatedly fails, ongoing care should own the lifecycle process.
First: define the review question and expected priorities.Then: decide whether recurring tenant management should own the resulting changes.
First: partner delivery defines client ownership and handoffs. Not first: sending the end client through a direct support door without a confirmed model.
Entry 04 Guides G1–G18
These guides explain responsibilities, boundaries, evidence, and provider questions without repeating a child brand’s sales offer.
Distinguish a user symptom, recurring tenant ownership, and a bounded control review.
Read guide G1 →Prepare a safe, observable issue brief and know when repeated problems signal a wider gap.
Read guide G2 →Map recurring responsibilities, operating boundaries, cadence, and transition evidence.
Read guide G3 →Clarify client ownership, handoffs, delivery evidence, and relationship boundaries.
Read guide G4 →Frame a decision, review, roadmap, or implementation brief around a useful artifact.
Read guide G5 →Separate a broken device from an unowned Intune/MDM enrollment and patch-cadence gap.
Read guide G6 →Distinguish a dropped connection, an unowned firewall or Wi-Fi footprint, and a scoped connectivity project.
Read guide G7 →Turn a vague Law 25 or PIPEDA compliance worry into a bounded question with a named artifact.
Read guide G8 →Frame a server retirement or Azure migration as a bounded, evidence-driven project.
Read guide G9 →Recognize a dated deliverable - a move, cutover, or rollout - distinct from an open-ended relationship.
Read guide G10 →Separate a blocked file or mailbox from unowned SharePoint and Teams sharing sprawl.
Read guide G11 →Name the alert-history and patch-cadence evidence a monitoring claim should show.
Read guide G12 →Treat a phone-system port, migration, or routing change as its own bounded project.
Read guide G13 →Separate "a backup runs" from a tested restore, with named RPO/RTO and single-point-of-failure evidence.
Read guide G14 →Split a fear-based "make us secure" ask into endpoint, phishing, training, and incident-response questions.
Read guide G15 →Give MFA, SSO, and Conditional Access a named owner instead of a buried tenant bullet.
Read guide G16 →Turn joiner-mover-leaver into a named, repeatable checklist instead of a single line item.
Read guide G17 →Give hardware buying and licence reconciliation a budget owner and a renewal calendar.
Read guide G18 →Entry 05 Provider questions
Ask for included people, systems, tasks, decisions, and explicit exclusions.
Dependencies and retained responsibilities should be visible before work begins.
Look for artifacts, decisions, records, or acceptance criteria appropriate to the work.
Ask who decides, what context is required, and how ambiguity moves between parties.