Microsoft Foundry: I can not deploy LLMs on Foundry

Hi @JingJing Bao

This occurs because new model series (like gpt-5.4-nano and gpt-5.1) do not have default Tokens-per-Minute (TPM) quota allocated to Pay-As-You-Go subscriptions yet, causing Default settings to fail.

2 Ways to Fix This:

1. Use Custom Settings (Quick Fix): Click Deploy > Custom settings (instead of Default settings). Change the Region / Deployment SKU to a region where your subscription has available TPM capacity.
2. Request Baseline Quota: If all regions show "Insufficient quota", submit the initial quota request form at aka.ms/oai/stuquotarequest to allocate baseline TPM for the gpt-5.x model family to your subscription.

Ref: Deploy Microsoft Foundry Models & Quota Management

Hello @JingJing Bao ,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

Thank you for sharing the details and screenshot. After reviewing the deployment behavior and the message shown in the deployment dialog, the issue appears to be occurring during quota/capacity validation for the selected deployment configuration, rather than during model discovery.

The model remains available in the Foundry Model Catalog; however, the selected deployment path is currently unable to obtain the required quota allocation or capacity needed to create the deployment.

One important observation is that the issue description references gpt-5.1, while the screenshot shows gpt-5.4-nano. Since quota is evaluated independently for each:

• Model and model version
• Deployment type
• Azure region
• Subscription quota allocation

confirming the exact model experiencing the issue will help determine whether the behavior is isolated to a specific model or affects multiple GPT models.

The screenshot provides an important diagnostic indication:

Default settings

• "Set to global standard and default quota"
• Appears unavailable

Custom settings

• "Set your own SKU, quota, PTU, spillover, and guardrails"
• Remains available

This indicates that the default deployment configuration is currently unable to satisfy the required quota/capacity requirements for the selected model and environment.

This does not necessarily mean that the model is unavailable or that all deployment options are blocked. Instead, it suggests that the limitation is related to the selected deployment configuration and available quota/capacity.

The availability of Custom settings indicates that alternative deployment configurations can be reviewed. Deployment success will still depend on whether sufficient quota and capacity are available for the selected configuration.The screenshot provides an important diagnostic indication:

Default settings

• "Set to global standard and default quota"
• Appears unavailable

Custom settings

• "Set your own SKU, quota, PTU, spillover, and guardrails"
• Remains available

This indicates that the default deployment configuration is currently unable to satisfy the required quota/capacity requirements for the selected model and environment.

This does not necessarily mean that the model is unavailable or that all deployment options are blocked. Instead, it suggests that the limitation is related to the selected deployment configuration and available quota/capacity.

The availability of Custom settings indicates that alternative deployment configurations can be reviewed. Deployment success will still depend on whether sufficient quota and capacity are available for the selected configuration.

For the previous deployments, the behavior does not necessarily indicate a change in Model Catalog availability.

This can occur because deployment validation evaluates the current quota and capacity conditions at the time of deployment. Availability may vary depending on:

• Selected model/version
• Deployment type
• Azure region
• Subscription quota allocation
• Existing deployments consuming quota
• Current available capacity

For example, quota allocated for an existing model deployment does not automatically provide quota for another model or model version.

A deployment that succeeded previously may fail later if:

• A different model/version is selected.
• Existing deployments consume the available quota allocation.
• The selected region has limited capacity for that model.
• The selected deployment type requires quota that is currently unavailable.

Foundry quota availability should therefore be evaluated based on the specific combination of model + region + deployment type + subscription

Please check if the following steps help-

1. Confirming the Deployment Details Please confirm the following:
   • Exact model name and version:
   • The issue description mentions GPT-5.1.
   • The screenshot shows GPT-5.4-nano.
   • Azure region where deployment is being attempted.
   • Deployment type selected:
   • Global Standard
   • Standard
   • Provisioned (if applicable)
   • Subscription type:
   • Pay-As-You-Go
   • Enterprise Agreement
   • CSP
   • Trial
   • Other subscription offers
   This information will help determine whether the issue is model-specific, region-specific, or subscription-related.
2. Testing Deployment Using Custom Settings Since Custom settings remains available in the deployment dialog:
   1. Open the deployment workflow.
   2. Select Custom settings instead of Default settings.
   3. Review the available deployment configurations.
   4. Check whether another supported deployment type is available.
   5. If the deployment experience allows, test with an appropriate TPM allocation.
   6. Verify whether the deployment completes successfully.
   This step helps determine whether the issue is limited to the default Global Standard deployment path or affects all available deployment options.
3. . Reviewing Model-Specific Quota Allocation Navigate to: Microsoft Foundry portal → Management Center → Quota Review the following:
   • Total quota
   • Allocated quota
   • Available quota
   • Existing deployments consuming quota
   • Affiliated deployments using the same quota pool
   If available quota is fully allocated:
   • Review existing deployments consuming quota.
   • Reduce TPM allocations for unused or oversized deployments where appropriate.
   • Remove unused deployments if they are no longer required.
   • Retry deployment after quota changes are reflected.
4. Validating Regional Availability Quota and capacity availability can vary by region. Recommended validation:
   • Attempt deployment in another supported region.
   • Compare the result using the same model and deployment type.
   If deployment succeeds in another region, this would indicate a regional capacity limitation rather than a model availability issue.
   1. Verifying access Permissions
   If quota information appears incomplete or unavailable, verify that appropriate permissions are assigned: Cognitive Services Usages Reader
   • Required to view quota information.
   Cognitive Services Contributor
   • Required for resource management operations.
   Owner or Contributor
   • Required for certain subscription-level quota management actions.
   Insufficient permissions may prevent accurate quota visibility within the portal.

The following references might be helpful , please check them out

• Deploy Microsoft Foundry Models in the Foundry portal - Microsoft Foundry | Microsoft Learn
• Manage and increase quotas for resources - Microsoft Foundry | Microsoft Learn
• Azure OpenAI in Microsoft Foundry Models Quotas and Limits - Microsoft Foundry | Microsoft Learn
• Understanding deployment types in Microsoft Foundry Models - Microsoft Foundry | Microsoft Learn
• Foundry Models sold by Azure - Microsoft Foundry | Microsoft Learn
• Role-based access control for Azure OpenAI (classic) - Microsoft Foundry (classic) portal | Microsoft Learn
• Microsoft Foundry Service: Request for Quota Increase

Please let us know if the response was helpful

Thank you