Qwalora is now a New Jersey Certified Small Business Enterprise, Category 1.What a set-aside actually sets aside

Tell us what you are working inside.

Contact us

|

Knowledge

·

6 min

Microsoft 365 went down today. Here is what to do, and what to claim.

Microsoft 365 went down today. Here is what to do, and what to claim.

Microsoft 365 went down today. Here is what to do, and what to claim.

On November 12, 2026, Outlook, Teams, SharePoint and Copilot stopped connecting across the Americas and beyond under Microsoft incident EX1550543. What to do while it is down, how the 99.9 percent SLA credit really works, and the three decisions to make before the next outage.

var(--variable-rpcX8dOAk)

On Thursday, November 12, 2026, Microsoft 365 failed in the middle of the workday. Outlook, Teams, SharePoint, Copilot and Defender XDR stopped connecting for organizations across the Americas and then in other regions. Microsoft is tracking it as incident EX1550543, with a related multi-service entry MO1550821. Updated Friday, November 13, 8:30 a.m. ET: The outage is in its second day and Microsoft has not declared it resolved. Overnight, servers it had restored stopped responding again once traffic returned. Early Friday it said servers were stable where a fix had been applied and that it was extending that fix region by region. It has not named a root cause and has committed to a Post-Incident Report once recovery is complete.

This page covers what happened, what to do while it is still down, how Microsoft's service credit actually works, and the decisions to make before the next one. If your organization runs on Microsoft 365, most of this applies to you whether or not your users noticed today.

What happened, in Microsoft's own words

  • Around 12:39 p.m. ET: reports of Outlook failures begin to spike.

  • 12:54 p.m. ET: Microsoft says it is investigating problems accessing Exchange Online mailboxes through multiple connection methods in the Americas, and soon after confirms the issue may affect Microsoft 365 connectivity in any region.

  • Early afternoon: Microsoft says part of its infrastructure is under elevated load across multiple regions, and begins redistributing connection traffic across its worldwide infrastructure.

  • Mid afternoon: Microsoft says the load is not caused by more traffic. A large number of servers became unexpectedly unavailable, pushing their load onto the rest. It paused all deployments and configuration changes, began restarting affected servers, and is testing a configuration change for servers failing automated health checks.

  • Around 4 p.m. ET: Microsoft says an alternative service health check method let a subset of servers return to service, and it begins applying that change broadly, with automated systems restarting servers that stop responding.

  • Early evening: Microsoft says its actions so far have not given the relief it expected. It has found that a core process on the affected servers becomes overwhelmed, causing the servers to stop responding. It reports no recent change correlated with the start of the incident.

  • Thursday evening: Microsoft returns a portion of the affected servers to service and shifts traffic to alternate routes where it can, describing the recovery as limited and gradual.

  • Around 7 p.m. ET Thursday: Microsoft says restored servers initially stay healthy but can stop responding again once they begin receiving traffic.

  • Overnight: Microsoft reports positive results from restarts, expands the fix, and scales up capacity to absorb the surge of reconnecting clients. It describes the overwhelmed component as a process on the affected servers that sets up secure connections.

  • Around 3 a.m. ET Friday: Microsoft says servers are stable where the fix has been applied and extends it region by region. Delayed inbound mail is being held for retry for up to 48 hours.

Microsoft executive Charles Lamanna has said there is no indication the outage resulted from malicious or cyber activity, and no published evidence links it to an attack. Treat it as a service failure, not as a sign that your own tenant was compromised.

By 2 p.m. ET, Downdetector had logged more than 97,000 Outlook reports. Affected connection methods include Outlook on the web, desktop Outlook (MAPI), mobile mail (Exchange ActiveSync) and the REST API, so switching apps does not help.

97,000+

Outlook reports on Downdetector by 2 p.m. ET

EX1550543

Microsoft incident ID to track in Service health

99.9%

Monthly uptime Microsoft commits to, per service

44 min

Full-tenant downtime that breaks 99.9% in an average month

Report count from WKYT citing Downdetector, November 12, 2026. Incident ID from Microsoft 365 Status. SLA figures from the Microsoft Online Services SLA as summarized by Office 365 for IT Pros; 0.1 percent of an average 30.4 day month is 43 minutes 49 seconds of downtime.

