Explore

Microsoft 365 Outage, November 12โ€“14, 2026: How to Claim Your Service Credit Before December 31

โ€”

14 mins read
Microsoft 365 Outage Compensation

Home โ€บย Blog โ€บ

Microsoft 365 Outage, November 12โ€“14, 2026: How to Claim Your Service Credit Before December 31

What You'll Learn

Microsoft 365 email was unreliable for roughly 36 hours between November 12 and 14, 2026, and business customers covered by Microsoft’s Online Services SLA may be able to claim a service credit โ€” but Microsoft does not apply credits automatically, and requests for this outage must be submitted by December 31, 2026. If your Outlook stopped working last week, you weren’t imagining it and you weren’t alone. Many small business owners in Miami and South Florida have been asking us the same question: can we get anything back for that downtime? The short answer is possibly yes, but only if you ask. This article explains what happened, who qualifies, how much you could claim, and how to file.

Key Takeaways

  • Exchange Online mailbox access problems began at 12:54 p.m. ET on November 12 (incidents EX1550543 and MO1550821), and service was restored to remaining customers at 1:09 a.m. ET on November 14 โ€” about 36 hours.
  • Teams, OneDrive, SharePoint, and the Office apps recovered earlier, according to Microsoft; Exchange Online could not, which is why email was hit hardest.
  • Microsoft said the issue was technical and “not related to cyber or AI / agents.” Its preliminary post-incident report points to a latent networking gateway defect, higher-than-usual load, and reduced server capacity combining at peak US traffic.
  • Business customers covered by the Microsoft Online Services SLA may be eligible for a service credit; Microsoft 365 Personal and Family plans are not covered by the same business SLA.
  • A service credit reduces a future bill. It is not a cash refund and does not cover lost revenue, missed deadlines, or overtime.
  • If you buy Microsoft 365 through a Cloud Solution Provider (CSP) such as Q-Tech, Microsoft accepts credit requests only from that provider.
  • Claims for this outage must be submitted by December 31, 2026, and Microsoft keeps incident history for only 30 days, so gather your evidence now.

Quick Reference: The Outage and the Claim at a Glance

ItemDetail
Incident IDsEX1550543 (Exchange Online), MO1550821; TM1550488 if Teams was also affected for you
First reported12:54 p.m. ET, November 12, 2026
Restored to remaining customers1:09 a.m. ET, November 14, 2026 (~36 hours)
Microsoft’s stated causeTechnical issue โ€” latent gateway defect plus load and capacity conditions; not a cyberattack
Exchange Online SLA credit tiersBelow 99.9% uptime: 25% ยท Below 99%: 50% ยท Below 95%: 100% of the affected service’s monthly fee
Claim deadlineDecember 31, 2026
Who filesYou (direct purchase) or your provider (CSP purchase)

Note on this table: these details are drawn from Microsoft’s status posts, its preliminary post-incident report, and the published Online Services SLA for Exchange Online, layered with what we’ve seen helping small businesses in Miami and South Florida. Credits depend on Microsoft’s own user-minute calculation for your tenant, so treat the tiers as a guide to what’s possible, not a guaranteed outcome.

What Happened With Microsoft 365 on November 12 to 14?

Microsoft first reported problems at 12:54 p.m. Eastern Time on November 12, with Exchange Online mailbox access issues in the Americas under incident EX1550543. Thirteen minutes later, Microsoft said users in any region could be affected, and from 1:35 p.m. it also cited a second reference, MO1550821. Service was restored to the remaining customers and regions at 1:09 a.m. Eastern Time on November 14 โ€” about 36 hours from first report to all clear.

During that window, many businesses could not reliably open mailboxes or receive email on time. Microsoft said Teams, OneDrive, SharePoint, and the Office apps recovered earlier because they could move away from the faulty networking gateway. Exchange Online could not, which is why email took the hardest hit.

What Happened to Email Sent During the Outage

Microsoft extended the email timeout to 48 hours to help preserve delayed mail, and said it was still working through queued messages on November 13. Its posts describe mail being held and delivered late. Microsoft has not said whether any messages were lost or returned to senders โ€” which is why we’re telling clients to check now rather than assume everything arrived.

