Deleted Microsoft Foundry resource remains in Azure AI Content Understanding Studio; delete button disabled

Hello @BilalAlTarazy-2894

Based on what you've already tested, this looks more like an orphaned association in Content Understanding Studio than an Azure Resource Manager deletion issue.

The key clue is the error:

Microsoft.CognitiveServices/accounts/tarazytech-6016-resource ... was not found

Combined with the fact that the resource is absent from both the active resource list and Manage deleted resources, Azure Resource Manager no longer appears to have a resource available for you to delete or purge. Your Incognito test also makes a browser-cache issue unlikely.

Microsoft documents that deleted Foundry resources normally enter a recoverable state for up to 48 hours and can be viewed, recovered, or permanently purged through Manage deleted resources. If the resource doesn't appear there, the normal Foundry recovery/purge workflow doesn't provide anything further for you to remove.

I therefore wouldn't recreate the resource with the same name simply to try to remove this entry. I also wouldn't attempt to delete the resource group if the actual Azure resource has already been removed.

For completeness, you can verify from Azure CLI that ARM no longer sees the resource:

az resource show \
  --resource-group rg-tarazytech-6016 \
  --name tarazytech-6016-resource \
  --resource-type Microsoft.CognitiveServices/accounts

If that returns ResourceNotFound, it further confirms that the remaining object you're seeing is not the actual Azure resource.

Microsoft's current Foundry documentation also distinguishes deletion of projects from deletion of the parent Foundry resource. Projects can be explicitly deleted through Foundry or az cognitiveservices account project delete, while deleting the Foundry resource itself removes the Microsoft.CognitiveServices/accounts resource.

Since you've already removed the deployments, project, and parent resource, and Content Understanding Studio still displays a nonfunctional reference to an ARM resource that no longer exists, I think this now warrants Microsoft-side investigation/cleanup rather than further client-side troubleshooting.

When escalating, I would provide:

• Subscription ID
• Tenant ID
• Resource group: rg-tarazytech-6016
• Deleted resource name: tarazytech-6016-resource
• Region: East US 2
• Screenshot of the orphaned entry
• The exact Resource ... was not found message
• Approximate UTC time when the resource was deleted

Ask specifically for the Azure Content Understanding/Foundry team to investigate and remove the stale resource association from Content Understanding Studio.

Other Foundry cases have also required backend cleanup when a resource was partially deleted or left in an inconsistent state, rather than another portal/CLI deletion attempt.

Based on the evidence you've provided, I don't see another supported self-service deletion step you may have missed. The ARM resource appears to be gone; the Content Understanding Studio reference just hasn't been cleaned up correctly.

Sharing these references with you:

Microsoft - Recover or purge deleted Microsoft Foundry resources

Microsoft - Create and delete Foundry projects

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.

Hi ,

Thanks for reaching out to Microsoft Q&A.

Based on the information provided, the underlying Azure resource appears to have been successfully deleted, while Azure AI Content Understanding Studio still retains a reference to it.

The indicators supporting this conclusion are:

• The resource returns ResourceNotFound when Studio attempts to access it.
• The entry shows"Failed to retrieve location" and"No models available".
• Both Configure and Delete actions are disabled.
• The resource is not present in either the active resources list or Manage deleted resources.
• The behavior is reproducible in an InPrivate session, making a browser cache issue unlikely.

I am not aware of any documented customer-facing method to manually remove an orphaned Content.

Based on the symptoms, i believe this appears to be either a sync issue or a stale resource reference within the Studio experience

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

@Allan Solomon Mejia and @Vinodh247-1375 thank you both for your replies and for taking the time to help.

Unfortunately, the suggested solutions did not resolve my issue. What I specifically need is a way to remove the stale records from Content Understanding Studio, and the approaches provided so far have not addressed that.

In any case, I really appreciate your help. At this point, I believe Microsoft may need to provide further guidance or a definitive answer on how these stale records can be removed.