←back to thread

285 points alephnerd | 1 comments | | HN request time: 0.209s | source
Show context
neya ◴[] No.41901576[source]
If you use Azure in any realistic production environments, then it's on you. Even with $100k in free credits, they couldn't convince me to use it for more than a month. It is expensive, the interface is highly user unfriendly and most important of all, their products don't at all seem reliable for production workloads because of stuff like this. Sorry Microsoft, I think you can do much better.
replies(15): >>41901755 #>>41902286 #>>41902571 #>>41902679 #>>41902715 #>>41903167 #>>41903320 #>>41903580 #>>41903869 #>>41904371 #>>41904976 #>>41905535 #>>41905826 #>>41905858 #>>41907485 #
prennert ◴[] No.41902715[source]
When you come from other cloud providers, working with Azure has so many dark-orange flags. It feels totally inconsistent and patched together. This makes it hard for me to believe that anybody can properly audit it for security.

The most uncomfortable part is their log in. The amount of re-directs and glitches there are insane. Its hard to believe that it works as intended.

As an example, for some reason I could not download the BAA because trying to download it lead to a login loop on their trust website, while I was still able to see the Azure console ok in the same browser.

When I signed out of my Azure account to try if a fresh login helped, it did not trigger my 2FA at the next login. In my mind, if I actively logged out from a browser window, I withdraw my trust in that device. So not being triggered for 2FA is a massive red flag.

(no I still could not download the BAA, nor file a ticket for it, but somehow a colleague could download it ok.)

replies(7): >>41902823 #>>41903429 #>>41904108 #>>41904633 #>>41904940 #>>41905080 #>>41909148 #
1. 7bit ◴[] No.41909148[source]
When you promote a Windows server 2016 or higher) to a domain controller, you suddenly get error message when trying to open the network adapter through the "new" settings app. You must open through control.exe, everything else just throws an error.

I opened bug with the Microsoft Premier support and they told me that this works as intended.

So when Microsoft says, it works as intended, it can still be bugged to hell and back. They just don't care.