Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Azure Outage

twitter.com

Post reply on HN
Print view View original

181–190 of 247 posts

Re: Microsoft Azure Outage

#181

Post by [deleted] »

polack wrote: post #140
wrldos wrote: post #137

Earlier quoted context omitted.

They never attach it to the monitoring because monitoring systems usually generate a lot of false positives which affect their published SLA.

Then they should have a "?" status that can be triggered by automated systems that acknowledge that it looks to be an issue but that they are manually investigating. If it's a false positive they just resolve it without it affecting SLA and if it's a real problem then us customers wouldn't have to debug our own stack for 2 hours before Microsoft informs us that they are the problem. EDIT: Wonder how many man-years of…

[deleted]

Re: Microsoft Azure Outage

#182

Post by latchkey »

saikatsg wrote: post #14

> We've identified a potential networking issue and are reviewing telemetry to determine the next troubleshooting steps. You can find additional information on our status page at https://msft.it/6011eAYPc or on SHD under MO502273.

It is often very difficult to test networking changes in production. For example, firewall rules. What sort of tools do people use for this?

Re: Microsoft Azure Outage

#183

Post by smileybarry »

tialaramex wrote: post #108
madduci wrote: post #98

Earlier quoted context omitted.

Many companies use Active Directory. The new kid in the block is Azure Active Directory (AAD), which is the evolution of the self-hosted Windows Servers. Since many companies rely on it, especially for role base access to internal resources, you can't avoid it as a developer/employee.

Azure Active Directory is not Active Directory but on Azure.

You're right, but that's not what they meant (and it's not AAD's trajectory). Microsoft's been adding more and more device management, policies, software rollout, etc. to AAD to bring it up into equal standing with AD and then, eventually, allow most deployments to use just AAD, instead of holding some bulky AD setup of on-prem & cloud.

Re: Microsoft Azure Outage

#184

Post by llama052 »

dustedcodes wrote: post #18

Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.

This place I work at has actively fought against using Azure, but we use them because it's advantageous to the business. (or it's perceived to be).

We have actively pushed for AWS or even GCP but it's futile when it doesn't align with business. I'd imagine a lot of developers are facing the same company issues.

Azure is a chore compared to AWS.

Re: Microsoft Azure Outage

#185

Post by zerohp »

jiggawatts wrote: post #127
tenplusfive wrote: post #23

Earlier quoted context omitted.

Luckily Microsoft also provides a service for that: Safelinks https://learn.microsoft.com/en-us/microsoft-365/security/off... Also a personal favorite of mine: http://microsft.com (not entirely sure if its just to prevent typosquatting or if this is actually used in some products)

microsft.com was used specifically for telemetry to bypass web proxy blocks for *.microsoft.com put in by administrators of secure networks. I know this because I was one of those admins trying to plug the leaks. Windows 10 + Office uses 200+ domains just for Microsoft stuff, of which something like 120 are for telemetry.

Yet people continue to defend Microsoft's telemetry practices. The OS won't let you opt out without it fighting you and they'll even fight you for blocking it on the network.

Windows is spyware.

Re: Microsoft Azure Outage

#186

Post by wereallterrrist »

dustedcodes wrote: post #18

Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.

The irony is the amount of money they have thrown at "Dev Advocates" who don't do a god damn thing to advocate for how developers use their platform. Frankly that's because folks that care burn out. I still remember the time a high-up rail-roaded me and lied repeatedly to a VP about the design of a product as I desperately tried to save them from the 5+ years of having to educate users on two different ways to do [basic ops]. Those basic cloud objects of course have major differences in functionality and ecosystem viability depending on what you choose, but this isn't really explained up front either, you find out by building a solution for months and then finding out you have to backtrack and start over the Azure integration. Maybe again.

All to say, I agree wholeheartedly with every word.

Re: Microsoft Azure Outage

#187

Post by Alupis »

zufallsheld wrote: post #39
dustedcodes wrote: post #18

Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.

> I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve I guess many developers do not use Azure voluntarily but are forced to by their companies (or customers).

Governments - local, state and federal, pretty much are captive Microsoft customers, and are eye-balls deep in Microsoft 365 + Azure services.

Re: Microsoft Azure Outage

#188

Post by Enginerrrd »

ctvo wrote: post #174
VyseofArcadia wrote: post #163

Earlier quoted context omitted.

When anything on that page turns not-green, there are news stories about it. Not positive ones. So exec approval is needed, because the decision to flip something on that page is ultimately the decision to cause stories negative to MS to be published. The exec has to weigh whether pissing off the customers (by failing to acknowledge reality) is worth the bad press and SLA fallout.

It has nothing to do with press. This is negative press already, and journalist can use this to write their stories without waiting for the official light to go from green to yellow. It's about contractual obligations and SLAs. Things are not officially down in most agreements until MSFT acknowledges they're down. Refunds issued because your blob storage failed to meet 99.9999 uptime to your largest customers are dir…

I'm not going out of my way to be hyperbolic or anything here, but that sounds suspiciously like "fraud" to me.

Re: Microsoft Azure Outage

#189

Post by wereallterrrist »

sofixa wrote: post #97
dx034 wrote: post #84

Shows that all these availability zones and regions don't really help if an outage can knock out a whole cloud provider. And that's not specific to Microsoft. The only way to really ensure uptime is to use two providers. Sadly, that's basically only possible with on-prem/colocation where traffic is cheap.

It's mostly Azure though that is badly designed to such an extent that multiple times there have been global outages. In general Azure availability, security (the only major cloud provider with not one but multiple cross-tenant security exploits) and usability are pretty terrible so it shouldn't be used for anything but saying "this is how it should not be done". GCP had a similar thing once, where a BGP update knock…

Someday someone will write a book about how AD, AAD, etc, exert the control they do at MS and go as unchecked (or at the time) as they do. AD's inability to execute made Azure a significantly less pleasant platform until they finally fixed accounts a couple of years back to properly do OAuth 2.0 with ARM.

Maybe the book is just "AD brings in the money" but wow, they sure bring it down as well. Global outages like that always stink of AD.

Re: Microsoft Azure Outage

#190

Post by jakewins »

cryptonym wrote: post #128
spoils19 wrote: post #67

It's good that Microsoft saved money via layoffs so that it balances out when customers leave Azure. Very forward thinking company.

Leave to go where? On-premise and being miserable having to wait months to get a new server with poor automation, observability and worse outages? To another major cloud provider with similar pricing and outages? Cloud helped mostly with automation and scaling but if your system is that critical, you should consider a good CDN as load balancer and multi-cloud (or at least multi-region) for actual robustness.

AWS and GCP both have ~100% uptime in every region for VMs this month. Meanwhile the majority of Azure regions have had various outages in the same period: https://cloudharmony.com/status-of-compute
Post reply on HN