Region not available for model deployments in Azure AI Foundry

Hien Duong 25 Reputation points
2026-06-12T13:14:05.1866667+00:00

Subscription type: Pay-as-you-go (new)

Few model deployments (tried gpt-4.1) no available regions to choose. Not sure if any other information needed.

User's image

Foundry Models
Foundry Models

A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference

Answer accepted by question author
Sina Salam 31,456 Reputation points Volunteer Moderator
2026-06-15T15:10:19.87+00:00

Hello Hien Duong,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you stated that "Region not available for model deployments in Azure AI Foundry."

Your Azure AI Foundry project is not the main problem, because GPT‑4.1 is available in Foundry, but your new Pay‑as‑you‑go subscription currently has no deployable GPT‑4.1 quota/entitlement for the selected deployment type in any eligible region. Because quota is scoped by subscription, model, region, and deployment type, Foundry correctly hides all regions when none have usable quota. - https://learn.microsoft.com/en-us/azure/foundry/openai/quotas-limits, https://learn.microsoft.com/en-us/azure/foundry/how-to/quota

The best fix is to go to Foundry > Operate > Quota, check GPT‑4.1 2025-04-14 for the intended deployment type, and request quota for a supported region/deployment type combination. Use Global Standard first unless you have strict data-residency requirements. After quota is approved and visible, the region list will become selectable and deployment will succeed. - https://learn.microsoft.com/en-us/azure/foundry/how-to/quota, https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/deployment-types, and https://learn.microsoft.com/en-us/azure/foundry/foundry-models/concepts/models-sold-directly-by-azure-region-availability gives more insights and steps to fix it.

I hope this is helpful! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Karnam Venkata Rajeswari 5,255 Reputation points Microsoft External Staff Moderator
    2026-06-12T13:30:33.1833333+00:00

    Hello @Hien Duong

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

    Thank you for sharing the details and the screenshot.

    The deployment limitation is caused by absence of available GPT‑4.1 quota or entitlement across all supported regions for the subscription.

    At least one region must have available quota for the deployment option to appear. When this condition is not met, all regions are automatically filtered out, resulting in “No available regions” being displayed.

    .The model remains available in Azure AI Foundry, however deployment requires at least one region with assigned and available quota.Once quota is provisioned in any supported region, the platform will automatically enable region selection and allow deployment to proceed.

    Although GPT‑4.1 is visible in Azure AI Foundry, deployment depends on the following:

    • Model entitlement enabled for the subscription
    • Available quota or capacity in at least one supported region
    • Alignment of deployment type with supported regions

    In this case, all regions are marked as “Insufficient quota”, which confirms:

    • No deployable GPT‑4.1 quota is currently available across supported regions
    • The system cannot identify any eligible region for deployment
    • The UI therefore hides region selection

    This condition is most commonly due to missing or unallocated quota/capacity, rather than configuration issues.

    Please check if the following steps help-

    1. Verifying quota and entitlement status
      1. Navigate to: Foundry > Management Center > Quotas
      2. Review GPT‑4.1 quota across regions
      3. Confirm whether quota is:
        • Not assigned
        • Set to zero
        • Fully consumed
      At least one region must reflect available quota before deployment becomes possible.
    2. Validating using an alternate model Attempt deployment using:
      • GPT‑4o
      • GPT‑4o‑mini
      Successful deployment confirms the issue is isolated to GPT‑4.1 quota/entitlement, not a general deployment limitation.
    3. Requesting quota or capacity allocation
      1. Please submit a quota increase or enablement request for GPT‑4.1
      2. Include expected workload and target regions
      Once quota is approved and assigned, eligible regions will automatically appear in the selection list.
    4. Validating project and deployment configuration
      1. Ensure the project is created in a supported region
      2. Confirm deployment type compatibility (Standard / Global Standard / PTU)
      Configuration alignment is required but cannot override missing quota or entitlement limitations.

    The following references might be helpful , please check them out

    Please let us know if the response was helpful

     

    Thank you

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.