What Microsoft Says Caused It

On November 13, Microsoft said, “This was a technical issue not related to cyber or AI / agents.” On November 16, it released a preliminary post-incident report in the admin center under MO1550821 and EX1550543, and Charles Lamanna, Microsoft Executive Vice President for Copilot, Agents, and Platform, published an abridged version the same day.

The report names three factors that came together:

  • A latent defect from July. A fix prepared for Microsoft 365 networking gateway servers introduced a problem that left servers overwhelmed and unresponsive under certain load conditions. It rolled out worldwide over several weeks from July and ran for more than three months without an issue.
  • More load than usual. About 15 hours before the outage, Teams moved from Microsoft’s alternative networking gateway to the primary one, which also serves Exchange Online.
  • Less capacity than usual. At the same time, nearly 14% of gateway server capacity was out of service because of an unrelated issue from the previous day.

Together, those conditions triggered the defect during peak US traffic. As each server stopped responding, traffic moved to the next ones, which then failed in turn. In less than two hours the cascade reached the whole fleet, and at the lowest point more than 80% of the servers were unresponsive.

We share this detail because it matters for planning. This was not a hack and it was not an AI failure โ€” it was an infrastructure failure that spread because the usual partitions didn’t contain it. Even the largest cloud platforms can go down, and your business still needs a way to work when email does.

Can Your Business Claim Compensation?

For Exchange Online, Microsoft advertises a financially backed 99.9% uptime SLA. In Microsoft’s terms, compensation means a credit on your bill, and it has to be requested.

Who Qualifies

Business customers covered by the Microsoft Online Services SLA may be eligible when monthly uptime falls below the 99.9% threshold. That includes Microsoft 365 Business and Enterprise plans purchased from Microsoft, covering services in your plan such as Exchange Online, Teams, and SharePoint.

Microsoft 365 Personal and Family plans don’t have an SLA in the same way, so they don’t qualify for this credit. They can still ask Microsoft, but any response would be at Microsoft’s discretion rather than under the business SLA.

If you buy through an IT provider in the Microsoft Cloud Solution Provider program, such as Q-Tech, Microsoft accepts these requests only from that provider. You don’t file directly in that case โ€” your provider files for you.

How Much Credit Could You Get

Microsoft calculates entitlement with a user-minutes formula, multiplying minutes of downtime by the number of affected users to produce a monthly uptime percentage. For Exchange Online, the tiers are:

  • Below 99.9% availability (more than about 43 minutes of downtime in the month): 25% credit of that month’s applicable service fee
  • Below 99% availability (more than 7.2 hours): 50% credit
  • Below 95% availability (more than 36 hours): 100% credit

The credit applies only to the affected service, prorated by the duration of the outage โ€” not your whole Microsoft 365 plan. Because the calculation is based on user-minutes across your tenant for the whole month, the tier you land in depends on Microsoft’s own figures, not just the headline outage length.

What the Credit Is Not

A service credit is not a cash refund. It reduces a future bill. It does not cover lost revenue, missed deadlines, overtime, or third-party costs. Microsoft’s Master Services Agreement says credits are your sole and exclusive remedy under that agreement and are capped at the month’s fee for the affected service.

That doesn’t mean it isn’t worth claiming. For a small business, a 25% or 50% credit on Exchange Online for the month is still real money back on a service that wasn’t available when you needed it.

How to Claim Your Service Credit Before December 31

Claims for this November outage must be submitted by December 31, 2026. For services other than Azure, the deadline is within one month from the end of the billing month in which the incident occurred.

Don’t wait until late December. Gather proof now, while the incident history is still in your admin center โ€” Microsoft says it keeps the history of incidents that affected your organization for 30 days.

If You Buy Microsoft Directly

Go to the Microsoft 365 admin center, then Health, then Service health, and open the issue history. Save a copy of the preliminary report under MO1550821 and EX1550543 before it disappears. Write down when the outage started and ended for you, how many people were affected, and which services were affected โ€” email only, or Teams too. Keep copies of any support tickets or messages you sent during the outage.

Then open a support ticket titled as a Service Level Agreement credit request, and include your tenant ID, the incident IDs, and proof of impact, along with an email from your company domain asking for the credit.

