The M365 status page not loading reminds me of one of my favourite Simpsons jokes: https://www.youtube.com/watch?v=3Hz2uOSdV24

Yep my org as well.

It's funny how text-only niche forum that looks like it's running on RPi stuffed in someone's closet is routinely used to discuss active outages in multimillion/billion corps.

It took 30 seconds to open a "local" file in Word, and my Outlook email wasn't updating.

In other words, a day that ends in "y".

My company was recently acquired by a company that uses Office, so I'm using Microsoft products for the first time in 15 years. It's absolutely APPALLING how bad they are. I assumed they got fairly usable in the last 15 years, but it seems they've gone backwards.

For all my gripes about GSuite, ... I don't know how businesses can justify using software this bad.

Azure communication services (ACS - transactional emails) also appears to be down. Quite amazing one thing can roll out and break so many Microsoft services at once.

> Current status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

I think it's safe to say, if the server is unresponsive, the change is not effective.

In the words of an ancient ...I think newgrounds(?) video embedded in a SWF, "I can't get to my email" Edit: here it is: https://www.youtube.com/watch?v=uRGljemfwUE

Hope this entertains you while we can't get to our emails.

Not sure they got the memo to host the status page in separate infrastructure...

Ironically, this article is down as well.

No worries, the AI was installing an update...now it's looking for the issue, found Exchange and deleted it...

For whatever reason 6.1 Sol is completely lobotomized for me this morning, so it wasn't helping much with the investigation, but it was pretty clear that MSFT was having issues.

I have a teams app with Outlook integration and received a bunch of 502s to smba.trafficmanager.net and a my logs are riddled with "RestError Temporary connection issue when contacting service. Please wait before retrying request"

I will say this, having apps deployed on Slack and Teams, Slack rarely has issues (an exponential backoff is enough to simply never worry about my Slack integration). With Teams I have mysterious failures to debug at least 2x a year - and they're often not very transparent about them (often my first instinct is to search Twitter and find people complaining about the same thing).