zlacker

> notable that they blame "our upstream provider" when it's quite literally the same company

As in why don't they mention Azure by name?

Or as in there shouldn't be isolated silos?

>>tbrown+(OP)
I get your point, but it just sounds a bit funny when it's an artefact of corporate structure that it's true.

Like imagine if AWS was composed of separate companies for different services - Fargate was an Heroku acquisition say - and then they all went down and blamed their 'upstream provider' because they can't work without say VPC or EC2 availability.

I think that's all GP meant, it just reads a bit funny, not that it's wrong.

>>tbrown+(OP)
Yup, they didn't mention it by name, it was stated as "our upstream provider".

>>tbrown+(OP)
A few years ago I talked to an developer advocate for Azure. I wanted to know why it took for ever when you wanted a new public IP. My take was that it felt like they went out on the internet to look for an IP to purchase from a 3rd. party. The answer I got was that do to the silos within Microsoft it might as well be a 3rd party supplier. The slowness is exactly because IPs are/were a managed by another Microsoft entity, who views any interaction, even within the company, as hostile.