If You Buy Through an IT Provider Like Q-Tech Inc.

Send your provider a short email from your company address asking them to request the credit for EX1550543 and MO1550821. Include your tenant ID, your outage window, how many users were affected, and what you couldn’t do during that time. If we manage your Microsoft 365, we can check who the provider of record is, pull the service health history with you, and file the request together.

What to Gather First

  • Your tenant ID
  • Incident IDs EX1550543 and MO1550821, plus TM1550488 if Teams was also affected for you
  • Your outage start and end times, in your own words, with dates
  • How many users were affected
  • Which services were affected
  • Any undeliverable notices, support tickets, or client messages about delayed email
  • An email from your company domain asking for the credit

A warning from this week: expect phishing emails offering compensation for the outage. Under Microsoft’s process, the claim goes through your admin or your provider, not through a link in an unsolicited message. Don’t click a compensation link in an email you didn’t expect โ€” if you’re unsure, forward it to your IT team first.

Three Checks to Do This Week

Do these now, even if you don’t plan to claim a credit. They take about five minutes and catch the real business risk from delayed mail.

  1. Search your inbox for undeliverable notices received between November 12 and 14, and resend those messages.
  2. Confirm anything time-sensitive arrived. If you were expecting a signed contract, payment confirmation, or quote in that window, ask the sender to confirm it was delivered.
  3. Request fresh verification codes or password reset links instead of using ones that arrived late โ€” they may have expired.

When email goes down for a day and a half, it isn’t just an IT problem. It’s missed quotes, delayed invoices, clients waiting for a reply, and a team that can’t move work forward. That’s why we’re writing this now, while the deadline is still open.

What to Do Before the Next Outage

The useful lessons from these 36 hours are practical, not technical:

  • Bookmark the public status page at status.cloud.microsoft. During the incident, Microsoft pointed users there when the admin center wasn’t available, and the page offers an RSS feed.
  • Turn on service health emails. In the admin center, go to Health, then Service health, then Customize, then Email. This sends incident notifications to up to two addresses per admin โ€” use at least one address that isn’t on Microsoft 365, so you still get the alert when Microsoft 365 is down.
  • Agree on a fallback channel now. Decide how your team and your three most important clients will reach each other when email is down โ€” a phone list, or a messaging app that doesn’t depend on the same provider.
  • Know who you buy from. Whether your licenses come from Microsoft directly or from a provider decides who files a credit claim, and the deadline won’t wait.

A resilient setup also depends on the layers around email. Our managed IT services in Miami team helps businesses plan for exactly this kind of provider outage, and our cybersecurity services in Miami team helps with the phishing risk that tends to follow a high-profile incident like this one.

Your Microsoft 365 Outage Claim Checklist

  • Note your outage window, how many users were affected, and which services were affected
  • Save your tenant ID and incident IDs EX1550543 and MO1550821 (plus TM1550488 if Teams was affected)
  • Save a copy of the preliminary report from Health, then Service health, in the Microsoft 365 admin center
  • Keep copies of support tickets, undeliverable notices, and client messages about delayed email
  • If you buy Microsoft directly, open a support ticket titled “Service Level Agreement credit request”
  • If you buy through an IT provider like Q-Tech, send your provider a short email from your company address asking them to request the credit
  • File before December 31, 2026
  • Search for undeliverable notices from November 12 to 14 and resend those messages
  • Confirm time-sensitive mail arrived, and request new verification codes or reset links rather than using late ones
  • Bookmark status.cloud.microsoft, turn on service health emails, and agree on a fallback channel for next time

Our Take at Q-Tech Inc.

In our experience, most small businesses don’t claim service credits โ€” not because they don’t qualify, but because no one tells them they have to ask, or because the deadline passes while they’re busy catching up after the outage. That’s understandable. When email comes back, the priority is clearing the backlog. But this claim is worth an hour of your time, especially if email is core to how you serve clients.

If you’re a Q-Tech client and you were affected, reach out. We can check your Microsoft 365 setup, confirm whether your plan qualifies, help you gather the service health history, and file the request with you before December 31. If you’re not a client yet, use the checklist above to file yourself, and keep the fallback plan for next time. A 36-hour outage is rare, but a plan for when email is down shouldn’t be.

