Unable to deploy GLM-5.3-Flash on Foundry

Truong Phung Quang 0 Reputation points
2026-09-28T03:53:37.4466667+00:00

We have an existing East US 2 subscription with Fireworks AI enabled. We can deploy GLM-5.3 successfully, but deployments of GLM-5.3-Flash and FW-DeepSeek-v4.1-Flash fail with the portal reports insufficient quota.

To rule out a quota issue, we created a new test subscription and were able to deploy GLM-5.3-Flash successfully. We also submitted and received approval for a quota increase on the original subscription, but the issue persists.

Can anyone explain why the older subscription cannot deploy GLM-5.3-Flash while the new subscription can? And how can we deploy GLM-5.3-Flash on our sub?

Thankyou

Foundry Models
Foundry Models

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

0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest
  1. Maciej Kępa 0 Reputation points
    2026-09-28T06:46:29.94+00:00

    Hey,

    The first thing I would check is the Fireworks Global Standard quota on the original subscription. Microsoft lists both FW-GLM-5.3-Flash and FW-DeepSeek-V4.1-Flash as Global Standard models.

    Fireworks has separate Global Standard and Data Zone Standard quota pools, each shared across Fireworks models. Deploying GLM-5.3 successfully does not mean that sufficient Global Standard quota remains for Flash. An increase applied to the Data Zone pool would not resolve a Global Standard shortage.

    I would suggest:

    1. Compare the successful and failed deployments using the same model version, region, deployment type, and requested TPM.
    2. Verify that the approved increase was applied specifically to Fireworks Global Standard on the original subscription in East US 2, and check the remaining quota after existing allocations.
    3. Retry with a smaller TPM allocation that fits the available quota.

    If the correct pool has sufficient quota and the deployment still fails, follow up on the existing case or open an Azure support request, including the details and ask support to verify the effective quota and deployment eligibility on the original subscription.

    Also, if the quota increase approval was recent, it may take up to 24h to reflect changes in your system.

    References:

    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.