Microsoft: Unable to delete ide05 due to remaining managed compute deployments

Question

Microsoft: Unable to delete ide05 due to remaining managed compute deployments

Mahamed Dalal 0

Problem description

I am trying to delete the Azure AI Foundry resource named ide05 in the resource group AI_Studio in East US, but the deletion fails with the error "CannotDeleteAccountWithManagedComputeDeployments". The documented cause is that there are still 2 managed compute deployments attached, which block the deletion.

Environment

Azure AI Foundry using a Microsoft.CognitiveServices/accounts resource in East US region.

What I've already tried

I reviewed initial diagnostics indicating no regional or platform outage, and confirmed that the account still has 2 managed compute deployments attached. I attempted to delete these deployments via the Azure portal and Azure CLI, but the delete operation still failed with the same error. I also checked for service health issues, resource locks, private endpoints, and permission issues, but found no resolution.

Current status

The deletion is still blocked by the remaining managed compute deployments. I am seeking guidance on how to identify and fully remove these deployments or resolve the dependency issue to successfully delete the ide05 resource.

Maraiah Kasetti (Wipro Limited) 85 Reputation points Microsoft External Staff Moderator

2026-11-02T23:21:53.46+00:00

Hello @Mahamed Dalal ,

Thanks for the question and using Q&A forum.

We are actively working on this issue and we will get back to you as soon as possible.

Thank you for your patience and understanding!

Regards,

Maraiah
Maraiah Kasetti (Wipro Limited) 85 Reputation points Microsoft External Staff Moderator

2026-11-02T23:31:35.5266667+00:00
Hello @Mahamed Dalal ,

The most likely cause is that one or more managed online endpoints still exist under the workspace (or under a project, if "ide05" is a hub). Azure won't delete the parent resource until those endpoints are removed. We haven't confirmed this for your resource yet, because we haven't reviewed your error details.

Step 1: Run az ml online-endpoint list --resource-group <your-rg> --workspace-name ide05 -o table.

Why this matters: it shows exactly which endpoints are blocking the delete.

How to verify: record each endpoint's name and provisioning state.

Step 2: Run az ml online-endpoint delete --name <endpoint-name> --resource-group <your-rg> --workspace-name ide05 --yes for each endpoint.

Why this matters: this releases the managed compute and stops the hourly charges for it.

How to verify: running the list command again returns no endpoints.

Step 3: Delete "ide05" again.

How to verify: the resource no longer appears in its resource group.

Reference: https://stackoverflow.com/questions/77230710/azure-machine-learning-online-endpoint-schedule-cost-management (shows the SDK v2 delete for online endpoints)

Your answer

Maraiah Kasetti (Wipro Limited) 85 Reputation points Microsoft External Staff Moderator

2026-11-02T23:21:53.46+00:00

Hello @Mahamed Dalal ,

Thanks for the question and using Q&A forum.

We are actively working on this issue and we will get back to you as soon as possible.

Thank you for your patience and understanding!

Regards,

Maraiah
Maraiah Kasetti (Wipro Limited) 85 Reputation points Microsoft External Staff Moderator

2026-11-02T23:31:35.5266667+00:00

Hello @Mahamed Dalal ,

The most likely cause is that one or more managed online endpoints still exist under the workspace (or under a project, if "ide05" is a hub). Azure won't delete the parent resource until those endpoints are removed. We haven't confirmed this for your resource yet, because we haven't reviewed your error details.

Step 1: Run az ml online-endpoint list --resource-group <your-rg> --workspace-name ide05 -o table.

Why this matters: it shows exactly which endpoints are blocking the delete.

How to verify: record each endpoint's name and provisioning state.

Step 2: Run az ml online-endpoint delete --name <endpoint-name> --resource-group <your-rg> --workspace-name ide05 --yes for each endpoint.

Why this matters: this releases the managed compute and stops the hourly charges for it.

How to verify: running the list command again returns no endpoints.

Step 3: Delete "ide05" again.

How to verify: the resource no longer appears in its resource group.

Reference: https://stackoverflow.com/questions/77230710/azure-machine-learning-online-endpoint-schedule-cost-management (shows the SDK v2 delete for online endpoints)