Microsoft outage November 2026

Question

Microsoft outage November 2026

Nikademus 0

MS services still down since 2:30pm EST. It's 8pm. Someone's getting fired over this. :)

Nikademus 0 Reputation points

2026-11-13T00:53:27.0166667+00:00

Awesome. Someone or Somebodys are getting fired over this latest outage. five and a half hours and counting. complete outage. Way to go Microsoft.
E-Roc 0 Reputation points

2026-11-13T00:57:22.5166667+00:00

i'm having the same issues, still down at 6:57 PM central time
David Rasbold 0 Reputation points

2026-11-13T11:34:52.8466667+00:00

Nothing is working... thank goodness I have some gmail accounts, and I don't need 365 to access my office files which are all saved on hard drive.
Joel Quispe Mamani 0 Reputation points

2026-11-13T13:12:58.2433333+00:00

Viernes 13, 9 am aun seguimos sin servicio :(
JOE DESROSIERS 0 Reputation points

2026-11-13T14:29:59.48+00:00

Any updates this morning that are not posted on the outage page? Is this Crowdstrike related?
David Rasbold 0 Reputation points

2026-11-13T18:09:06.26+00:00

Thankfully, access is back at 100%. No problems. It does bring up the concerning reality that we're far too reliant on technology. I couldn't do anything yesterday. That's probably not a good thing...

2 answers

Your answer

Nikademus 0 Reputation points

2026-11-13T00:53:27.0166667+00:00

Awesome. Someone or Somebodys are getting fired over this latest outage. five and a half hours and counting. complete outage. Way to go Microsoft.
E-Roc 0 Reputation points

2026-11-13T00:57:22.5166667+00:00

i'm having the same issues, still down at 6:57 PM central time
David Rasbold 0 Reputation points

2026-11-13T11:34:52.8466667+00:00

Nothing is working... thank goodness I have some gmail accounts, and I don't need 365 to access my office files which are all saved on hard drive.
Joel Quispe Mamani 0 Reputation points

2026-11-13T13:12:58.2433333+00:00

Viernes 13, 9 am aun seguimos sin servicio :(
JOE DESROSIERS 0 Reputation points

2026-11-13T14:29:59.48+00:00

Any updates this morning that are not posted on the outage page? Is this Crowdstrike related?
David Rasbold 0 Reputation points

2026-11-13T18:09:06.26+00:00

Thankfully, access is back at 100%. No problems. It does bring up the concerning reality that we're far too reliant on technology. I couldn't do anything yesterday. That's probably not a good thing...

Answer 1

Vikki-T 14,290 Microsoft External Staff Moderator

Hi Nikademus,

I’m sorry to hear that you are having trouble with the Microsoft service.

Microsoft is currently reporting a global outage affecting some of its services. Since Copilot relies on online services to load, it may be related to what you are seeing, although this cannot be confirmed from your description alone. You can monitor the current status here: Service Health Status.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. My role is limited to providing technical guidance on reported issues, requests, or ideas.

Thank you so much for your understanding and I look forward to your reply.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Whispering Clouds 0 Reputation points

2026-11-13T12:10:51.4066667+00:00

Thanks Vikki that matches what I measured from outside, and the detail is worth adding because the failure isn't uniform, which is why individual reports look random.

I probed the mailbox frontends from 11 regions this morning. About 70% of the addresses DNS was still handing out accepted nothing on 443, while the edge in front of them served at 0.0% error and identity, Teams and Office were clean in every region. Same probe, same minute: one address answers in 7 ms, the next two time out. Which server you land on predicts it; your country doesn't.

That's the practical part for anyone in this thread retrying, or switching network, will sometimes work and sometimes not, and it isn't your config. Method, raw data and the falsification test here:

https://github.com/hallowenhappy05-commits/Microsoft_Outage

Not a root cause, just a timestamped record of what the public edge did.
Whispering Clouds 0 Reputation points

2026-11-13T17:41:42.7933333+00:00

Thanks Vikki that matches what I measured from outside, and the detail is worth adding because the failure isn't uniform, which is why individual reports look random.

I probed the mailbox frontends from 11 regions this morning. About 70% of the addresses DNS was still handing out accepted nothing on 443, while the edge in front of them served at 0.0% error and identity, Teams and Office were clean in every region. Same probe, same minute: one address answers in 7 ms, the next two time out. Which server you land on predicts it; your country doesn't.

That's the practical part for anyone in this thread retrying, or switching network, will sometimes work and sometimes not, and it isn't your config. Method, raw data and the falsification test here:

https://github.com/hallowenhappy05-commits/Microsoft_Outage

Not a root cause, just a timestamped record of what the public edge did.

Answer 2

Microsoft is reporting an active Microsoft 365 service degradation on November 13, 2026, and customers should monitor Microsoft 365 admin center → Health → Service health for tenant-specific recovery updates rather than troubleshoot individual devices.

Microsoft’s public status feed reports that a core process on affected servers became overwhelmed, causing servers to stop responding and reducing service capacity. Mitigation includes isolating infrastructure, restarting affected components, rerouting traffic, and gradually returning servers to service; limited recovery has been observed in some regions, but restoration is not yet universal.^1^

Check the status affecting your tenant

Sign in to the Microsoft 365 admin center with an administrator account.
Open Health → Service health.
Under Active issues Microsoft is working on, select the relevant incident.
Review User impact, Affected services, Status, and All updates.

Service health is tenant-aware and therefore provides more precise information than the public status page. Service Support admins and Helpdesk admins can also view it.^2^

If the admin center is unavailable, use Microsoft’s public service status page. That page is intended as the fallback when an incident prevents access to the admin center or its Service health functionality.^3^

What to do now

Avoid making broad tenant, identity, DNS, or client configuration changes while the incident remains active.
Record the incident ID and timestamps for internal tracking.
If your symptoms are not listed in Service health, select Report an issue there.
If the incident is already listed, Microsoft advises following its Service health updates rather than opening a duplicate support request.^3^
After restoration, check Health → Service health → Issue history for the final update or any published post-incident report.^2^

References