Support escalation guide

Self-service quota tooling handles adjustable quota requests, and some capacity problems still require Microsoft intervention through a support request (Increase quota in Azure portal, Create an Azure support request). 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 reservation incidents: Capacity reservations don't behave as expected for reserved quantity, VM association, or deployment outcomes, and need Microsoft investigation through the support request path.

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

Open the Azure portal, select the ? icon, and choose Create a support request.
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).
Provide detailed problem statements, including region, VM series, desired quota value, and deployment blockers.
Attach supporting files (screenshots, export logs) and specify severity and preferred contact method.
Submit and capture the support request ID for tracking (Create an Azure support request).

Required technical evidence package

Include this data in the support request and in any follow-on escalation package:

Support request ID, subscription ID, tenant ID, region, availability zone (if relevant), and workload stamp identifier (Create an Azure support request).
Quota target details: provider namespace, quota name (for example VM family), current limit, current usage, requested limit, and requested effective date (Per-VM quota requests, Quota groups).
Reproduction details: exact deployment operation, expected result, actual result, correlation IDs, UTC timestamps, and error payloads (Create an Azure support request).
Capacity reservation details when applicable: capacity reservation group, reservation SKU, zone scope, reserved quantity, associated VM or VMSS resource IDs, and failure symptoms (Capacity reservation overview).
Impact statement: affected subscriptions, regions, SKUs, blocked release or scale event, and quantified demand window (vCPU, VM instances, or service throughput) (Manage your workload supply chain).
Attachments: screenshots, activity log exports, deployment logs, and CLI output that matches the reported timeframe (Create an Azure support request).

Escalation path on Azure surfaces

Start with an Azure support request under the relevant quota or service surface (Create an Azure support request).
Validate support outcomes when access or quota changes are applied, including region access, zonal enablement, quota limits, and reservation behavior (Region access request process, Zonal enablement request for restricted VM series, Per-VM quota requests, Capacity reservation overview).
Escalate internally only with the same SR-linked technical evidence package so Microsoft support and internal incident systems reference the same facts (Manage your workload supply chain).

Region and zone access workflow

When requesting region or zone enablement (Region access request process, Zonal enablement request for restricted VM series), 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.