“What else do buyers usually ask?”
Know what is-and is not-being offered.
Use this page to check service fit, plan differences, safe intake, approvals, and the point where everyday support becomes another kind of work.
Question group
Fit & scope
Is M365 Desk a full managed IT service?
No. It is positioned for everyday Microsoft 365 user support. Network, hardware, broad strategy, migrations, security investigations, and major projects need separately defined ownership.
Can we begin with one issue?
Describe the issue or prepare a support brief. Fit should be confirmed before implying that a plan or one-off engagement applies.
Does the desk support non-Microsoft software?
The published lane is Microsoft 365 user support. Another application may be relevant context, but its ownership needs clarification rather than an assumption of coverage.
When does a ticket become project work?
When the desired outcome is migration, redesign, tenant-wide policy, a major rollout, investigation, or another defined change rather than restoring expected everyday use.
Question group
Plans & pricing
What currency and pricing unit are shown?
Essential is $39 and Plus is $49 CAD per user per month.
What does Plus add?
Plus adds priority queue position, light tenant check-ins, and light security-baseline support to the core everyday user-support lane.
Are Microsoft licences included?
No. You keep your own Microsoft 365 licensing. The per-user price here is for support only.
Is support unlimited?
No unlimited-support claim is published. Team context, request pattern, administrative access, and fit still need confirmation.
Is Plus a security audit?
No. Light security-baseline support is not a focused audit, hardening engagement, or investigation.
Question group
Requests & safety
What should a useful request include?
Share the affected person, app or service, device, exact wording, time observed, business impact, recent change, and whether others are affected.
Should we send a password or recovery code?
No. Never include passwords, recovery codes, private keys, or approval prompts. Describe the prompt instead.
Do you guarantee a response time?
No response-time guarantee is published on this site. Plus names priority queue position, not a specific response-time commitment.
What must our team approve?
Name authorized people for mailbox access, licences, guests, roles, departures, information ownership, and other routine changes. Urgency does not create authority.
What counts as a useful outcome?
The employee is unblocked, an approved routine change is recorded, required information or approval is named, or the issue is handed to the correct owner with usable context.