![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 46%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Azure Content Understanding in Foundry Tools
An AI tool in Foundry for analyzing documents and media to classify content, extract entities, and generate structured understanding
The behavior described (an analyzer stuck in the Creating state for days) indicates a backend provisioning issue rather than a configuration problem in the project.
From the available guidance, analyzer creation is an asynchronous operation. When creating an analyzer via the REST API, a 201 Created response includes an Operation-Location header, and a subsequent GET on that operation URL should eventually return "status": "succeeded" once provisioning completes.
If the analyzer remains in Creating for an extended period and cannot be deleted, this matches the pattern of other Azure resources that are stuck in a pending state (for example, Azure Cache for Redis instances that cannot be deleted while still “being created”). In those cases, the resource eventually transitions to a failed state and can then be removed.
For this analyzer:
- Wait for the analyzer to transition from Creating to a terminal state (such as Failed). Once it does, delete it from the analyzer list in Content Understanding Studio.
- After deletion succeeds, recreate the analyzer (either from Content Understanding Studio or via the REST API) and verify that the new analyzer reaches the Ready state.
- If the analyzer never leaves Creating and deletion remains blocked, this is a service-side provisioning issue that requires Azure Support to intervene at the platform level.
Because this is a control-plane provisioning problem, it is not caused by the analyzer schema or content and is not something that can be fixed from the client side. It is also separate from runtime issues such as Document Intelligence requests timing out.
References:
- Create a custom analyzer (programming-language-rest)
- Create a custom analyzer (programming-language-csharp)
- Create a custom analyzer (programming-language-java)
- Create and improve your custom analyzer in Content Understanding Studio
- Create Content Understanding Standard and Pro tasks in the Microsoft Foundry (classic) portal (Preview)
- Stuck in Creating / Failed provisioning Redis Cache - Microsoft Q&A
- Document Intelligence classification and extraction requests timing out - Microsoft Q&A