What you need to know
- Microsoft 365 experienced an outage of sorts that prevented people from signing in.
- Though most of the services appear to be up and running again, Outlook.com remains affected.
- Microsoft is actively working on remedying the issue.
Microsoft 365 services experienced an outage this evening, preventing people from signing into their accounts. While those who were signed in could continue to access their various Office and Microsoft services, anyone who signed out was unable to log in. While most of the services appear to be back up and running, Outlook.com is still affected, according to Microsoft's Office service status (opens in new tab) page.
The original issue was down to Microsoft's infrastructure failing to [process] authentication requests in a timely manner," according to an earlier update on the Office service status page. Microsoft says it rerouted traffic to alternate systems in response.
"Our mitigation strategy was successful in allowing users to sign into the previously impacted services," Microsoft said in an update to the page. "Our internal monitoring has validated this recovery and we have received positive confirmation from customer reports. We'll continue to monitor the service and provide updates on full recovery to remaining impacted users."
It's unclear when Outlook.com will be fully up and running again, but we'll update this post with more details as they become available.
Ha ha ha. All of your eggs in one basket. Why I will always stay 100% offline with all my programs.
Still having all your eggs in one basket. What happens when your computer dies or you need to access something when you're miles away? Both have their positives and negatives but the cloud is the future.
I have a offline backup of everything. Plus if I need to access something miles away, I have a flash drive. I know cloud never reliable anytime I want to use it.
Nah. Outlook.com has been just fine.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.