What to do right now

  1. Read your tenant's own status, not social media. In the Microsoft 365 admin center, open Health, then Service health, and find EX1550543 and MO1550821. If the admin center will not load, Microsoft publishes status at status.cloud.microsoft.

  2. Stop the reinstalls. This is a service incident. Reinstalling Outlook, resetting passwords or rebuilding profiles wastes the afternoon and creates new problems once service returns.

  3. Tell staff on a channel that is not Microsoft. If Outlook and Teams are both down, your usual announcement channel is down too. Use SMS, a phone tree or a personal email list, and say what you know and when you will update next.

  4. Warn staff about phishing. Large outages bring fake "restore your mailbox" and "re-verify your account" messages. Nobody should enter credentials from a link in the next few days.

  5. Start the record now. Write down when your users lost access, which services failed, how many users were affected, and when access returned. That record is what a service credit claim rests on.

  6. When Microsoft marks service restored, test before announcing. Check one mailbox in Outlook on the web first, then desktop, then mobile.

How the Microsoft 365 service credit scales

Downtime in a month, all users affected

Service credit on that service's fees

Under 43 min 49 sec

Under 43 min 49 sec

→

None, 99.9% met

More than 43 min 49 sec

More than 43 min 49 sec

→

25%

More than 7 hr 18 min

More than 7 hr 18 min

→

50%

More than 1 day 12 hr 31 min

More than 1 day 12 hr 31 min

→

100%

Will you get money back?

Microsoft's financially backed SLA commits to 99.9 percent uptime per service, per month. It is measured per named service, so Exchange Online, Teams and SharePoint Online are each assessed separately, and the downtime is measured across your users rather than the whole Microsoft cloud. Three things decide whether a credit is owed:

  • Duration in your tenant. An outage that hits every user for about 44 minutes in a month breaks 99.9 percent. One that hits a fraction of your users counts proportionally.

  • Which service. The credit applies to the fees for the affected service, not your whole Microsoft bill.

  • A claim. Credits are not automatic. Your administrator files through Microsoft support, with the record from step 5 above. Check the claim window in the current Online Services SLA and file early.

For a 50 seat organization the credit will be small. Its value is the evidence: it forces a written record of what one afternoon of downtime actually cost you, which is the number you need for the decisions below.

Three decisions to make before the next one

  1. Who can see Service health. Many small organizations have one global administrator, often a founder or an outside provider. Give at least two named people a role that can read Service health, using accounts that do not depend on a single person's phone.

  2. A communications channel that does not run on Microsoft 365. Keep a current staff contact list outside the tenant and test it twice a year. For client-facing teams, decide in advance where an outage notice goes: website banner, phone message or SMS.

  3. What work must continue without email. List the three or four processes that cannot stop for an afternoon, such as payroll approvals, client intake, a grant deadline or a council packet. Decide how each one continues: a shared phone line, a printed procedure, or a second system for that one function. Most organizations do not need a second email platform. They need to know which work stops and what replaces it for four hours.

Work this through with us

If today stopped your organization, tell us your seat count and what failed. We will look at who can see service health in your tenant, how you reached staff today, and which processes need a fallback, and tell you what we would change first.

Sources

  • Microsoft 365 Status (@MSFT365Status), incident updates for EX1550543 and MO1550821, November 12, 2026

  • TechRadar, "Microsoft Outlook is down for many: Here's what we know", live coverage, November 12, 2026

  • WKYT, "Nationwide Microsoft Outlook outage reported", November 12, 2026 (Downdetector report counts)

  • Variety, "Outlook Outage: Microsoft's Email Service Goes Down Nationwide", November 12, 2026 (timeline)

  • How-To Geek, "Microsoft Outlook outage leaves thousands struggling to access their email", November 12, 2026 (affected connection methods)

  • Office 365 for IT Pros, "Microsoft 365 Uptime Suffers Major Blip in First Quarter of Calendar Year 2026", April 22, 2026 (per-service, per-month SLA measurement)

  • Office 365 for IT Pros, SLA thresholds and service credit tiers under the Microsoft Online Services SLA

Disclosure

Qwalora resells cloud and software licensing through distribution and earns margin on products supplied, including Microsoft products through the Cloud Solution Provider program.

Qwalora takes no margin from a client on anything named in a report delivered to that client, during the engagement and for twelve months afterward.

No vendor named in this piece paid for it, reviewed it, or saw it before publication.

Qwalora resells Microsoft licenses and hardware and discloses its margin to clients.

Qwalora is now a New Jersey Certified Small Business Enterprise, Category 1.What a set-aside actually sets aside

Tell us what you are working inside.

Contact us