Azure Database for PostgreSQL Flexible Server: Region-access request in East US never escalated to a human

Question

I'm trying to understand if this is expected behavior for Azure support on region-access requests, because it doesn't match the documented 24-48h SLA.

Context: A subscription of ours can't provision Azure Database for PostgreSQL Flexible Server in East US. az postgres flexible-server list-skus --location eastus returns:

"Provisioning is restricted in this region. Please choose a different region. For exceptions to this rule please open a support request with Issue type of 'Service and subscription limits'."

What I did: Opened a support ticket exactly as documented — Issue type: Service and subscription limits (quotas), Quota type: Region access, Service: Azure Database for PostgreSQL flexible server, Region: East US.

What happened: Over 9 days, I received three AI-generated responses (case #2608260040010469), all repeating the same generic instructions I had already followed and explicitly confirmed twice. No human engineer was ever assigned — confirmed directly via the Support API (supportEngineer: {} from start to finish). The case was even auto-flagged for closure citing "no response," despite an active reply from me already on record.

My question: Is there a known escalation path to get a region-access request in front of an actual engineer on the Azure Database for PostgreSQL team, rather than restarting the same automated triage script every 24-48h? Is this the expected support experience for this specific request type (region access), or is something misconfigured on this case?