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

81–90 of 247 posts

Re: Microsoft Azure Outage

#81

Post by 8fingerlouie »

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.

It doesn't really matter, at least if you're in the EU.

While Google, Amazon and others were busy complaining about GDPR, Microsoft was busy working on being compliant, with the result that today they're pretty much the only legal/compliant solution in most of the EU.

The more regulated the industry (health, finance, etc), the more you can be certain that it's running on Azure if it's EU based and running in the cloud.

Re: Microsoft Azure Outage

#82

Post by adql »

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).

We're migrating on Teams because of that kind of reasoning.

It's utter shit of a service. Even worse if you need to write integrations for it

Re: Microsoft Azure Outage

#84

Post by dx034 »

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.

Re: Microsoft Azure Outage

#85

Post by adql »

ricardobayes wrote: post #54
noinsight wrote: post #32

Earlier quoted context omitted.

If you implement an allowlisting proxy, the number of required domains for M365 / Azure is something like 120 [1]. Google basically requires three, tunnel.cloudproxy.app, *.google.com and *.googleapis.com. Amazon requires *.aws.amazon.com, *.amazonaws.com, *.awsstatic.com, *.api.aws and *.aws.dev. Microsoft has some great domain planning. [1] https://learn.microsoft.com/en-us/microsoft-365/enterprise/u...

My point is MS uses a lot of unrelated domains that are very different from the main brand, even the one above looks dodgy (msft[.]it) From your list, microsoftonline-p[.]com is an official domain, but it looks like a typosquat. I think it's quite far from "great domain planning".

> I think it's quite far from "great domain planning".

The poster saying they have 120 of them would imply that being sarcasm

Re: Microsoft Azure Outage

#87

Post by joecool1029 »

ricardobayes wrote: post #17
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.

I'm so surprised by MS's strategy for using random domains and TLD's, this certainly don't make it easy for phishing avoidance.

.it ccTLD is especially bad. Almost all of the generated SEO spam links to malicious ad networks I get on search pages are usually .it domains, all written in machine english, not italian. Thanks for reminding me and discovering -site:.it works in search queries to filter it out.

Re: Microsoft Azure Outage

#88

Post by luckylion »

tenplusfive wrote: post #23
ricardobayes wrote: post #17

Earlier quoted context omitted.

I'm so surprised by MS's strategy for using random domains and TLD's, this certainly don't make it easy for phishing avoidance.

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)

I don't know whether it's a typo but https://support.microsoft.com/en-us/topic/contact-us-91f63b4... lists "EOC: criskgro@microsft.com (For CEE and MEA)" under the Microsoft Credit Services. It feels like a typo, but who knows. If they don't have anything in place to catch this type of error, it's probably a good idea to register every domain someone could accidentally type.

Re: Microsoft Azure Outage

#89

Post by robertlagrant »

ricardobayes wrote: post #54
noinsight wrote: post #32

Earlier quoted context omitted.

If you implement an allowlisting proxy, the number of required domains for M365 / Azure is something like 120 [1]. Google basically requires three, tunnel.cloudproxy.app, *.google.com and *.googleapis.com. Amazon requires *.aws.amazon.com, *.amazonaws.com, *.awsstatic.com, *.api.aws and *.aws.dev. Microsoft has some great domain planning. [1] https://learn.microsoft.com/en-us/microsoft-365/enterprise/u...

My point is MS uses a lot of unrelated domains that are very different from the main brand, even the one above looks dodgy (msft[.]it) From your list, microsoftonline-p[.]com is an official domain, but it looks like a typosquat. I think it's quite far from "great domain planning".

They appear to be being sarcastic. I don't think anyone would be seriously saying 120 is better than 3 or 6 domains.

Re: Microsoft Azure Outage

#90

Post by ibejoeb »

dsign wrote: post #34

This makes you wonder if some centralization patterns, i.e. Azure AD, are not a national security problem?

Azure AD is a nightmare. I don't know how many of you sign in to multiple tenants in the console, but it generally involves buying a new computer.
Post reply on HN