Share via

Increased Quota on Kimi 2.5 in Foundry not showing 36 hours later?

Kyle F 0 Reputation points
2026-03-12T17:26:01.0766667+00:00

Hello,

I got a request to increase quota approved a few days ago and still don't have the quota increase either listed in the portal or in behavior.

Side note: I cannot open up a case in Azure either despite paying for developer support.

Azure OpenAI Service
Azure OpenAI Service

An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.

{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-12T17:26:16.9166667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Quota changes can take up to 15 minutes to propagate. If the increase still does not appear in the Azure AI Foundry portal or in behavior after several days, this indicates an issue that requires Azure support intervention.

    For Foundry/OpenAI quotas:

    1. Verify the correct subscription and region are selected when viewing quota in the Azure AI Foundry portal at Management > Quota for the relevant Foundry project or hub.
    2. Confirm the required roles on the subscription:
      • At least Cognitive Services Usages Reader to view quota.
      • Owner or Contributor to request or modify quota.
    3. If the quota page appears but the new limit is not reflected after more than 24 hours, follow the documented guidance to contact Azure support, as this is treated as a propagation issue.

    If the quota UI is empty or the Request quota button is disabled, use the troubleshooting guidance:

    • Empty quota page or no allocations: ensure Cognitive Services Usages Reader role and correct subscription selection.
    • Request quota button disabled: ensure Owner or Contributor role and check that the specific model/region combination supports quota increases.

    Because the quota increase was already approved and more than 24 hours have passed, the next step is to open a support case so an engineer can verify and correct the backend quota for the Kimi 2.5 model in that subscription/region.

    If there are issues opening a case through the normal flow, use the generic support creation entry point and select a quota-related issue type (Service and subscription limits/quotas) as shown in the quota and billing support examples in the context.


    References:

    0 comments No 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.