6 ms·

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 ha

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

mrweasel 2y ago
> It feels totally inconsistent and patched together. I believe that multiple article, e.g. on The Register, has mentioned that people who have left the Azure team has routinely complained that the pace was to high, and that everything is pretty much duct taped together. This was years ago, so it may have changed.
- m_mueller 2y ago
  Narrator: It hasn't.
- stogot 2y ago
  I read that recently after their security breaches
stogot 2y ago
I have had similar issues. And I know a fair amount about these systems, and still cant figure what the backend mess looks like that results in these problems. I found a reproducible login bug on Teams and spent a while trying to figure out who to report it to and gave up
chrisandchris 2y ago
> [...] is their log in. On every first try, I cannot log in into Azure Portal. I chlick "try again", it works. And it's like that for months, if not years. IMHO it says a lot of your culture if every first interaction of your customers with your product end with an error - and you simply don't care to fix it.
- paulryanrogers 2y ago
  I wonder if things like this are due to testing only on the vendor's own/preferred browser. In this case Edge?
  - rat9988 2y ago
    Almost 0 chance.
- velcrovan 2y ago
  [flagged]
  - deathanatos 2y ago
    Every login I've ever done into the Azure portal is like the upstream describes: an absurd number of redirections and refreshes that leave you wondering "is it supposed to work like that?" I've also encountered strange bugs, like asking to log into tenant A and getting logged into, instead, tenant B. In a loop, effectively locking me out. The exact quirks and bugs seem to come and go, I presume as the code is changed & updated.
    - velcrovan 2y ago
      Sure, but Azure also exposes an extremely large array of knobs and buttons that put the tenant admin squarely in control of what "login" means in the first place: the kinds of authentication allowed or required, by whom, under what risk profiles, for which applications, etc. If you feel like it is screwed up there is, as likely as not, action that it is the tenant admin's — not MS's — responsibility to take, to fix it. I don't know what to tell you about refreshes, that's just how Oauth works mostly. I'm tempted to take a video of myself logging into the Azure portal right now just to ask what about it is so weird.
moi2388 2y ago
It’s not. Their security has known massive issues and security holes, and they consciously do not fix them. Look at the CVEs for azure, msal and Active Directory for some good laughs. Now realise most governments, large companies and education works on this
hedora 2y ago
I’ve never used Azure, but my kid plays Minecraft (offline), and got forced into using a Microsoft account to login. From what I can tell, they use it as proving ground for whatever crap they’re going to force on other applications. After getting it to work on a raspberry pi, I decided I wouldn’t use any logged in Microsoft product in a professional setting. Anyway, I’m sure they’ll eventually unify GitHub and LinkedIn login the same way they did with Minecraft. At that point, our industry will implode.
blitzar 2y ago
When you come from bare metal, working with any of the cloud providers feels totally inconsistent and patched together.
7bit 2y ago
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.

mrweasel 2y ago

> It feels totally inconsistent and patched together. I believe that multiple article, e.g. on The Register, has mentioned that people who have left the Azure team has routinely complained that the pace was to high, and that everything is pretty much duct taped together. This was years ago, so it may have changed.

m_mueller 2y ago
Narrator: It hasn't.
stogot 2y ago
I read that recently after their security breaches

stogot 2y ago

I have had similar issues. And I know a fair amount about these systems, and still cant figure what the backend mess looks like that results in these problems. I found a reproducible login bug on Teams and spent a while trying to figure out who to report it to and gave up

chrisandchris 2y ago

> [...] is their log in. On every first try, I cannot log in into Azure Portal. I chlick "try again", it works. And it's like that for months, if not years. IMHO it says a lot of your culture if every first interaction of your customers with your product end with an error - and you simply don't care to fix it.

paulryanrogers 2y ago
I wonder if things like this are due to testing only on the vendor's own/preferred browser. In this case Edge?
- rat9988 2y ago
  Almost 0 chance.
velcrovan 2y ago
[flagged]
- deathanatos 2y ago
  Every login I've ever done into the Azure portal is like the upstream describes: an absurd number of redirections and refreshes that leave you wondering "is it supposed to work like that?" I've also encountered strange bugs, like asking to log into tenant A and getting logged into, instead, tenant B. In a loop, effectively locking me out. The exact quirks and bugs seem to come and go, I presume as the code is changed & updated.
  - velcrovan 2y ago
    Sure, but Azure also exposes an extremely large array of knobs and buttons that put the tenant admin squarely in control of what "login" means in the first place: the kinds of authentication allowed or required, by whom, under what risk profiles, for which applications, etc. If you feel like it is screwed up there is, as likely as not, action that it is the tenant admin's — not MS's — responsibility to take, to fix it. I don't know what to tell you about refreshes, that's just how Oauth works mostly. I'm tempted to take a video of myself logging into the Azure portal right now just to ask what about it is so weird.

moi2388 2y ago

It’s not. Their security has known massive issues and security holes, and they consciously do not fix them. Look at the CVEs for azure, msal and Active Directory for some good laughs. Now realise most governments, large companies and education works on this

hedora 2y ago

I’ve never used Azure, but my kid plays Minecraft (offline), and got forced into using a Microsoft account to login. From what I can tell, they use it as proving ground for whatever crap they’re going to force on other applications. After getting it to work on a raspberry pi, I decided I wouldn’t use any logged in Microsoft product in a professional setting. Anyway, I’m sure they’ll eventually unify GitHub and LinkedIn login the same way they did with Minecraft. At that point, our industry will implode.

blitzar 2y ago

When you come from bare metal, working with any of the cloud providers feels totally inconsistent and patched together.

7bit 2y ago

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.