Custom Neural Model Training Stuck at 0% and Unable to View Cognitive Services Quotas

Question

Hello Microsoft Support,

I’m experiencing an issue with Azure Document Intelligence (Custom Neural Model training) where every training operation gets stuck at 0% progress indefinitely. This happens even when creating brand‑new projects, new containers, and even new Document Intelligence resources.

I have in the past trained the models(several are stuck) ok and training completed. Region UK south.

When I delete the stuck models via the cli I get a 204 request(success) but the models continue showing in the model list as running.

Additionally, when I attempt to check Cognitive Services usage or quotas through the Azure CLI/ARM management API, the result is always empty, meaning I cannot see any Cognitive Services quota information for my subscription or region

Answer 1

I am on S0 and my model only has approximately 500 pages. Not sure it is a quota issue since it's just at the beginning of the month and this should have reset. I only have two new pages this month so the rest have trained ok severally for a couple of months

Answer 2

The behavior matches a quota/limit or backend provisioning issue affecting custom neural model training and quota visibility.

For Document Intelligence v4.0 custom neural models, the following limits apply per resource:

• Training dataset size (neural and generative): 1 GB, not adjustable on either Free (F0) or Standard (S0).
• Max number of pages for neural/generative training: 50,000 pages, not adjustable.
• Custom neural model training time:
  • Free (F0): 10 hours per month.
  • Standard (S0): No hard limit, but billed by the hour, with 10 free hours each month and the ability to request increases.

If the monthly 10‑hour free training allowance is exhausted on F0, or if a custom quota configuration is mis‑applied on S0, training jobs can remain in a non‑progressing state while still being accepted. Since training time is tracked per calendar month, the counter resets monthly. For higher training volume on S0, a support request is required to increase the monthly training limit.

In addition, there is a hard limit on the number of custom neural models per resource:

• Max number of neural models: 100 on Free (F0), 500 on Standard (S0), not adjustable.

If the resource is at or beyond this limit, model management operations can behave inconsistently (for example, models appearing to remain in a running state even after delete calls return 204). Cleaning up models below the limit and then re‑checking can help, but if the portal or control plane is stuck, support intervention is needed.

For the separate issue where Cognitive Services quotas appear empty in the portal/CLI:

• When the quota page is empty or shows no allocations, the required role at subscription level is Cognitive Services Usages Reader. Without this role, quota data will not be returned even though the resource exists.
• If the Request quota button is disabled, Owner or Contributor role on the subscription is required. Some model/region combinations do not support quota increases.
• After any approved quota change, allow up to 15 minutes for propagation and refresh the Quota page. If the change is still not visible after 24 hours, Azure support must be contacted.
• If a specific model’s quota cannot be found, verify that the model is available in the selected region.

Given the symptoms:

1. Verify that the subscription has Cognitive Services Usages Reader at the subscription scope and that the correct subscription and region (UK South) are selected when viewing quotas.
2. Confirm whether the resource is on Free (F0) and whether the 10 hours/month of custom neural training may have been consumed. If so, either wait for the next calendar month or move to Standard (S0) and, if needed, request a training‑limit increase.
3. Check that the number of neural models is below the documented maximum (100 on F0, 500 on S0). If near or above the limit, reduce the number of models and then retry training.
4. If quota pages remain empty despite correct roles and the training jobs continue to stay at 0% or models remain stuck in Running after 204 deletes, open an Azure support request. This is necessary both to:
   • Investigate and fix the control‑plane state for the stuck models and training jobs in UK South.
   • Investigate the quota/usage visibility issue for Cognitive Services on the subscription.

These actions align with the documented limits and the guidance to use Azure support when quota changes or control‑plane state do not behave as expected.

---

References:

• Service quotas and limits
• Document Intelligence custom neural model
• Manage and increase quotas for resources with Microsoft Foundry (Foundry projects)
• Unable to deploy resources, can't view Quotas or request increases - Microsoft Q&A