Why a structured M365 rollout matters
Microsoft 365 is not a single product — it is a stack of tightly coupled workloads (Exchange Online, SharePoint, Teams, OneDrive, Entra ID, Intune, Purview, Defender) that share an identity and compliance backbone. A migration that treats each workload in isolation ends up with broken mail flow, orphaned identities and unmanaged endpoints. The approach I have used across dozens of tenants is to land identity and security first, then migrate workloads in priority order, then optimise licences once usage data is real.
This guide walks through each workload in the order I implement them, with the configuration decisions, PowerShell snippets and governance choices that hold up in production.
Exchange Online migrations and hybrid deployments
Pick the migration path by tenant size and downtime tolerance: Cut Over for under 150 mailboxes with a maintenance window, Staged for larger estates migrating in batches, Hybrid when mailboxes must live on both sides for an extended period, and IMAP for non-Exchange sources. For Hybrid, run Azure AD Connect and the Hybrid Configuration Wizard (HCW) to establish free/busy, mail flow and routing.
- Verify the public domain and accepted domains in the tenant before cutover
- Lower MX/TTL DNS records 24 hours before switchover
- Run a 5–10 mailbox pilot batch before bulk migration
- Keep the last on-premises Exchange server for recipient management after migration
Bulk-enable remote mailboxes with PowerShell
When moving to a Hybrid with cloud mailboxes, enable remote routing for on-premises users in one scripted pass:
$OU = "OU=Staff,DC=corp,DC=contoso,DC=com"
$TargetDomain = "contoso.mail.onmicrosoft.com"
Get-User -OrganizationalUnit $OU -RecipientTypeDetails User |
Where-Object { -not $_.RemoteRecipientType } |
ForEach-Object {
Enable-RemoteMailbox -Identity $_.DistinguishedName `
-RemoteRoutingAddress ("{0}@{1}" -f $_.SamAccountName, $TargetDomain)
}SharePoint Online governance and collaboration
Design SharePoint around business units using a small number of hub sites, not a flat sprawl of team sites. Hub sites roll up navigation, search and branding across associated sites. Set tenant-level external sharing to "Existing guests" and tighten further on HR, Finance and Legal sites. Time-box anonymous sharing links so forgotten access does not linger.
- Limit hub sites to a handful aligned to business units
- Default external sharing to existing guests; expire anonymous links
- Enable Microsoft 365 group expiration to retire inactive sites
- Train site owners — governance is a people problem first
Teams administration and calling
Teams governance starts with meeting policies, messaging policies and app permission policies. For calling, configure Direct Routing or Operator Connect, assign calling plans, and define voice routing policies. Use Teams templates to standardise team creation for departments, and restrict who can create org-wide teams.
| Teams policy area | What to configure | Why it matters |
|---|---|---|
| Meeting policies | Who can bypass lobby, recording, cloud video interop | Controls meeting security and compliance |
| App permission policies | Allowed/blocked apps per user group | Prevents unvetted third-party data access |
| Calling policies | Private calls, voicemail, delegation | Defines user calling experience |
| Voice routing | Routes, PSTN usages, trunks (Direct Routing) | Directs calls to the right gateway |
Entra ID / Azure AD implementation
Entra ID is the identity backbone for every M365 workload. Get sync right first: Azure AD Connect with sourceAnchor (mS-DSN-ConsistencyGuid), filtered to exclude service and test accounts. Choose Seamless SSO plus Password Hash Sync as the default, add ADFS only when a specific app demands SAML federation. Layer Conditional Access as the control plane — require MFA for admins, block legacy auth, require compliant devices for sensitive apps.
- Filter service, shared and test accounts out of sync
- Enable Seamless SSO before the first user signs in
- Maintain two break-glass admins excluded from Conditional Access
- Run Conditional Access in report-only mode for a week before enforcing
OneDrive management and compliance
OneDrive is the personal layer of M365 storage. Set per-user storage quotas to match business need (not the default), configure sharing policies to align with SharePoint tenant settings, and enable Files On-Demand to reduce endpoint storage pressure. Use DLP policies to catch sensitive identifiers before they leave the tenant.
Purview compliance and data governance
Microsoft Purview turns compliance into operations. Use retention labels to classify content by business value, sensitivity labels to mark and protect confidential data, and Data Loss Prevention policies to stop risky sharing. Start narrow and high-value — one or two DLP policies (e.g. credit card numbers in Exchange and SharePoint) — then expand. Enable unified audit logging on day one; you cannot retroactively audit what was never logged.
Defender for Office 365 security
Exchange Online Protection is the baseline anti-malware and anti-spam layer. Defender for Office 365 Plan 1 adds Safe Links and Safe Attachments; Plan 2 adds threat hunting and automated investigation. Apply the preset Standard and Strict security policies before hand-tuning rules — they give a defensible baseline in minutes. Enable Safe Links for internal mail too, not just inbound, because lateral phishing is real.
Intune device management
Use Windows Autopilot for corporate device enrolment and MAM app protection policies for BYOD instead of full MDM. Replace Group Policy with Intune configuration profiles (Settings Catalog and Administrative Templates), piloting each profile before broad assignment. Tie Intune compliance to Conditional Access so non-compliant devices lose access to Exchange Online, SharePoint and Teams.
License management and optimisation
Licence spend is the largest variable cost in M365. Assign licences via group-based licensing so joiner-mover-leaver is automatic. Monitor usage reports to downgrade unused E5 licences to E3, and reclaim licences from inactive accounts. Use the Graph PowerShell SDK to audit licence assignment at scale.
Connect-MgGraph -Scopes "User.Read.All","Directory.Read.All"
$skus = Get-MgSubscribedSku
foreach ($sku in $skus) {
$consumed = $sku.PrepaidUnits.Enabled - $sku.PrepaidUnits.Suspended
[PSCustomObject]@{
SkuPart = $sku.SkuPartNumber
Enabled = $sku.PrepaidUnits.Enabled
Consumed = ($sku.ConsumedUnits)
Available = $sku.PrepaidUnits.Enabled - $sku.ConsumedUnits
} | Format-Table -AutoSize
}Implementation sequence and best practices
A defensible rollout order that I have used repeatedly:
- Identity: Azure AD Connect, Seamless SSO, Conditional Access baseline
- Security: Defender preset policies, audit logging, MFA enforcement
- Exchange: Hybrid or migration, mail-flow hardening (SPF/DKIM/DMARC)
- SharePoint & OneDrive: hub architecture, sharing controls, quotas
- Teams: policies, templates, calling (if required)
- Endpoints: Intune enrolment, compliance, app protection
- Compliance: Purview retention, sensitivity labels, DLP
- Optimise: licence usage review, cost right-sizing
Lessons learned
- Land identity and security before migrating any workload
- Apply preset security policies before writing custom rules
- Use group-based licensing to automate joiner-mover-leaver
- Keep a break-glass admin outside Conditional Access, stored in a vault
- Never assume Microsoft backs up M365 data — add a third-party backup
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.