Microsoft 365 email down. Here's why and how to get it back.
If your team can't send or receive email, every hour costs you. I'm a USAF veteran with CompTIA Security+. Below is the actual triage sequence I run when M365 email goes down. Try the steps, and if you're still stuck after step 4, call (208) 918-0636.
Symptoms that brought you here
- ✓ Sent emails sit in the Outbox and never leave
- ✓ "Outlook couldn't connect to the server" / disconnected status
- ✓ "Mailbox unavailable" or "your mailbox is almost full"
- ✓ Quota exceeded, can't send or receive
- ✓ MFA prompt loops repeatedly and Outlook never authenticates
- ✓ "Need password" prompt that won't accept the password
- ✓ New email setup fails with "we couldn't find any settings"
- ✓ External senders getting bouncebacks but you don't see anything
The 6 most common causes
Most M365 email outages trace to one of these. Microsoft service outage is rarer than people assume, but always check it first.
Microsoft service outage
It happens. When it does, it's usually regional. Always check status.office.com first. If Microsoft has a posted incident affecting Exchange Online or Outlook, no amount of local troubleshooting will fix it. Sit tight, monitor the incident, and let your team know what's going on.
DNS / MX records wrong
If MX, autodiscover, SPF, or the SRV records for your domain were changed (or were never right to begin with), inbound mail bounces and Outlook can't auto-configure. Common after domain transfers, registrar moves, or website rebuilds where someone touched DNS without realizing email lived there too.
License expired or removed
If a user's M365 license expires, gets unassigned, or the subscription billing fails, the mailbox is removed from Exchange Online and the user starts getting "mailbox unavailable" errors. It's common during ownership changes, credit-card-on-file expirations, and accidental admin removals.
MFA / token issue
Stale MFA tokens, broken Modern Authentication settings, an Authenticator app that's been reinstalled without re-enrollment. Any of these can put a user in an MFA loop where Outlook prompts forever and never authenticates. Often fixed by clearing cached credentials and re-registering MFA.
Conditional Access policy
A well-meaning admin enables a Conditional Access policy ("require compliant device" or "block legacy authentication") and suddenly half the office can't access email. CA policies are powerful and unforgiving. They need to be tested in report-only mode before enforcement.
Mailbox at quota
50 GB sounds like a lot until 10 years of attachments fills it. Once a mailbox hits quota, sending stops and (eventually) receiving stops. The fix is an archive policy, mailbox cleanup, or upgrading to an Exchange plan with a larger mailbox. I do this without losing email history.
4-step triage sequence
Check status.office.com
Open status.office.com in any browser (no login required). If Microsoft has an active incident affecting Exchange Online, Outlook, or Authentication, you've found your answer in under a minute. Bookmark this. It should be the first thing you check, every time.
Try Outlook on the web
Go to outlook.office.com and try logging in with the affected user's credentials. If OWA works fine, the issue is your local Outlook client (cache, profile, MFA token, network), not the M365 service. If OWA also fails, the issue is service-side or account-side and your desktop Outlook is a red herring.
Run testconnectivity.microsoft.com
Microsoft's free Remote Connectivity Analyzer can simulate Outlook autodiscover, inbound SMTP, and Exchange ActiveSync. Run the "Office 365 / Exchange Online" tests for the affected mailbox. The output points directly at DNS issues, autodiscover misconfiguration, or authentication failures with specific error codes.
Check the user in admin.microsoft.com
Log into the Microsoft 365 admin center, find the affected user, and verify: the user is not blocked, has an active license, has the Exchange Online mailbox provisioned, and is not in a Conditional Access policy that's breaking access. Three out of four "email broken" tickets get diagnosed in this one screen.
When to stop troubleshooting and call
Email is mission-critical. Past a certain point, fishing in the admin center for hours costs more than the call. Pick up the phone if any of the following are true:
- ✓ Outage longer than 1 hour with no clear cause
- ✓ Multiple users affected at the same time
- ✓ Mission-critical email blocked (legal, medical, billing)
- ✓ You suspect a configuration mistake but don't know which
- ✓ You're seeing weird MFA / Conditional Access prompts
- ✓ testconnectivity.microsoft.com is showing failures you don't understand
- ✓ Microsoft has a ticket open and you need someone fluent to drive it
What Idaho Proper IT does
Hourly pricing
$250/hr
emergency rate after hours · 1-hour minimum · scope quote usually same day
Nationwide remote support. You don't have to be in Boise for me to fix M365.