I'm assuming this is related: I can't do any development using Visual Studio 2019 at the moment because it calls home to verify the license and it is currently unable to log me in to to verify my license. So VS is basically bricked for me until this gets fixed :-(<p>Screenshot: <a href="https://rog.gy/ss/3b14f7a2ac.png" rel="nofollow">https://rog.gy/ss/3b14f7a2ac.png</a>
Is this /really/ the status page? It looks like it was pasted straight out of an email to Jason Zander from whoever is trying to fix the problem.<p><a href="https://status.office365.com/" rel="nofollow">https://status.office365.com/</a><p>Title: Can't access Microsoft 365 services<p>User Impact: Users may be unable to access multiple Microsoft 365 services.<p>More info: Any Microsoft 365 service that leverages Azure Active Directory (AAD) authentication may be impacted by this issue.<p>Current status: We've identified and are reverting a recent change to the service which may be causing or contributing to impact.<p>Scope of impact: Any user may experience access problems for Microsoft 365 services.
"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable."<p>Ironically found on <a href="https://www.microsoft.com/en-us/research/publication/distribution/" rel="nofollow">https://www.microsoft.com/en-us/research/publication/distrib...</a><p>The cloud is the ultimate rent-seeker's dream. The world's computing power in the hands of a few enormous companies... who then sell it to you in tiny pieces and charge for every little thing you use on their services. And when something goes wrong, you are powerless to do anything about it.
I just finished convincing old-school management to move to Office365/Azure/Teams after we've been doing everything on-premise, saying we can reduce our maintenance and increase in reliability since we're a small operation. Needless to say this isn't a good look for me.
At least the guy with the change request was vindicated for now. That must have felt good - about to be crucified for putting in a change that brought down AAD globally, they roll it back and shit's still broken. :D hahaha wudn't me mofos!
You could play status page roulette...<p><a href="https://status.azure.com/en-us/status" rel="nofollow">https://status.azure.com/en-us/status</a><p><a href="https://status.office365.com" rel="nofollow">https://status.office365.com</a><p><a href="https://portal.office.com/servicestatus" rel="nofollow">https://portal.office.com/servicestatus</a>
I've gone all in on Microsoft for my company (high Office usage) with O365, Azure and friends and I'm regretting this decision.<p>OneDrive for Business is almost unusable on Windows 10. The web apps are incredibly slow. Teams is very inconsistent for users between desktop and mobile usage. It's a mess.<p>I'm planning on switching to Amazon next year. I hope I can find an alternative to the Office situation (maybe offline licenses).
There's an <i>unconfirmed rumor</i> that this outage has taken out 911 services in multiple parts of the US.<p><a href="https://www.nbcnewyork.com/news/local/nationwide-reports-of-911-system-outages-cause-not-immediately-clear/2640684" rel="nofollow">https://www.nbcnewyork.com/news/local/nationwide-reports-of-...</a>
O365 (aka Microsoft 365 now) has easily been the most unreliable SaaS product I've been forced to use over the past 8 1/2 years, it's been a real disaster story for several of the clients I used to have and for several of them has resulted in loss of profits and general distrust in Cloud/SaaS software.<p>A few times during outages I managed to get hold of someone that worked at Microsoft who stated something along the lines that they only state that a service is degraded or has an outage if enough customers complain - or if the websites they have to sell / demonstrate products to potential customers are unavailable.
The best part: "Add this page to your favorites"<p>The link is <i>javascript:window.external.AddFavorite(location.href,%20document.title);</i>
I know many posts in this thread have been jokes, but I do hope this outage helps MS reconsider their offline iterations of Office. I use Office on a near constant basis (writing and building lecture PowerPoints). The subscription model isn't feasible and would ultimately be more expensive in the long term. When Office 2019 was released I quickly picked it up out of worry that MS would shift their academic licensing programs to 365, which they ultimately did.
I wish this were only limited to Office 365. It's most services that use authentication backed by Azure Active Directory.<p><a href="https://status.azure.com/en-us/status" rel="nofollow">https://status.azure.com/en-us/status</a><p>A few days ago a similar outage occurred with Google Accounts.
It's called Office 365 for a reason. 2020 is a leap year, but there is no reason for the outage to occur exactly on February 29 or December 31.<p>Wasn't there also a widely-publicized outage in 2016?
Azure DevOps' Git is also down (a git pull hangs forever) which is a bit surprising. I wouldn't have expected SSH key authentication to depend on Azure Active Directory.<p>Microsoft Teams also appears to be down so it's not just authentication that's affected as I was already logged in and it still doesn't work, just hangs trying to load forever.<p>Edit: appears to be resolved at 1:07 am London time.
Ahh, this explains why I was unable to log into my personal email account on my work laptop.<p>I thought it was just the network here being overly keen to block requests since I'm relatively new and am still finding out all the quirks<p>This also explains why clicking "Sign in" would randomly download an HTML page (ie logout.html) instead of redirecting to the proper auth endpoint!
I noticed some strange behavior around 3-4PM central. I was searching my inbox and saw an error in Outlook "we're unable to search the server" or something like that. I have never seen a message like that from Outlook before.
I'm reminded of what Leslie Lamport (who ironically went on to work for Microsoft) once observed:<p>"You know you have a distributed system when the crash of a computer you’ve never heard of stops you from getting any work done."
My kids' school district is doing all online over MS Teams; things started crashing and burning around 3PM PST (no "Dad Support" can fix MS's servers though).
is this a national risk? - think other countries taking out these massive, saas offerings. must be easier than simultaneously targeting thousands of disparately configured, onprem implementations