Azure AI Foundry: Pending TPM Quota Increase Requests — Scaling Blocked

Hello @Nige Admin ,
Greetings,
We sincerely apologize for the inconvenience caused by the delay in processing your TPM quota increase requests for the Azure OpenAI Service (5.6 model family). We understand the impact this issue has had on your ability to scale deployments, and we want to help you move forward decisively.

Below are insights into how quota requests are processed, practical steps to mitigate the scaling block, and suggestions to expedite resolution.

Understanding Quota Request Processing
Here’s what you need to know about how Azure handles TPM quota increase requests:

1. Processing Order: Requests are handled in the order they are received, subject to internal review.
2. Priority Rules: Priority is typically given to customers with active inference traffic on their existing quota allocation (“active usage”), while lower-priority requests may experience delays.
3. Dependencies: Quota timelines also depend on available capacity in the requested region and the Azure team’s approval queue.

Reference: Quota Overview – Azure AI Foundry.

Check Current Quota Pool in Foundry
To confirm the status of your current usage and submitted request:

1. Log into the Azure AI Foundry portal.
2. Navigate to Manage (or Management Center) → Quota.
3. Use the Tokens Per Minute (TPM) tab to view capacity for:
   • Specific Subscription
   • Model Family (e.g., 5.6)
   • Azure Region

Compare the Used TPM against the Allocated TPM Limit. Also check if quota adjustments were enacted but not fully consumed yet.

Note: If shared quota is being used across deployments, you can adjust allocation within each deployment’s settings under the portal’s Quota Management section. Changes typically take about 15 minutes to propagate.

Reference: Manage Quotas in Azure Foundry

Mitigation Options While Quota Requests Are Pending

To minimize disruptions while waiting for the quota increase to be approved:

• Scale in Alternative Regions: If capacity is available in another Azure region, attempt to redeploy using quota in that region.
• Reallocate Existing Quota: If active deployments share quota within the same subscription, consider freeing capacity by reducing the TPM allocation on lower-priority deployments.

These adjustments can allow partial scaling until the new quota is processed.

How to Expedite Resolution

Since your quota request has been pending since August 24, 2026, which exceeds the standard processing time (3-5 business days), we recommend taking the following steps:

1. Raise an Urgent Support Ticket:
   • Go to Azure Portal > Help + Support > Create a support request.
   • Use the details below for the request:
   • Issue Type: Service and subscription limits (quotas)
   • Service: Azure OpenAI Service
   • Details to Include in the Ticket:
     • Subscription ID.
     • Region for the request.
     • Affected model family (5.6) and quota request ID(s).
     • Business impact (e.g., blocked scaling or disrupted workloads).
2. Submit Quota Request Form: Ensure the official quota adjustment form has been completed for your request. You can find it here: Quota Request Form .
3. Follow Up Directly with Support: Respond to the support ticket regularly to request status updates. Meet with your Microsoft Customer Success Account Manager (CSAM) if you have one, as they can often escalate urgent cases.

If you have any follow-up questions or need clarification on any of these steps, feel free to reach out or continue the discussion in the thread.

Thanks,