How-to guide

Planning your Microsoft 365 rollout

For International businesses 10 min read Updated May 2026

A Microsoft 365 rollout succeeds when you treat it as a program with milestones, not a weekend DNS flip. The checklist below is aimed at owners, ops leads, and IT partners planning the first 90 days.

Plan users, domains, security, and training before you assign licenses
Plan users, domains, security, and training before you assign licenses

Phase 1 — Discovery (week 1–2)

User and license inventory

Question Why it matters
Who needs company email? Drives Exchange seat count
Who needs desktop Office? Standard/Premium vs Basic
Any shared inboxes (support@, sales@)? Often free with licensing rules
Frontline or shared tablets? May suit F-series or kiosk policies

Document job roles, not just headcount. A warehouse tablet that only checks Teams shifts should not automatically get the same SKU as a finance analyst with Power BI.

Current systems map

List what you are leaving: Gmail or cPanel mail, Dropbox folders, Zoom-only meetings, on-prem file servers. Each dependency needs an owner and a cutover date.

Phase 2 — Foundation (week 2–4)

Domain and mail

  • Verify you control DNS for your primary domain.
  • Plan MX, SPF, DKIM, and DMARC before cutover; test with a pilot mailbox.
  • Keep a rollback window (often 48–72 hours) if you migrate from another host.

Security baseline

Decide on day-one rules:

  • MFA for all admins and all users (recommended).
  • Block legacy authentication where possible.
  • Separate break-glass admin accounts from daily work accounts.
Multi-factor authentication should be planned before mass user invites
Multi-factor authentication should be planned before mass user invites

Phase 3 — Collaboration design

Agree internally:

  • Teams team naming (department, project, customer).
  • Whether guest access is allowed for suppliers.
  • File locations: personal OneDrive vs SharePoint libraries behind Teams channels.

Publish a one-page "where work happens" guide before you invite hundreds of users.

Phase 4 — Pilot and training

Run a pilot group (10–20 people across roles) for two weeks. Collect friction on mail mobile setup, Teams channels, and sync errors. Schedule two short trainings: mail + MFA and Teams + files. Name an internal champion who can escalate to your partner.

Phase 5 — Go-live and hypercare

  • Stagger license assignment if your partner supports it.
  • Monitor helpdesk themes in the first month (password resets, sync, meeting audio).
  • Review external sharing and guest accounts after 30 days.

Procurement timing

When seat counts and SKUs are stable, get quotes on M365 Deals pricing or ask for migration-inclusive scope via contact.