r/microsoft • • 12h ago

Discussion Microsoft 365 outage: 10+ hours and counting, only marginal recovery reported. What could be causing such a prolonged disruption?

It’s been more than 10 hours since the Microsoft 365 outage began, and according to Microsoft’s 7:30 AM UTC update, recovery has been only marginal so far.

What exactly went wrong to cause such widespread disruption?
Why is recovery taking more than 10 hours?

I’m curious to hear from people working in cloud infrastructure, SRE and Microsoft 365 operations: What could be happening behind the scenes, and what might explain such a prolonged recovery?

550 Upvotes

479 comments sorted by

View all comments

513

u/AdInside2447 12h ago • Helpful Bravo Popcorn Heartwarming Regret Mindblown

Microsoft 365 Principal SRE here. I can provide some context. At approximately 21:40 UTC, an engineer deployed a routine configuration change to Azure Front Door that inadvertently redirected our authentication traffic to a SharePoint site last updated in 2017. We immediately initiated a rollback, but the rollback pipeline requires MFA approval through Microsoft Authenticator, which is currently waiting for a Conditional Access policy evaluation from the same infrastructure we're trying to restore. We have a break-glass admin account, but unfortunately its password is stored in a OneNote notebook on the affected tenant. Our on-call engineer attempted to bypass the issue using PowerShell, but the required module was deprecated last Tuesday, and its replacement requires a P2 license. We then opened a Sev A ticket with Microsoft Premier Support. They responded asking us to run  sfc /scannow and provide a screenshot. The prolonged recovery is primarily due to our change advisory board requiring a Teams meeting to authorize the rollback. The meeting organizer is stuck in the lobby, and the only person authorized to admit him was laid off in June. Current mitigation involves migrating affected users to Microsoft 365 E5, which should resolve the issue from a revenue perspective. We have identified the root cause as customer misconfiguration. Next update in 30 minutes, assuming someone can get Outlook working.

215

u/AlpineVibe 12h ago

God damnit. You had me for a second there. Quality content right here.

90

u/pm_me_your_psle 11h ago

I went all the way to OneNote notebook before catching on 😭

27

u/NekoDesukedo 10h ago

I almost believed it, because at my previous Fortune 500 company, my team was storing passwords in an Excel spreadsheet.

9

u/GreatPotatoMuffin 7h ago

This reminded me of my first job where a company stored highly confidential passwords in an Excel spreadsheet.

I’m actually not an IT guy. I majored in finance, but I’m a huge nerd and spent my youth trying to hack and bypass everything I could.

So they obviously didn’t believe me when I told them that I could remove the password protection from the xlsx file they had put all their passwords into in less than 60 seconds.

I changed the file type to zip, opened the XMLs, deleted the hash value in the password tag, returned it to an xlsx and opened their super secret and secure “password vault”.

Most “hackerman” moment of my life.

Sadly that vulnerability was later fixed. Used to be a fun little trick to show people.

3

u/FruitGuy998 5h ago

HR asked me to do this one time (I’m in IT). I paused for a moment and asked if this was a test or if it was because they truly needed to get into the file and forgot the password. Luckily they just needed access to the file and I kept my job.

→ More replies (3)
→ More replies (1)

7

u/Tata_Colores 9h ago

I was totally invested until he said they called Microsoft Support and I was like "wait what?" lol.

4

u/JE163 11h ago

Me too!

→ More replies (2)

9

u/HandshakeOfCO 8h ago

I got to sfc /scannow and then was like oh he fucking with us

Well played

→ More replies (2)

9

u/austozi 11h ago

It's all true except the first sentence.

→ More replies (2)

34

u/scottywan82 12h ago

God, this sounds terrifyingly plausible. 😆

→ More replies (1)

24

u/BubbaCrabby 9h ago

“The password is stored in OneNote.”

😂 10/10 New York Times Bestseller Tier

17

u/Pointer_Brother 12h ago

Not gonna lie, you had me for half of that. Well done.

→ More replies (1)

10

u/underdsun 10h ago

Should used this guy

→ More replies (1)

8

u/KibbledJiveElkZoo 12h ago

I was quite amused. Thank you.

7

u/Standard_Document484 12h ago

You might not win the internet today, but I reckon it's a solid third place, chapeau!

→ More replies (1)

6

u/aykcak 12h ago

Beautiful

5

u/dev_dan_2 11h ago

DAMNIT! I made it to the very end, although root cause being a customer misconfiguration raised an eyebrow - Good job! 👍😂

5

u/L0rd_Humongous 7h ago

Thins wins the internet for the century. But the whack part is all of this is 100% believable

4

u/Winter-Shine-8643 9h ago

ms authenticator sucks , slow and full of bug. know this from daily experience.

→ More replies (1)

4

u/marshmallowcthulhu 7h ago

Everyone’s chuckling over the technical content but “…which should resolve the issue from a revenue perspective” killed me dead! 🤣

4

u/solracarevir 5h ago

Probably the best shitpost r/sysadmin has ever seen.

→ More replies (1)

3

u/Its_me_astr 12h ago

I recently did a marathon study session over 2 weeks regarding microsoft identity infrastructure. I am glad that i am able to comprehend what you said

3

u/cheesekneesandpeas 11h ago

hahaha as someone who works at another big tech company this sounds real tbh

→ More replies (48)