Share via

gpt4-o deployment in Sweden resetting quota

Nemanja 20 Reputation points
2025-12-08T16:06:41.6533333+00:00

Since Friday we have been having issues with our sweden deployment. We were mostly experiencing timeouts but today we are seeing different issues.

On Sunday I requested a quota increase which was increased however, when we configure the usage Azure at certain point reduces the quota automatically without informing us! As you can see in the screenshot below I set it to 600000 but it sets it back to 18000! The problem is that at first it updated it but it suddenly changed, causing a production issue. It does not seem to be only for Sweden but we also see the same in France region, only for gpt4- standard data zone.

We already removed this deployment and deployed a new one but we still see the same issue of quota being reset to a lower number.

I also see other issues related to Sweden. Is this known? There is nothing on the status page.
https://v4.hkg1.meaqua.org/en-gb/answers/questions/5651825/gpt-4o-deployment-timeouts
User's image

Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
Answer accepted by question author
  1. Anshika Varshney 4,345 Reputation points Microsoft External Staff Moderator
    2025-12-08T17:24:44.9866667+00:00

    Hi Nemanja,

    Thanks for reporting this.

    In Azure AI OpenAI services, quotas are tracked per model, per region, and they can sometimes reset or auto-adjust when backend capacity changes, especially for newer or high-demand regions/models like GPT-4-o.

    A few points that might help clarify the situation:

    • Quota enforcement is region-specific: Each model deployment has its own quota limits in each region, and they do not aggregate across regions. Even if a quota increase shows successfully applied, the portal can still reset the quota if that capacity is not actually available for your subscription in that region. Microsoft Learn
    • Automatic quota adjustment: Azure may adjust available quota behind the scenes based on capacity availability or regional constraints, particularly for high-traffic regions like Sweden Central. This can sometimes result in the appearance that a quota is “reset” without a clear notification. Tracking quota limits via the Azure portal’s Quotas blade can help verify what’s actually assigned at any moment.
    • Not isolated to one region: As you noted seeing the same in France, this behavior can occur in multiple regions where demand exceeds provisioned capacity for a specific model version.

    Please share any logs or error messages you see after the reset, and we can help you outline the support ticket if needed.

    Thankyou!

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.