Cognitive Services resource stuck in Failed state — delete returns 500 InternalServerError

Question

Cognitive Services resource stuck in Failed state — delete returns 500 InternalServerError

pranit k 0

HTTP Status: 500
x-ms-failure-cause: service

Tracking info:

Request ID: 5d87e2fa-7cdb-4172-a079-b3abdc9db993
Correlation ID: 4e52b092-b8d1-4604-a1a0-691b8de0cc65
Timestamp: 2026-09-14T11:52:47 UTC

The resource is confirmed not soft-deleted (checked via az cognitiveservices account list-deleted, which returns nothing for it) — it's an active resource permanently stuck in a Failed provisioning state. This is blocking deletion of the parent resource group.

Would appreciate guidance or a backend force-delete/purge to resolve this. Happy to share the exact subscription/resource ID privately if a moderator needs it.

Ganesh Gurram 7,485 Reputation points Microsoft External Staff Moderator

2026-09-14T15:25:21.26+00:00

@pranit k We have reached out to you through private chat. Could you please provide the requested details there so that we can investigate the issue further?

Thank you for your cooperation.
Ganesh Gurram 7,485 Reputation points Microsoft External Staff Moderator

2026-09-15T12:31:10.8266667+00:00

@pranit k - Glad to know that you were able to successfully delete the resource and that the issue has been resolved.

Could you please share the steps you followed to resolve the issue? This would be helpful for other customers who may encounter a similar issue in the future.

Thank you for the update and for your cooperation.

Your answer

Ganesh Gurram 7,485 Reputation points Microsoft External Staff Moderator

2026-09-14T15:25:21.26+00:00

@pranit k We have reached out to you through private chat. Could you please provide the requested details there so that we can investigate the issue further?

Thank you for your cooperation.
Ganesh Gurram 7,485 Reputation points Microsoft External Staff Moderator

2026-09-15T12:31:10.8266667+00:00

@pranit k - Glad to know that you were able to successfully delete the resource and that the issue has been resolved.

Could you please share the steps you followed to resolve the issue? This would be helpful for other customers who may encounter a similar issue in the future.

Thank you for the update and for your cooperation.