Microsoft blames Outlook's wobbly weekend on 'problematic code change'

And Monday's not looking that steady, either

This weekend's Microsoft 365 outage, which left unlucky subscribers unable to login and use its Outlook email service as expected, has been blamed on a "problematic code change" by the Windows giant.

The problems for Redmond, and its paying customers, started at around 2100 UTC on Saturday. At least 30,000 Outlook users reported problems via DownDetector alone, and there are still intermittent issues for some users as the new week swung around. Now, according to Microsoft's status page, everything's fine and should be working again.

"We've identified a potential cause of impact and have reverted the suspected code to alleviate impact. We’re monitoring telemetry to confirm recovery," the cloud titan added in an alert on US state media.

"Following our reversion of the problematic code change, we’ve monitored service telemetry and worked with previously impacted users to confirm that service is restored."

There were some hiccups along the way, however. iOS users reported still being unable to login even after the promised fix was rolled out. In some cases they report having to delete the app from their handsets and reinstall it to get successful connectivity.

Then to add insult to injury on Monday, Redmond was again warning of some downtime affecting Microsoft 365 services. For instance, some of those looking to enjoy start-of-the-week Teams meeting to catch up with coworkers were stymied and unable to use the system as hoped. Your mileage may vary: Some people have working access to M365, some don't.

We've asked Microsoft for clarification about the issues that have caused the bumpy service and will update as more information comes in.

That said it hasn't been the greatest of starts to the year for Microsoft on the outages front. Last month Azure took a dive for Nordic customers, and in January 365 login problems led to a lot of customers having a bad case of the Mondays - made worse coming after another Azure outage a few days beforehand. ®