Resource group related to Foundry model is not deleting

MD. HASIB MUYEN 20 Reputation points
2026-10-22T22:50:40.31+00:00

Hi,

I created a model in Foundry just for playing around. After I was done, I wanted to delete the resource group but it did not delete. And now I am charged a hefty amount for this.

I used the troubleshooting steps in support and it says

"The most likely cause of the charges is an active managed compute deployment on the Cognitive Services Speech account. Deletion of the account failed because it still contains 1 managed compute deployment, and this kind of managed compute is billed hourly per accelerator, so it can continue generating charges even when text-to-speech character usage is low or absent. Over the examined period, no synthesized-character usage was observed, so standard TTS character consumption does not appear to be the source of the billing issue."

My question is how can I delete this resource group and model and how can I request to not pay for this resource that I have not used.

Cost Management
Cost Management

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

0 comments
Answer accepted by question author

AI answer

2026-10-22T22:52:00.29+00:00

Delete the active managed-compute deployment from the Cognitive Services account first, verify that no deployments remain, and then delete the resource group.

1. Remove the managed-compute deployment

Open Azure Portal → Cloud Shell → Bash, select the affected subscription, and run the following commands. Replace all bracketed values with the resource group, Cognitive Services account, and deployment names shown in the support diagnosis.

az account set --subscription "<subscription-name-or-id>"

az cognitiveservices account managed-compute-deployment list \
  --resource-group "<resource-group>" --name "<cognitive-account>" --output table

az cognitiveservices account managed-compute-deployment delete \
  --resource-group "<resource-group>" --name "<cognitive-account>" \
  --deployment-name "<deployment-name>"

az cognitiveservices account managed-compute-deployment list \
  --resource-group "<resource-group>" --name "<cognitive-account>" --output table

The final command should return no managed-compute deployments. This command group is currently in preview, and --name refers to the Cognitive Services account name, not the model name.^1^

If the command returns an authorization error, the account scope requires Cognitive Services Contributor, Foundry Owner, or Foundry Account Owner. Foundry User and Cognitive Services User are read-only for managed-compute deployments.^2^

2. Delete the resource group

After the deployment is gone:

az group delete \
  --name "<resource-group>" \
  --yes

Resource-group deletion is irreversible.^3^

If deletion still fails:

  1. Open Azure Portal → Resource groups → your resource group → Activity log.
  2. Open the failed delete event and record its exact error code and affected resource.
  3. Check Resource group → Locks and remove any Delete or Read-only lock if authorized.
  4. Check whether the reported resource depends on something outside this resource group.

Locks and cross-resource-group dependencies can prevent deletion even when the caller has the resource-group delete permission.^3^

3. Request a billing review

Deleting the resources stops future managed-compute allocation; it does not automatically reverse charges already accrued.

In the Azure portal, go to:

Help + support → Create a support request → Billing → Unexpected charges

Subscription-management support, including billing, is available without purchasing a technical support plan.^4^

Include:

  • Subscription and invoice numbers.
  • Resource group and Cognitive Services account names.
  • Managed-compute deployment name and resource ID.
  • Date the deployment was created and date deletion first failed.
  • The failed deletion’s Activity Log entries.
  • Cost Analysis details grouped by Resource and Meter.
  • The support diagnostic statement showing no synthesized-character usage.
  • The deployment deletion time and confirmation that the resource group was removed.
  • A direct request for a billing adjustment or one-time courtesy refund because the resource was created for evaluation, remained billable while deletion was blocked, and was not intentionally used.

Microsoft can investigate and decide whether an adjustment is appropriate, but a refund is not guaranteed.^5^ Cost Management also recommends reviewing the invoice, Cost Analysis, audit logs, and then opening an Azure support request for unrecognized charges.^6^

If the managed-compute delete command itself fails despite the required role, attach its complete output and the Activity Log event to the same support request and ask for the deployment’s backend deletion to be escalated.

References

  1. az cognitiveservices account managed-compute-deployment delete
  2. Managed compute in Microsoft Foundry (preview)
  3. Azure Resource Manager resource group and resource deletion
  4. Create an Azure support request
  5. i got charged 3 times for a managed compute environment - Microsoft Q&A
  6. Ingest cost details data
AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.