Support escalation guide

Self-service quota tooling resolves most requests, but some capacity problems still require Microsoft intervention. Use this guide to recognize when escalation is necessary and how to submit a support ticket with the required context so you don't lose time gathering details after the ticket opens.

When to escalate

• Restricted regions or zones: Subscriptions cannot deploy to a region or zone because of access restrictions that only Microsoft can lift.
• Non-adjustable quotas: The My quotas blade flags the target quota as non-adjustable or the automated request is denied.
• Service-specific limits: Services such as Azure Cosmos DB require engineering review to raise account/container limits or throughput ceilings.
• Capacity SLA claims: Capacity reservations fail to meet the SLA despite available quantity, requiring investigation and potential credits.

Pre-submission checklist

• Confirm you have Owner, Contributor, or Support Request Contributor rights on the subscription; without appropriate RBAC the portal blocks ticket creation.

Creating the request

1. Open the Azure portal, select the ? icon, and choose Create a support request.
2. On the Problem description tab, select Service and subscription limits (quotas), choose the subscription, and pick the relevant quota type (for example, Compute-VM (cores-vCPUs), Azure Cosmos DB, or Microsoft Fabric).
3. Provide detailed problem statements, including region, VM series, desired quota value, and deployment blockers.
4. Attach supporting files (screenshots, export logs) and specify severity and preferred contact method.
5. Submit and capture the support request ID for tracking.

Region and zone access workflow

• When requesting region or zone enablement, list all regions, VM series, and logical zones required for upcoming deployments within the ticket.
• Reference prior approvals if recycling subscriptions so Microsoft can reconnect previously granted access.