All Resources
Microsoft 365

Microsoft 365 Business Setup Checklist for Small Businesses

A new Microsoft 365 tenant works out of the box, but "works" and "set up correctly" are not the same thing. Most of the security incidents and licensing waste we clean up in Greater Sudbury businesses trace back to shortcuts taken during initial setup. This checklist walks through the full sequence in order, so nothing gets skipped or bolted on after the fact.

Published August 9, 2026 Updated August 9, 2026 10 min read By Joshua Arimoro Greater Sudbury & Ontario
The short answer

A proper Microsoft 365 business setup follows a fixed sequence: verify your domain and DNS, build identity and groups, enforce MFA and baseline conditional access, assign licences deliberately, harden Exchange Online and publish SPF/DKIM/DMARC, structure SharePoint and OneDrive, set Teams governance, enrol devices, configure retention, add third-party backup, and document an offboarding process. Skipping or reordering these steps is the most common cause of later security and licensing problems.

Phase 1: Domain and DNS

Everything in Microsoft 365 hangs off your verified domain, so get this right before creating a single mailbox.

  1. Add and verify your custom domain in the Microsoft 365 admin centre.
  2. Set the custom domain, not the onmicrosoft.com domain, as the default for new users.
  3. Update MX records to point mail flow at Exchange Online.
  4. Add the Autodiscover CNAME so Outlook and mobile mail clients configure automatically.
  5. Keep the onmicrosoft.com domain as a backup reference, never delete it.

Phase 2: Identity and groups

Identity is the security perimeter in a cloud-first business, more so than any firewall. Build the structure before you add users, not after. See our guide on Microsoft 365 security best practices for the reasoning behind identity-first design.

  • Create a naming convention for usernames and display names before onboarding staff
  • Build Microsoft 365 groups or security groups that mirror departments, not the org chart from three reorgs ago
  • Set up dynamic groups where membership should follow attributes such as department or location
  • Assign no more than two or three Global Administrator accounts, each dedicated to admin tasks only

Phase 3: MFA and conditional access basics

Multi-factor authentication is non-negotiable in 2026, and Conditional Access is what turns MFA from a blunt instrument into a policy engine. Read how MFA protects your business for the underlying threat model.

  • Require MFA for every licensed user, with no standing exceptions for executives
  • Use the Microsoft Authenticator app with number matching rather than SMS where possible
  • Block legacy authentication protocols tenant-wide
  • Require MFA for all admin role sign-ins regardless of location
  • Build a baseline Conditional Access policy requiring compliant or hybrid-joined devices for access to SharePoint and Exchange

Setting up a new Microsoft 365 tenant?

We build new tenants correctly the first time, following this exact sequence, so you are not retrofitting security later.

Talk to Us About Setup

Phase 4: Licence assignment

Licence sprawl starts on day one when everyone gets the same SKU regardless of role. Assign deliberately, and revisit quarterly. Our Microsoft 365 Business Premium comparison explains what each tier actually includes.

  • Match licence tier to role, not habit: front-line staff rarely need the same SKU as management
  • Use group-based licensing so new starters inherit the correct licence automatically
  • Track unused and dormant licences monthly

Phase 5: Exchange Online settings

  • Set a sensible default mailbox retention and litigation hold policy where required
  • Enable mailbox audit logging tenant-wide
  • Configure shared mailboxes for departmental inboxes instead of shared logins
  • Set external sender warnings so staff can spot impersonation at a glance
  • Disable auto-forwarding to external domains by default

Phase 6: Email authentication (SPF, DKIM, DMARC)

Without these three DNS records, anyone can forge an email that appears to come from your domain. This is foundational for the anti-phishing work covered in securing business email from phishing.

  1. Publish an SPF record listing Microsoft 365 and any other legitimate senders (marketing tools, invoicing platforms).
  2. Enable DKIM signing for your domain in the Microsoft 365 admin centre.
  3. Publish a DMARC record starting at p=none to monitor without blocking.
  4. Review DMARC reports for two to four weeks, then move to p=quarantine.
  5. Move to p=reject once you're confident all legitimate senders are authenticated.

Phase 7: SharePoint and OneDrive structure

Set the structure before anyone starts saving files, because migrating a messy structure later is far more disruptive than building it correctly up front.

  • Create a SharePoint site per department or project, not one giant document library
  • Restrict external sharing to authenticated guests by default, not anyone-with-the-link
  • Set OneDrive as the default for personal working files, with SharePoint for shared and departmental documents
  • Apply sensitivity labels to documents containing financial, HR, or client data

