Microsoft 364 trips over its own network settings in North America Microsoft 365 services toppled over in North America last night due to an infrastructure misconfiguration. According to affected users, the outage started at 1810 UTC on October 9 and affected all Microsoft 365 services including Teams. The outage was brief, and just over an hour later, Microsoft confirmed that everything was …
The servers were up. We have had at least 1 server turned on at all times since whatever date we launched whatever you categorise as the current platform. Your inability to access the backend services is irrelevant to the truthfulness of the 365 branding.
Stop complaining and get to work figuring out which combination of additional licenses you need to purchase for each user to get the "ability to access services" feature.
- Microsoft Legal Team
"The company's Admin Center said: "We're analyzing configuration policies and traffic management processes on the affected network infrastructure to identify necessary refinements and increase resilience in the event of future incidents."
In other words, "We will be using this incident to train our AI systems to ensure it doesn't happen again".
A high-wire act balanced on a wobbly infrastructure. Consolidating all critical computing workloads within a singular cloud control plane. A virtual machine running on a cluster on virtual containers over a software-defined network. What could possible go wrong :o
" The outage was brief, and just over an hour later ..."
It would have been sooner but the option to change the setting had been moved 5 times in the last month, this time to:
Settings -> Special -> Dynamic -> Network -> Offsite -> Nebulous -> Containers -> Automatic -> AI -> Microsoft -> All Settings -> General -> Advanced -> Overrides -> Cloud -> Virtual
/s
If I were running Exchange on-premises, at least I'd have access to log files. Well, assuming Microsoft's programmers are smart enough to write to log files. I don't know; I was forced away from my legacy system because my management wanted to go all Microsoft and move as much as we can to the cloud. In somewhat related news, I'll be retiring in 280 days if all goes to plan.
But yeah, the cloud has weird shit happening and no ability for me to see the log files, so that was a downgrade.
You and your skills will be missed. I am a few years behind you, unfortunately. It amazes me how compartmentalized IT is these days and it's like network people don't even remember that their equipment has logging capabilities, never mind the ability to log to servers where even the most rudimentary tools are useful. Grep goes a long way.
it's expensive, doesn't work, you end up hiring entire teams of accountants in "finops", you have zero idea what you ACTUALLY need to buy to do what you want and that's BEFORE ingress and egress costs come along.
Then someone bean counter decides that a feature your company is desperately dependent on isn't making enough money so they'll turn it off, or they'll suddenly redesign the front end so your support staff can't find anything.
As ever.... only the idiots put stuff in the cloud
From an across the pond perspective....
Need to get away from it.... It's just toxic
The only thing stopping homegrown alternatives is laziness and easy monies
We speak the samish language but the cultures have always been distinctly different
When government bodies start leveraging away from companies like oracle/ms/salesforce/meta etc... and above all the emotionally immature rich saddo's running them..... That is when the tide will turn
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
