An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
Hello Robert Janssen - Zenarate,
Thank you for reaching out on the Microsoft Q&A.
When you reduce quota for an existing model, the changes don’t always reflect in the UI immediately. This usually happens because the backend takes some time to process and sync the updated values across resources.
One thing you can try is refreshing and rechecking after a short while. In most cases, the updated quota becomes visible once the system completes processing. You may also want to verify the quota at the API level, since sometimes the API reflects the updated numbers earlier than the portal UI.
Another possibility is that the newer model can’t take the reallocated quota yet because the old model’s quota reduction hasn’t fully propagated. This is more of a temporary synchronization delay than an actual issue with your setup.
In short, this behavior is expected, and the quota should update after some time. Once it syncs, you should be able to allocate the freed-up quota to the newer model.
I Hope this helps. Do let me know if you have any further queries.
Thankyou!