Azure Machine Learning: Deletion of orphaned registry resources — Assistance Needed

Welcome to Microsoft Q&A!

Note: This is the Nederlands‏ (nl-nl) forum. I kindly recommend posting your question in Nederlands, as this will make it easier for other forum members and subject matter experts to engage with your inquiry. If you prefer to post in English, you may also consider using the English forum, where a larger English-speaking audience can review and respond to your question. Thank you for your understanding.

Thank you for your understanding and for providing such detailed information about the issue and the troubleshooting you have already completed.

Based on the behavior you described, this appears to be an orphaned Azure Machine Learning service-managed resource scenario, rather than a typical resource-group deletion issue.

Azure uses deny assignments to protect certain managed resources. A deny assignment can prevent specific Azure resource actions even when a role assignment would otherwise grant the user access. Azure also creates and manages deny assignments for generally available scenarios, and system-protected deny assignments cannot be directly edited or deleted.

In your situation, the Azure Machine Learning registry has already been removed, while related resources appear to remain subject to the deny assignment. This may indicate that the expected cleanup was not fully completed, which would be consistent with the permission/deny-assignment errors you are receiving when attempting to delete the remaining resources.

At this stage, I would not recommend continuing with additional force-delete attempts.

Instead, please open an Azure technical support request for the affected subscription and select Azure Machine Learning as the service most closely related to the issue.

Moreover, I want to clarify why escalation is appropriate in this case. Microsoft Q&A is a community technical forum, so I can help explain the documented Azure behavior, review the symptoms, and point you toward the appropriate resolution path. However, troubleshooting an orphaned service-managed resource that remains protected by an Azure-managed deny assignment may require investigation of the affected subscription and resources beyond what can be performed through a public forum.

An Azure Support request is therefore the appropriate next step. Azure Support can investigate the specific affected resource and subscription. When creating a technical support request, make sure that you select the subscription where the affected resources reside and provide the detailed resource and error information above.

Once Azure Support has investigated the remaining service-managed protection or dependency and confirmed that the issue has been addressed, retry the resource deletion and verify that the orphaned resources and resource group can be successfully removed.

I hope this helps clarify why the resources cannot be removed through the usual deletion path and provides a clear next step toward getting the orphaned resources cleaned up.

References:

List Azure deny assignments - Azure RBAC | Microsoft Learn

az ml registry | Microsoft Learn

How to create an Azure support request - Azure portal | Microsoft Learn

If you find it useful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.