And based on my own personal experience, even if you persevere and force them to acknowledge the problematic behaviour, they can turn around and say it's not a problem and working as intended.

For example, when using Azure Front Door, it's apparently absolutely not a problem that as yet un-cached file in their CDN downloads from their own Azure Blob storage have a maximum download speed of around 2MB (16Mb) per second:

Them:

> Hello Jonathan,

> I hope you are doing well!

> I sincerely apologize for the significant delay in our response, which was necessary to conduct further internal testing.

> After a comprehensive review, we have determined that the behavior you are experiencing is typical for this type of operation.

> This is primarily due to the connection not being entirely directly, as it must pass through Azure Front Door. This process also involves distributing the cache among point-of-presence (POP) servers, which inevitably impacts the > operation's speed. Let me provide you with documentation covering that matter:

Me:

> So to be clear, Azure Front Door maxes out at less than 2MB/s (16Mbit/s) for uncached items even when everything is on Microsoft’s own servers?

Them:

> Hello Jonathan,

> Thank you for getting back to me.

> These values may vary by region, but those particular ones apply for South Africa North.

I also tested this behaviour in US and EU regions (from an Azure VM requesting a file from Azure Blob storage in the same region as the VM but via Azure Front Door) and in EU it was also similarly limited while in the US it was only a tiny bit better.

We use Cloudflare now, cheaper, faster, configuration UI which isn't painfully slow. Not without their own recent incidents, but better than Azure Front Door 99.99% of the time.