the resource entity provisioning state is not terminal, could not be deleted

Hello Pulin Gupta,

Welcome to Microsoft Q&A .Thank you for reaching out.

The Azure AI Foundry resource is currently in a non‑terminal provisioning state (Creating). In Azure Resource Manager, a resource must reach a terminal state (Succeeded, Failed, or Deleted) before update or delete operations are allowed. While the resource remains in Creating, Azure intentionally blocks deletion and modification to prevent backend inconsistency.

This situation typically occurs when the initial provisioning workflow does not complete successfully at the control‑plane level. The resource creation request is registered, but the backend service does not return a final success or failure signal. When this happens, the resource remains locked until the provisioning state transitions.

Deletion is currently blocked as

• Delete and update operations are blocked by Azure Resource Manager while provisioning is non‑terminal
• Portal, CLI, PowerShell, and REST all follow the same enforcement path
• There is no supported force‑delete mechanism for resources stuck in Creating

The following troubleshooting steps can help to determine whether the resource can transition to a terminal state.

1. Check for active deployments at the resource‑group level

If an Azure Resource Manager deployment is still marked as running, cancelling it may allow the resource to move to Failed.

az deployment group list --resource-group <resource-group-name>

If any deployment shows Running, please cancel it

az deployment group cancel --resource-group <resource-group-name> --name <deployment-name>

After cancellation, allow a short interval and retry deletion.

2. Review the Activity Log for provisioning errors

Navigate to Resource Group > Activity Log and review entries related to the Foundry resource.

Please look for:

• Long‑running “Create” operations
• RequestConflict or AnotherOperationInProgress
• Correlation IDs tied to the original creation attempt

This step helps confirm that the issue is control‑plane related.

Azure Monitor activity log - Azure Monitor | Microsoft Learn

3. Verify whether any visible child resources exist

If any child items are visible and removable, delete those first:

• Model deployments
• Connections or endpoints shown under the Foundry resource

If no child resources are visible, this usually indicates the resource never completed provisioning.

4.As a diagmostic step  attempt resource‑group deletion

Deleting the entire resource group can confirm whether the Foundry resource is fully blocked.

az group delete --name <resource-group-name> --yes --no-wait

• If the resource group deletes successfully, cleanup is complete
• If deletion rolls back citing the Foundry resource, the backend provisioning state is still blocking deletion

Use the Azure portal and Azure Resource Manager to Manage Resource Groups - Azure Resource Manager | Microsoft Learn

5. Please allow some time for backend reconciliation

In some cases, backend jobs eventually time out and move the resource to a terminal state (Failed). Once this occurs, deletion becomes available. There is no guaranteed timeframe for this transition.

Few important limitations to note are that

• Purge APIs apply only to already deleted resources and cannot be used for resources stuck in Creating
• REST or CLI delete calls cannot bypass provisioning state checks
• Role or permission changes do not unblock this condition

Recover or purge deleted Microsoft Foundry resources - Foundry Tools | Microsoft Learn

If the resource remains in Creating after the steps above, the provisioning state must be corrected at the backend before deletion can proceed. Once the state transitions to a terminal value, normal deletion becomes possible.

 

References:

Troubleshoot common Azure deployment errors - Azure Resource Manager | Microsoft Learn

Thank you!

Hello Pulin Gupta,

Checking in to see if you had any chance to review the above response.

Do let me know if you have any further queries.

Thank you