> We have confirmed that an inadvertent configuration change was the trigger event for this issue.
Folks, it's all okay! It was just an inadvertent configuration change [that happened to bring loads of services for millions of users down]. No biggie.
Look, this is the level of professionalism we should expect of Microsoft at this point.
They had a separate global outage of Office 365 (or whatever it's called this week) *this month* already:
https://www.bleepingcomputer.com/news/microsoft/microsoft-365-outage-blocks-access-to-teams-exchange-online/
And then there was the one from February this year:
https://www.upi.com/Top_News/US/2025/03/01/microsoft-outages/3061740867107/
Not to mention smaller ones, like the one in US-East that prevented admins from accessing the admin center:
https://www.bleepingcomputer.com/news/microsoft/microsoft-investigates-outage-affecting-microsoft-365-admin-center/
Microsoft 365 outage blocks access to Teams, Exchange Online
Microsoft is working to resolve an ongoing outage preventing users from accessing Microsoft 365 services, including Microsoft Teams, Exchange Online, and the admin center.
www.bleepingcomputer.com · BleepingComputer
Link author: 
Sergiu Gatlan@serghei@mastodon.social
If you have a fediverse account, you can quote this note from your own instance. Search https://mstdn.social/users/rysiek/statuses/115459980415813121 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
