Region-access support requests for PostgreSQL Flexible Server are stuck in an AI triage loop

As an Azure MVP, I want to flag a real gap I just hit firsthand.

I opened a support ticket (Issue type: Service and subscription limits (quotas), Quota type: Region access) because a subscription of ours couldn'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... open a support request with Issue type of 'Service and subscription limits'", exactly as documented.

 Over 9 days, I got three AI-generated responses (case #2608260040010469), all repeating the exact same generic instructions I had already followed and explicitly confirmed I'd followed — twice. No human engineer was ever assigned (confirmed via the Support API: supportEngineer: {} the entire time). The case was even auto-flagged for closure citing "no response," despite an active reply from me on record before that message was sent.

 This isn't a one-off complaint about response speed — it's a structural problem: region-access requests for this service appear to route through an automation loop that can't recognize "I already did what you're asking" and doesn't have a reliable escalation path to a human, even after an explicit "I'm still having an issue" signal.

 Has anyone else hit this on region-access requests specifically? And is there a known way to get these routed to an actual engineer instead of restarting the same script every 24-48h?