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

Mahamed Dalal 0 Reputation points
2026-11-02T22:38:44.83+00:00

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.

Microsoft Foundry
Microsoft Foundry

A unified Azure platform for creating and managing AI models, agents, and applications with built‑in enterprise security, monitoring, and governance

Answer recommended by moderator
Maraiah Kasetti (Wipro Limited) 100 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)

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. SHOUMIK CHAKRAVARTY 1,455 Reputation points
    2026-11-08T05:16:47.3666667+00:00

    Hi @Mahamed Dalal

    Welcome to the Microsoft Azure QnA Community.

    Managed compute deployments are a separate resource type with their own CLI commands. They are not the model deployments you see in the portal, and not Azure ML online endpoints either. So the usual delete commands will not touch them, which is why nothing appears to happen.

    List them:

    az cognitiveservices account managed-compute-deployment list -g <resource-group> -n ide05 -o table

    Then delete each one:

    az cognitiveservices account managed-compute-deployment delete -g <resource-group> -n ide05 --deployment-name <deployment-name>

    Here, -n is the Cognitive Services account name, not a workspace name. Once the list is empty, the account should delete normally

    If the CLI doesn’t recognize the command, run az upgrade because this command group is still in preview.

    If the list command shows nothing but the delete error still appears, export the resource group’s ARM template and search for managedComputeDeployment. The deployment names will be in the template and you can delete them using the same command.

    Also check for resource group locks or read‑only permissions, since both can make deletes look like they did nothing.

    https://learn.microsoft.com/en-us/cli/azure/cognitiveservices/account/managed-compute-deployment

    Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.