A few interpretations:
- Folks on Azure are active-active in multiple availability zones
- Most of those using Azure are not impacted by this particular outage
- Azure isn't widely used
...
- Folks on Azure are active-active in multiple availability zones
- Most of those using Azure are not impacted by this particular outage
- Azure isn't widely used
...
AWS and GitHub seem to crater right when everyone is using them the most (i.e. 10am EST on a Tuesday), so there is bound to be far more discussion around these occurrences since everyone is wired on coffee, ass-in-chair, frustrated that they can't get any work done. People usually don't get out of bed and then get on the internet to complain about a transient outage that occurred while they were asleep.
Why would people on Azure be more likely than people on AWS to have redundancy? Anyway, in the recent AWS outages, multiple AZs didn't help much. Needed to be in multiple regions.
AWS is far more popular in general, but especially with smaller teams that are more self-directed, start with prototypes and iterate from there. It wouldn't surprise my if the latter often only built in redundancy after learning lessons the hard way, even though AWS provides the ability to do so from the get go.
Purely conjecture, but that skew in the customer type is definitely there.
Porting over to Azure AD probably wasn’t such an issue then, as most firms would lift&shift their on-prem to the cloud, keeping the same configurations.