Need Help Claiming or Checking Your Setup?

Book a free 15-minute consultation with Q-Tech Inc. No obligation, Miami-based, bilingual team. You can also reach us at [email protected] or (954) 530-6029.

Sources

  • Microsoft 365 Status, incident thread EX1550543 and MO1550821, November 12โ€“14, 2026
  • Microsoft statement on the incident, November 13, 2026
  • Charles Lamanna, abridged root cause of the November 12 incident, November 16, 2026
  • Microsoft service health status, status.cloud.microsoft
  • Microsoft Learn, Request a credit from Microsoft, Partner Center
  • Microsoft Service Level Agreements for Online Services, Exchange Online section
  • Firstpost via Inshorts, “What compensation can Microsoft 365 users claim after outage?” by Jessica Rajan
  • Bluehatweb summary, “Why was Outlook down? Microsoft 365 outage cause and compensation,” November 14, 2026

Editorial note: this article is based on Microsoft’s status posts for EX1550543 and MO1550821, Microsoft’s preliminary post-incident report released November 16, 2026, and the Microsoft Online Services SLA for Exchange Online. No client case study is included. We don’t publish fabricated case studies.

FAQ

Q: How long was the Microsoft 365 outage in November 2026?

A: About 36 hours, from Microsoft’s first report at 12:54 p.m. ET on November 12 to restoration for remaining customers at 1:09 a.m. ET on November 14. Exchange Online email was the most affected service.

Q: Was the Microsoft 365 outage caused by a cyberattack?

A: No. Microsoft said it was a technical issue not related to cyber or AI agents, and its preliminary report describes a latent gateway defect combined with higher load and reduced capacity.

Q: Can I get compensation for the Microsoft 365 outage?

A: Business customers covered by the Online Services SLA may be eligible for a service credit on the affected service, but credits must be requested, aren’t automatic, and aren’t cash refunds.

Q: What is the deadline to claim a Microsoft 365 service credit for this outage?

A: December 31, 2026. Gather your evidence now, since Microsoft keeps incident history for 30 days.

Q: I buy Microsoft 365 through an IT provider. Can I claim directly?

A: No. For Cloud Solution Provider purchases, Microsoft accepts credit requests only from the provider, so ask your provider to file on your behalf.

What You'll Learn

Ready to Talk?

Book your free 15-minute consultation โ€” no obligation.

Subscribe to our Newsletter

Stay informed with Q-Techโ€™s latest insights! Subscribe to our newsletter for updates on IT solutions, Digital Marketing, and business innovations.

Still troubleshooting the
same issues every month?

In a quick 15-minute call, our IT team will look at what is slowing you down and map a clear path forward. No prep needed on your end.

15 MINUTES. REAL ANSWERS. A CLEAR NEXT STEP YOU CAN ACT ON TODAY.

Still troubleshooting the
same issues every month?

In a quick 15-minute call, our IT team will look at what is slowing you down and map a clear path forward. No prep needed on your end.

15 MINUTES. REAL ANSWERS. A CLEAR NEXT STEP YOU CAN ACT ON TODAY.

About Andres Quintero | Q-Tech Inc's Author

Andres Quintero is the founder, President, and CEO of Q-Tech Inc., an IT services company serving businesses across Miami-Dade and Broward County, Florida. He leads Q-Techโ€™s strategy across managed IT services, cybersecurity, cloud services, network reliability, and IT automation, helping organizations keep their systems secure, dependable, and ready to grow. Since founding Q-Tech in 2008, Andres has spent more than 15 years building practical, business-focused technology strategies for companies across healthcare, legal, real estate, accounting, and other industries. He has written about IT and cybersecurity trends and hosts The Q-Tech Connection Podcast, where he shares practical insights on emerging technology, cybersecurity, and business leadership.

Enjoying this post?

Get more like it

Marketing Consultation Request

Enter your details below and select your preferred date and time for your free consultation. A confirmation email will be sent; please check your spam folder if it does not appear in your inbox.

IT Consultation Request

Enter your details below and select your preferred date and time for your free consultation. A confirmation email will be sent; please check your spam folder if it does not appear in your inbox.