Unable to delete Resource Group, Microsoft is billing for no reason on VS Pro subscription

Parimal Raj 0 Reputation points
2026-07-20T20:37:54.64+00:00

Hello team,

I am unable to delete rg-parimal.raj-3427 associated with my subscription 0ff55103-e789-4359-a416-e513336d3ce7 (VS Pro 50$ credit)

I tested out some compute based model and deleted them on same day. And still getting billed for unknown reasons.

Error:

Failed to delete resource group rg-parimal.raj-3427: Deletion of resource group 'rg-parimal.raj-3427' failed as resources with identifiers 'Microsoft.CognitiveServices/accounts/parimal-in' could not be deleted. The provisioning state of the resource group will be rolled back. The tracking Id is '06bcd442-032b-4044-ba80-ca87bcd32c0c'. Please check audit logs for more details. (Code: ResourceGroupDeletionBlocked) Could not delete account since it contains 1 deployment(s). Please delete deployments first and try again. (Code: CannotDeleteAccountWithDeployments, Target: /subscriptions/0ff55103-e789-4359-a416-e513336d3ce7/resourceGroups/rg-parimal.raj-3427/providers/Microsoft.CognitiveServices/accounts/parimal-in)

Regards

Parimal Raj

Cost Management
Cost Management

A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Christos Panagiotidis 3,566 Reputation points
    2026-07-21T12:07:02.8833333+00:00

    The error identifies the blocker: Cognitive Services account parimal-in still contains one model deployment. Azure will not delete the parent account while the child deployment exists.

    In Azure portal, open parimal-in, select Models and endpoints or Deployments, and delete the remaining deployment. Alternatively, run az cognitiveservices account deployment list, then az cognitiveservices account deployment delete with the resource group, account, and returned deployment name. Confirm the list is empty, delete the Cognitive Services account, and retry the resource-group deletion. If it still fails, check for delete locks on the resource and resource group.

    For the continuing cost, open Cost Management > Cost analysis at subscription scope, filter to this resource group, and group by Resource or Meter. Cost data can arrive after deletion, so older usage may appear later. If charges continue accruing after the resources are confirmed gone, submit a billing support request with the cost item and deletion time.

    Was this answer helpful?

    0 comments
  2. Venkatanaidu Madamanchi 85 Reputation points Microsoft External Staff Moderator
    2026-07-23T20:42:11.47+00:00

    Hello @Parimal Raj

    Thanks for reaching out to the Microsoft Q&A Team.

    The error indicates that the Azure AI / Cognitive Services account parimal-in still has at least one active deployment associated with it:

    CannotDeleteAccountWithDeployments

    Please follow the below steps:

    Sign in to the Azure Portal.

    Open Resource Group rg-parimal.raj-3427.

    Open the Azure AI / Cognitive Services account parimal-in.

    Navigate to Deployments.

    Delete all model deployments listed.

    Wait for the deployment deletion to complete.

    Delete the parimal-in resource.

    Retry deleting the resource group rg-parimal.raj-3427.

    If no deployments are visible in the Azure Portal, please also check:

    Azure AI Foundry / Azure OpenAI Studio

    Deployments tab under the parimal-in account

    Regarding the charges, deployed endpoints/models can continue to incur costs until they are fully removed. You can review the source of the charges under:

    Cost Management + Billing → Cost Analysis

    and filter by resource group rg-parimal.raj-3427 to identify the remaining billable resource.

    The resource group cannot be deleted until all deployments are removed from the Cognitive Services account.

    Thanks,

    Venkat.M

    Was this answer helpful?

    0 comments

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.