2 ms·
A lot of people are comparing AWS identities to G Suite or Apple ID. A better, more apples-to-apples comparison would be Azure Active Directory. A single AAD
by jiggawatts 5y ago
A lot of people are comparing AWS identities to G Suite or Apple ID.
A better, more apples-to-apples comparison would be Azure Active Directory.
A single AAD account enables access to: Azure DevOps, Microsoft 365 collaboration apps, remote desktop logins to servers, virtual desktops, and a bunch of other stuff.
It certainly is very convenient, but the downside is that a global outage of AAD takes down a lot of things all at once.
For example, AAD system-managed identities are used as a type of "service account" in Azure. This means that web apps can lose access to their HTTPS certificates stored in Key Vault because AAD is down, causing massive outages.
In theory, AAD has a "read-only delayed replica" as a fallback, but in practice this hasn't worked.
This is actually one of the core "philosophical" differences between AWS and Azure. The former values completely distinct services with no (or minimal) interdependencies, the latter values integrated, cohesive architectures.
In my experience Azure's approach is more convenient but more fragile. Conversely, AWS is more robust but can be super irritating for end-users.