Have you opened Outlook this week, waited for new messages, and then watched nothing arrive? Or tried to send an invoice and the message sat in Outbox far longer than usual?
You are not imagining it. Many businesses saw delayed or missing Outlook mail during a Microsoft 365 disruption that started late August 2026 and stretched into this week. Exchange Online, sign-in, search, and even Teams or SharePoint were affected for some customers. The instinct is to assume your domain, DNS, or hosting is broken. Often it is not. The first job is to stay calm and figure out whose problem it actually is.
Why this feels like “our email is down”
When Microsoft 365 has trouble, it usually looks like this:
- Messages send but never show up for the other person
- Incoming mail is hours late or missing
- Outlook asks you to sign in again and again
- Search inside the mailbox is empty or frozen
- The website and other email on the same domain still work fine
That last point matters. If your website loads and a different mailbox on the same domain still works, the domain itself is probably healthy. The delay is more likely inside Microsoft’s service.
Step 1: Check official status before you change anything
Do this before you edit DNS, passwords, or Outlook settings.
- Open the Microsoft 365 admin center at admin.microsoft.com (an admin login is needed).
- Go to Health, then Service health.
- Look at Exchange Online and any listed incident. Recent events were tracked as a core authentication configuration problem that also touched other Microsoft 365 apps.
- If you cannot get into the admin center, check the public Microsoft 365 Status account on X (@MSFT365Status) and trusted outage trackers.
- Ask one or two people outside your office whether they can send mail to you right now.
If Microsoft shows an active incident and other companies are reporting the same delays, pause. Do not start changing MX records, SPF, or nameservers in a hurry. A clear picture of how those pieces connect is in Your Domain Name, DNS and Email – The 2026 Survival Guide.
Step 2: Tell a provider outage from a local problem
Use this simple split.
It is more likely a Microsoft outage when:
- Several mailboxes fail at the same time
- Outlook on the web and the desktop app both struggle
- Teams, OneDrive, or the admin center are also odd
- Official status pages mention Exchange Online or authentication
- Your website still loads and DNS looks unchanged
It is more likely on your side (domain, DNS, or one mailbox) when:
- Only one person is affected
- Mail works in Outlook on the web but not in one desktop profile
- New messages bounce with errors about “no mail server,” “does not exist,” or authentication failure
- You recently moved the domain, changed nameservers, or edited MX, SPF, DKIM, or DMARC
- Other Microsoft 365 apps work, but this one mailbox does not
If the trouble started right after a domain or DNS change, review Your Domain Name, DNS and Email – The 2026 Survival Guide and Understanding Microsoft 365 Plans and Requirements. If mail started landing in spam after a new address or a move, see Why New Business Email Addresses Sometimes Go Straight to Spam (And How to Fix It).
Step 3: What not to change while mail is delayed
Panic edits create a second outage on top of the first.
Avoid these until you know the cause:
- Deleting or rewriting MX records
- Pointing mail to a different host “just to test”
- Removing SPF, DKIM, or DMARC records
- Changing nameservers
- Creating new forwarding rules that send everything to a personal Gmail address
- Installing random Outlook “repair” tools from search ads
Safe things you can do:
- Restart Outlook or try Outlook on the web in a private browser window
- Confirm you can still sign in
- Note the exact time mail stopped and any bounce text
- Ask customers to wait or use a backup contact method
- Take a screenshot of Service health if an incident is listed
If you already changed DNS this week, stop and write down what you changed. That list helps us fix it later. Also leave SPF alone unless you know an old include is wrong. Cleaning those records is a planned task, not an emergency one. See Cleaning Up Old SMTP Services and SPF Records.
Step 4: Keep talking to customers while mail is slow
You still need a way to take orders and answer people.
Practical options while Exchange Online is catching up:
- Use a published phone number or a contact form that does not depend on that mailbox
- Have a second person check a working mailbox if you have more than one service
- Post a short note on your website or social accounts: “Email may be delayed. Please call or text.”
- Save important outgoing messages as drafts and send them after status returns to normal
- Do not blast the same message over and over. That can hurt reputation once the service recovers
If you rely on contact forms in WordPress, make sure those forms send from a real mailbox, not a noreply address. That is a separate deliverability issue. After mail is moving again, our Email Security Checklist for Small Businesses is a good quarterly review.
Step 5: After Microsoft says it is recovering
Outages often clear unevenly. Mail flow may return before search does.
When status improves:
- Give it time. Delayed messages can arrive in a bunch.
- Check Sent Items and Deleted Items so nothing was stuck or filtered.
- Send one test message to a Gmail or other outside address you control.
- Confirm SPF, DKIM, and DMARC still look the same as before. Do not rebuild them unless they are actually missing.
- If one mailbox still fails after everyone else is fine, treat that as a local profile or account issue.
Walk through the records with 5 Essential Tips for Mastering SPF, DKIM, and DMARC in 2026 and Google and Microsoft’s Sender Guidelines in Plain English. If bounces continue to Gmail, Yahoo, or AOL after the outage, use Emails bouncing back in Gmail/Yahoo/AOL? Here’s what’s going on.
If the “outage” turns out to be a suspicious sign-in or a mailbox that started forwarding on its own, treat it as a security event. Start with What to Do If an Employee Clicks a Phishing Link.
Quick first-check list
- Look at Microsoft 365 Service health and @MSFT365Status
- See if more than one mailbox or app is affected
- Confirm the website and DNS still look normal
- Do not edit MX or authentication records in a rush
- Give customers a phone or form backup
- Test one outbound message after Microsoft reports recovery
- Save bounce messages and times if the problem continues
How KartHost helps if the problem is actually on your domain
When the outage is on Microsoft’s side, the honest answer is wait and keep customers informed. When the problem is yours, it is usually DNS, a recent domain move, or a mailbox that never finished setup.
If your domain and DNS are with KartHost, our team can review MX, SPF, DKIM, and DMARC against the Microsoft 365 values that should be there. We look for leftover records from an old host, a broken include in SPF, or a nameserver change that never copied mail settings. That review is the same work we describe in Emails bouncing back in Gmail/Yahoo/AOL? Here’s what’s going on.
Your website, domain, and inbox are supposed to work together. When Microsoft 365 hiccups, a short checklist keeps you from breaking the parts that were still healthy. If you want a second set of eyes on the records after this week’s delays, we are here to walk through them with you.
