
Multifactor authentication is the single most effective step for protecting Microsoft 365 accounts — and the one teams with many mailboxes most often leave half-done. Outreach inboxes, shared team mailboxes, and admin accounts all need it, and each brings its own wrinkle. This guide covers Microsoft 365 MFA setup for organizations with multiple accounts: the three ways to turn MFA on, what Microsoft already requires, step-by-step setup, Conditional Access for larger tenants, how MFA works with sending tools connected by OAuth, and recovery.
One Compromised Mailbox Can Send Phishing Under Your Brand
💡 TL;DR
For Microsoft 365 MFA setup across many accounts, turn on security defaults (available in every tenant) or, with Entra ID P1 or P2, Conditional Access policies that require MFA for all users — not legacy per-user MFA. Use the Microsoft Authenticator app or phishing-resistant methods, keep two emergency access accounts, block legacy authentication, and connect sending tools by OAuth so mailboxes keep working after MFA is enforced. Microsoft already requires MFA for its admin portals.
Every outbound mailbox protected only by a password is an open door. If one is phished or its password is reused elsewhere, an attacker can send messages from your domain in minutes — to your prospects, your customers, or everyone in your contacts. Beyond the immediate damage, the domain's reputation can take weeks to recover.
Teams running cold email feel this more than most, because they have many mailboxes, often managed by several people. A single unprotected inbox is enough.
By the end of this, you'll know exactly how to complete Microsoft 365 MFA setup across every account without breaking the tools your team depends on.
Three Ways to Turn On MFA
Method | Availability | Control | Recommendation |
|---|---|---|---|
Security defaults | Every tenant (Microsoft Entra ID Free) | Simple, all-or-nothing baseline | Best for small and mid-size organizations |
Conditional Access | Microsoft Entra ID P1 or P2 (for example, Business Premium, E3, E5) | Fine-grained policies by user, app, location, and risk | Best for larger or more complex tenants |
Per-user MFA (legacy) | All tenants | Set user by user | Not recommended for new setups |
Security defaults and Conditional Access can't run at the same time — if you use Conditional Access, security defaults are turned off. Microsoft's MFA guidance for Microsoft 365 recommends security defaults or Conditional Access over per-user MFA.
Here's the advice we'd push back on: "Turn on per-user MFA for each mailbox as you create it." It works, but it's easy to miss accounts and it doesn't block legacy authentication. A tenant-wide approach covers every account, including ones created next month.
What Microsoft Already Requires
Microsoft has been making MFA mandatory for administrative access. It announced that from February 3, 2025 it would begin requiring MFA, in phases by tenant, for accounts signing in to the Microsoft 365 admin center, following similar requirements for the Azure portal, Microsoft Entra admin center, and Intune admin center.
Admins must have an MFA method registered before enforcement reaches their tenant.
Admin portal enforcement isn't the same as protecting mailboxes. It covers sign-ins to admin portals; ordinary mailbox sign-ins still need your own policy.
Automation accounts that sign in to admin tools need a plan — Microsoft recommends moving automation to workload identities rather than user accounts.
So even if your admins are already prompted for MFA, your Microsoft 365 MFA setup isn't finished until every mailbox is covered.
Setting Up Security Defaults Step by Step
Create two emergency access ("break-glass") accounts with long, unique passwords stored securely. You'll exclude them from Conditional Access later if you move to it.
Sign in to the Microsoft Entra admin center as at least a Security Administrator.
Go to Identity → Overview → Properties and select Manage security defaults.
Set security defaults to Enabled and save.
Ask users to register the Microsoft Authenticator app at their next sign-in; they have a short registration window.
Check the sign-in logs for accounts that haven't registered or that use legacy authentication.
Roll out during a quiet week and tell people in advance, so the first MFA prompt doesn't look like a phishing attempt.
Security defaults also block legacy authentication protocols, which can't do MFA. That's good for security — and it's why sending tools need to connect by OAuth.
Conditional Access for Many Accounts
With Entra ID P1 or P2, Conditional Access gives you more control. A sensible starting set of policies:
Policy | Applies to | Purpose |
|---|---|---|
Require MFA for all users | All users, excluding emergency access accounts | Baseline protection |
Block legacy authentication | All users | Close the protocols that bypass MFA |
Stronger methods for admins | Admin roles | Phishing-resistant methods such as passkeys or security keys |
Require MFA for admin portals | Admin roles | Matches Microsoft's own requirement |
Report-only first | New policies | Check impact before enforcing |
Exclude only what you must. Every exclusion is a gap, so keep a written list of excluded accounts and the reason for each, and review it quarterly.
Microsoft provides Conditional Access templates for these common cases in the Entra admin center. Start in report-only mode, review the sign-in logs, then switch to enforce.
MFA and Outreach Mailboxes Connected to Sending Tools
This is where cold email teams usually hesitate: will MFA break the mailboxes connected to Instantly, Smartlead, or Lemlist? Not if they connect by OAuth.
Connect each mailbox by OAuth — the tool opens Microsoft's sign-in, the user completes MFA once, and the tool receives a token.
Sending continues with the token. Users aren't prompted again for every email.
Reconnect when tokens are revoked — after a password reset, for example.
Avoid app passwords and Basic authentication. Microsoft is turning off Basic auth for SMTP AUTH by default — see Microsoft 365 OAuth setup.
Assign a clear owner for each outreach mailbox's MFA method, so it isn't tied to someone who leaves.
Litemail Microsoft 365 inboxes come with full admin access, so you can apply your own MFA policies, and support one-click OAuth export to common sending tools.
Choosing MFA Methods
Not all second factors are equally strong. Part of a good Microsoft 365 MFA setup is steering people toward the better ones.
Method | Strength | Notes |
|---|---|---|
Passkeys / FIDO2 security keys | Strongest — phishing-resistant | Ideal for admins and high-value accounts |
Microsoft Authenticator (push with number matching) | Strong | Good default for most users |
Authenticator one-time codes | Good | Useful backup method |
SMS or voice codes | Weakest of the common options | Better than nothing; avoid as the only method for admins |
Ask every user to register at least two methods so a lost phone doesn't become a help-desk emergency. For admins, require phishing-resistant methods through Conditional Access where you can.
For outreach mailboxes managed by a team, decide in writing whose device or key holds each mailbox's method. A Microsoft 365 MFA setup is only as reliable as its recovery plan — if the one person with the method leaves, you need a clean way to reset and reassign it. Plan that before you finish your Microsoft 365 MFA setup, not after someone is locked out.
Recovery and Common Problems
Problem | Likely cause | Fix |
|---|---|---|
User lost their phone | Only one MFA method registered | Admin resets MFA registration; encourage a second method |
Sending tool stopped working after MFA | Tool used Basic auth or an app password | Reconnect by OAuth |
Admins locked out | No emergency access accounts | Create two break-glass accounts and store credentials safely |
Some accounts never registered | Registration window missed | Check registration reports and follow up |
Departed employee still owns a mailbox's MFA | No ownership plan | Reset methods and reassign the mailbox on offboarding |
Review MFA registration and sign-in logs monthly, especially after adding batches of mailboxes. Access reviews are part of the routine in how to monitor email infrastructure health, and offboarding steps are in the account handover checklist.
Mailboxes you can secure your way — Litemail Microsoft 365 inboxes come with full admin access to apply your MFA and Conditional Access policies, OAuth export to your sending tool, SPF/DKIM/DMARC pre-configured, and dedicated US and EU IPs. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Microsoft 365 OAuth Setup · Encrypt External Emails in Microsoft 365 · Configure Mailboxes for Cold Email · Microsoft 365 Inboxes
Key Takeaways
For Microsoft 365 MFA setup across many accounts, use security defaults or Conditional Access — not legacy per-user MFA.
Security defaults are available in every tenant; Conditional Access needs Entra ID P1 or P2.
Microsoft began phasing in mandatory MFA for the Microsoft 365 admin center from February 3, 2025.
Keep two emergency access accounts and block legacy authentication.
Connect sending tools by OAuth so outreach mailboxes keep working after MFA.
Assign an owner for each mailbox's MFA method and review registration monthly.
Frequently Asked Questions
How do I set up MFA for all Microsoft 365 users?
Turn on security defaults in the Microsoft Entra admin center, or create a Conditional Access policy requiring MFA for all users if you have Entra ID P1 or P2.
What's the best method for Microsoft 365 MFA setup?
Security defaults for most small and mid-size organizations; Conditional Access for larger or more complex tenants. Avoid legacy per-user MFA for new setups.
Does Microsoft require MFA for admins?
Yes. Microsoft has phased in mandatory MFA for its admin portals, including the Microsoft 365 admin center from February 2025.
Will MFA break cold email tools connected to Microsoft 365?
Not if they connect by OAuth. The user completes MFA once during connection and the tool sends using a token.
Can I use security defaults and Conditional Access together?
No. Using Conditional Access turns off security defaults.
What are emergency access accounts?
Highly protected accounts kept for emergencies, such as admins being locked out. Microsoft recommends keeping two and excluding them from Conditional Access policies.
Can I apply my own MFA policies to Litemail mailboxes?
Yes. Litemail Microsoft 365 inboxes include full admin access, so you can apply your own MFA and Conditional Access policies.
Secure Every Outreach Mailbox
Litemail Microsoft 365 inboxes come with full admin access, OAuth export, SPF/DKIM/DMARC configured, dedicated US and EU IPs, and free domain replacement on pre-warmed plans.
Plans from $39/month · Microsoft 365 and Google Workspace · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Microsoft 365 Inboxes · Microsoft 365 Pre-Warmed Accounts · Cold Email Inbox Management for Agencies · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