Phase 8: Teams governance

  • Decide who can create new Teams, rather than leaving it open to everyone
  • Set a naming convention and an expiration policy for project-based Teams
  • Archive or delete Teams that have gone dormant instead of letting them accumulate
  • Control guest access at the tenant level before enabling it broadly

Phase 9: Device enrolment

Every device that touches company data should be enrolled and managed, whether company-owned or personal. See why modern businesses need endpoint management for the full case, and consider mobile device management for phones and tablets.

  • Enrol Windows devices in Intune via automatic enrolment or Autopilot
  • Enforce disk encryption, screen lock, and minimum OS version compliance
  • Set app protection policies for personal phones accessing company email
  • Build a compliance policy that feeds into Conditional Access device checks

Phase 10: Retention and backup

Retention policies and backup solve different problems and both are required. Retention governs how long data is kept for compliance; backup protects against deletion, corruption, and ransomware. Native Microsoft 365 retention is not a backup, a point we cover in depth in why Microsoft 365 backup is necessary.

  • Set retention policies for Exchange, SharePoint, and Teams based on your compliance obligations
  • Deploy a dedicated third-party SaaS backup solution covering Exchange, OneDrive, SharePoint, and Teams
  • Test a restore at least once after initial setup to confirm the backup actually works

Phase 11: Offboarding process

A documented offboarding process closes the single most common security gap we find in growing businesses: former employees who still have active access.

  1. Disable the account sign-in immediately upon departure, before removing licences.
  2. Convert the mailbox to a shared mailbox if ongoing access to correspondence is needed.
  3. Revoke all active sessions and refresh tokens.
  4. Transfer OneDrive file ownership to a manager or successor.
  5. Remove the user from all groups, Teams, and distribution lists.
  6. Reclaim the licence and reassign or retire it.
  7. Document the offboarding date and actions taken for audit purposes.

Setup checklist at a glance

Microsoft 365 setup phases and key actions
PhaseKey actionWhy it matters
Domain and DNSVerify domain, update MX and AutodiscoverEverything else depends on this
IdentityNaming convention, groups, limited Global AdminsReduces attack surface from day one
MFA and Conditional AccessMFA for all users, block legacy authStops the majority of account takeovers
LicensingAssign by role, use group-based licensingPrevents licence sprawl and waste
Exchange OnlineAudit logging, shared mailboxes, no auto-forwardVisibility and control over mail flow
Email authenticationSPF, DKIM, DMARC to p=rejectPrevents domain spoofing
SharePoint and OneDriveSite-per-department, restricted external sharingPrevents data sprawl and leaks
TeamsCreation controls, naming, expirationPrevents Teams sprawl
DevicesEnrol in Intune, enforce complianceExtends control to endpoints
Retention and backupRetention policies plus third-party backupCompliance and disaster recovery
OffboardingDocumented, immediate, repeatable processCloses access gaps at departure

Sources and further reading

Frequently asked questions

How long does a proper Microsoft 365 setup take?

For a business with 10 to 50 users, a full setup following this checklist typically takes one to three weeks, including a testing period before staff are fully migrated.

Can I skip Conditional Access if I have MFA?

No. MFA confirms who is signing in, while Conditional Access controls the conditions under which that sign-in is allowed. Together they cover far more scenarios than either alone.

Do I need SharePoint if I already use OneDrive?

Yes, for anything shared. OneDrive is designed for an individual's personal working files, while SharePoint is built for documents that a team or department needs to access and manage together.

Is native Microsoft 365 retention the same as backup?

No. Retention policies preserve data for compliance windows but are not designed for point-in-time recovery. A dedicated backup product is required to fully protect against deletion or ransomware.

What is the most commonly skipped step in Microsoft 365 setup?

DMARC enforcement. Many tenants publish an SPF record and stop there, leaving DMARC at p=none indefinitely, which does nothing to stop domain spoofing.

About the author

Joshua Arimoro

Joshua Arimoro is the Principal Consultant at Nickel City Tech Solutions, a managed IT and cybersecurity provider based in Lively, Ontario, serving businesses across Greater Sudbury and Northern Ontario. He works hands-on with Microsoft 365, server and network infrastructure, endpoint management, and backup and recovery for small and mid-sized organisations.

More about our team

Get your Microsoft 365 tenant set up right the first time

We handle new tenant builds and migrations for Northern Ontario businesses, following a documented setup process from domain verification through offboarding.

Technologies mentioned in this article

See what we support around each platform on our supported technologies hub.

Keep exploring

Related services, locations, and resources

Related services

Related resources