Microsoft's Azure networking takes a worldwide tumble Microsoft's cloud services are having a bad day with users worldwide reporting difficulty connecting to Azure. According to the Windows giant's social media orifice for all things Microsoft 365-related, "We're currently investigating access issues and degraded performance with multiple Microsoft 365 services and features." …
If Microsoft operated an airline you'd have pay £6.99 for the journey, £150 for "upgrades" (like a seat, seat-belt). £49 for "optional security extras" (shared use of wings and a landing gear), £199 for the pilot, a further £599 for a security product to ensure the pilot isn't pissed, and you'd have to book it by calling a number in India, answered by someone who only understands you if you talk like Hugh Grant. If your flight leaves on Monday, they'll arrange to call you back, on Wednesday.
Nope this is a MS problem, 100%.
Seemed to be more of a internal routing problem.. Or someone forgot to pointed the Azure ( sorry Entra) servers to the wrong IP or one of a million other possible errors that a company that size will undoubtedly make.
This might sound stupid but "We pay for shit to happen and it does". MS will always guarantee that side of things for us.
Please can Microsoft et all either fix their status pages (I know, I'm being ridiculously unrealistic here) or just get rid of them as they always claim that everything's rosy in the Seattle garden.
It appears to be that as long as a single horse trader in Ulaanbaatar can access the system that counts as 100% uptime globally and so the status pages are worse than useless. No doubt because stating otherwise would mean that Big Tech would have to admit it isn't perfect in every possible way (and presumably SLA $$$ would be due to some organisations).
Just a thought. As AI is so wonderful and can solve all of the world's problems, could they not just point Copilot at it /s?
The Microsoft 365 status pages (and the admin alerts they push out to Outlook) seem to always line up with actual issues, in fact if I was going to credit Microsoft with doing one thing well, it might even be that. Compared with, for example, pretty much every ISP I've ever had dealings with, whose status pages almost always deny there's anything wrong, even when you're dealing with a multi-day outage.
Compared with, for example, pretty much every ISP I've ever had dealings with, whose status pages almost always deny there's anything wrong, even when you're dealing with a multi-day outage.
Spectrum Internet: have you rebooted all your equipment, turned off all of your security, and connected your PC directly to our modem? Do that first. Even though the blinking lights on the cable modem clearly state it's having trouble communicating with their network.
Outage map, well that is only accessible by going through our chat bot. Make sure you have our useless app installed on your phone so that we can tell you that there are no outages reported in your area. Finally you'll get a text telling you of an outage with an ETA in 6 hours. (plus or minus 6 hours) Odd how all these regular outages happen at the same time of the day. Almost like scheduled maintenance.
This post has been deleted by its author
Azure has what Microsoft describe as a "backbone network".
Effectively an internal network that operates within Azure's infrastructure and doesn't expose any traffic to the wider internet. Supposedly excellent for connecting all your Azure thingy things.
It's redundant in the sense of the same thing has been repeated a lot of times.
Given everything is fucked I'd suspect it's got something to do with that.
We have an Azure Exchange instance hosted in the US. Users are in California and, in the office, are behind a firewall that geofilters. Last week we started noticing that Outlook was trying to access Exchange using IP addresses, apparently belonging to Microsoft, that geolocated to Chile, Brazil and India. Eventually Outlook would find an IP address that wasn't blocked. Microsoft support told us on Saturday that there was an outage but didn't give me any more information.
You've whitelisted the recommended Microsoft IP ranges corresponding to your services right?
Or at least fixed it after the "Microsoft outage" that affected the pool of customers that hadn't set up their firewall rules correctly?
I.e.
https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide
Filter for appropriate services and regions...
Surely Microsoft need to use their own Azure Chaos Studio on their network. Once they have it all working and nothing ever fails, then and only then can they preach to everyone else.
Currently this just looks like a story of "we have a tool, but don't use it, but you should use it" implying that in some way, it would solve THEIR problem.. Muppets.
As of last week I am 'at leisure' since I supported a non-MS product which was considered not sexy enough for a 'forward thinking progressive finance company'. Their solution was to throw out bath water and baby and go fully MS to have a tightly integrated global 'one size fits none' solution albeit at orders higher cost than the previous smorgasbord of products which each did their specific function perfectly and could talk to each other quite happily.
I hear there may have been a few issues which may have impacted every element of the day to day business and my heart goes out to all those poor buggers left scrambling to explain why they are not able to fix anything as the problems are 'in the cloud'...you know, that totally resilient, can never be broken, reach it from anywhere solution which the CxO people all believe is for 'the Greater Good'
Once it stops being so pleasantly sunny here I may drop the guys an email to see how it's going although that does require them to be able to get into O365 (insert alternative names here) to read it
Condolences on the change in work level if it wasn't desired.
'Forward thinking progressive finance company'" sounds like a few antithetical juxtapositions back to back. And if going all in with one vendor is "Forward Thinking" I am a dancer with the Paris Opera Ballet.
My employer wasn't able to resist the lure of the cloud, but a compromise was reached where we don't use any proprietary crap such as AWS Lambda and have disaster recovery on dedicated servers at a nearby data centre. On AWS we use EC2 for the "servers", RDS for managed databases and S3 with a little Cloudfront. That's easy to replicate with similar functionality on real machines, and hopefully we'll survive the inevitable mega outage when Amazon have their own CloudStrike or Azure fuckwittery.
I've found that tallikg quickly works better than the English habit of talking loudly and slowly
I am assuming your technique produces no response at all while the old imperial standard one produces complete nonsense or at best misleading responses.
All in all I suspect you might have the better techinque if a little pointless. Could try speaking Klingon or old Elvish (Quenya)* for the same result. :)
In all honesty I am sure it really would not matter what language was used as you would still get the same codswallop.
* it appears there are quite a number of unusual people that have collected, compiled and augmented these "languages."
"Someone else's computer that you are paying too much for"
And, don't forget that those uptime numbers that are touted are diluted to the point of irrelevancy because of the vast scale of the systems being reported against.
99.99999% availability doesn't mean sh!t if 100% of the stuff that impacts YOUR shop are down, and likely no one gives a crap about any one particular customer outage until it is large enough to make it into the news (or El Reg, anyway)
I wonder if AT&T is down again? They made this big deal about how they were moving basically everything but the physical radios for their cell phone network into Azure. They've already had grilling for a few outages this year (since it also blocked 911 -- that's 999 over there -- calls.)
Once again "Dur Cloud" is an excuse for no resilience, and no service:
"HM Courts and Tribunals Service took to Xitter to say: "We are aware of users experiencing issues accessing multiple online services. This appears to relate to a global Microsoft Azure outage.""
If this was on-prem, there would be redundancy, as quaintly, we used to think this was important. Now nobody needs to bother as a cloud outage is treated as some kind of natural disaster, instead of a system design failure on the part of the service provider.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
