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
Yes. This can be expected for a newly converted or newly active Pay-As-You-Go subscription.
Quota in Foundry is assigned at the subscription level and is scoped per region, per model, and per deployment type in Tokens-per-Minute (TPM). A model can appear in the catalog but still show no usable quota in Operate > Quota or show 0/0 TPM, which means there is no initial baseline allocation/entitlement available yet for that subscription-model-region combination. In that state, deployment is blocked.
For the scenarios described:
- Is 0/0 TPM normal for multiple models on a new Pay-As-You-Go subscription?
Yes. The documented quota model is per subscription, per region, and per model. The accepted Microsoft Q&A guidance also states that when a model appears in the catalog but shows insufficient quota and no quota row, it typically means the subscription does not yet have a default TPM allocation for that model. - Does the subscription need an initial quota/entitlement first?
Yes. A deployment requires available quota for that model. If no baseline allocation exists, the model cannot be deployed until quota is granted. - Is there an activation or provisioning step after converting from introductory credit to Pay-As-You-Go?
No separate activation step is documented in the provided material. The supported path described is quota assignment and quota request management, not a post-conversion activation workflow. - What is the correct way to obtain quota?
Use one of these supported paths:- In Foundry, go to Manage > Quota.
- Review the model deployment entry and current allocation.
- If quota exists elsewhere, reallocate TPM from affiliated or other deployments to free capacity.
- If no usable quota exists, select Request quota in the upper-right corner of the Quota page, or submit the quota increase request form: https://aka.ms/oai/stuquotarequest
Additional points supported by the documentation:
- Quota changes can take up to 15 minutes to propagate after editing allocation or submitting a request.
- Quota increase requests are processed in received order, with priority for customers actively using existing quota.
- Quota increases are supported for Foundry Models sold by Azure, Azure OpenAI models, and Anthropic models. Except for Anthropic models, models from partners and community do not support quota increases.
So for multiple providers showing 0/0 TPM, the practical interpretation is:
- the subscription currently has no deployable quota for those model/region/deployment-type combinations, and
- the next action is to check Manage > Quota, then request quota where supported, or reallocate existing TPM if any is already assigned.
- Deploy Microsoft Foundry Models in the Foundry portal
- Manage Azure OpenAI in Microsoft Foundry Models quota
- Manage Azure OpenAI in Microsoft Foundry Models quota (classic)
- Manage Azure OpenAI in Microsoft Foundry Models quota
- Microsoft Foundry Models quotas and limits
- GPT-5.2 appears in Foundry catalog but all regions show insufficient quota; cannot request quota - Microsoft Q&A