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 in Foundry Models

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anshika Varshney 12,365 Reputation points Microsoft External Staff Moderator
    2026-03-12T18:20:10.1466667+00:00

    Hi Kyle F

    If your Kimi 2.5 quota increase was approved but is still not showing in Azure AI Foundry, this is usually due to quota propagation or portal refresh behavior, not because of how you are using the model.

    Here are a few things you can check.

    First, please confirm that you are looking at the correct subscription and region in Azure AI Foundry. Quota is applied per subscription and per region. If the Foundry project or hub is pointing to a different region, the increased quota will not appear there.

    Second, check quota from the Foundry Quota page, not from deployment or usage views. In Foundry, go to Operate and then Quota. This is the only place where updated limits are reflected.

    Third, make sure you have the right permissions to view quota changes. To see updated quota, your account needs Cognitive Services Usages Reader access on the subscription. Without this role, the portal may still show old values.

    Fourth, keep in mind that quota updates are not instant. For some models like Kimi 2.5, approved quota can take time to fully sync across backend systems. During this time, the portal and actual usage may still behave as if the old limit is applied.

    Also note that Kimi models are Foundry base models, and their quota handling is slightly different from Azure OpenAI models. Because of this, quota visibility can lag even after approval.

    You can find official guidance on viewing and managing Foundry quotas here https://learn.microsoft.com/azure/foundry/how-to/quota

    And details about the Kimi 2.5 model availability in Foundry here https://ai.azure.com/catalog/models/Kimi-K2.5

    If everything above looks correct, this is typically a backend sync delay, and the quota should start reflecting once the update finishes propagating.

    Hope this helps explain what is happening and what to check.

    If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

    Thankyou!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

  2. AI answer

    2026-03-12T17:26:16.9166667+00:00

    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:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.