Azure AI Search: Resource in inconsistent state blocking resource group deletion — Need guidance

Question

Azure AI Search: Resource in inconsistent state blocking resource group deletion — Need guidance

Ivan RAMUS 0

Problem description

I am facing an issue with my Azure AI Search service in the Sweden Central region. After a failed creation attempt, the service entered a stuck, inconsistent state where it cannot be read, updated, or deleted. It does not appear in the resource group listing and still blocks the deletion of the resource group.

Environment

Service: Azure AI Search; Region: Sweden Central; SKU: serverless and later redeployment attempt: basic.

What I've already tried

I have attempted multiple retries of creation, updates, and deletions. Specifically, I retried deployment with different SKUs, sent delete requests, and attempted to delete the resource group multiple times. I also confirmed that there are no resource locks affecting the resource or resource group. Additionally, I verified that the resource is not listed in the resource group view, yet Azure still treats it as present and blocks deletion.

Current status

The resource remains in an inconsistent, stuck state, preventing deletion of the resource group. I am seeking guidance on how to resolve this orphaned resource and clear the blocking state to delete the resource group.

0 comments

2 answers

Your answer

Answer 1

Hi @Ivan RAMUS

Thank you for your patience while we investigated this issue.

Based on our investigation, we have confirmed that this behavior is related to a known Azure AI Search service-side issue. The relevant engineering team is aware of the issue and is working on addressing it.

As a temporary workaround, we recommend creating a new Azure AI Search service using a different service name. This should allow you to proceed with your workload while the underlying issue is being addressed.

If you are able to proceed successfully using the workaround, please let us know. If this resolves the immediate impact and no further assistance is required, please also confirm so we can consider this issue addressed.

Thank you for your patience and understanding.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

Hi Ivan,

This is a known issue in Azure Resource Manager (ARM) where a failed provisioning state leaves behind a "ghost" or orphaned resource. Because the resource provisioning never fully completed, the Azure Portal UI hides it, but the ARM backend still registers its existence—which is why it is blocking your Resource Group deletion.

Since the portal UI, standard deletion attempts, and checking for resource locks have not worked, you will need to bypass the standard UI to clear it. Here are the steps to resolve this:

1. Force Delete via Azure CLI / Cloud Shell

Sometimes the CLI can force the deletion of the entire resource group even when the portal gets confused by the stuck state. Open Azure Cloud Shell and run:

az group delete --name <YourResourceGroupName> --yes --no-wait

2. Use Azure Resource Explorer

The Azure Resource Explorer allows you to see the raw ARM backend state and issue direct API calls.

Go to resources.azure.com and log in.

In the left tree, navigate to: subscriptions > [Your Subscription] > resourceGroups > [Your Resource Group] > providers > Microsoft.Search > searchServices.

If you see your stuck AI Search service here, click the Edit button at the top of the screen, and then click Delete.

3. Open a Support Ticket (Backend Purge)

If the resource explorer fails with a backend error, the resource is completely locked at the underlying infrastructure level. At this point, only Microsoft Support can purge it.

Open a support ticket via the Azure Portal. You do not need a paid technical support plan for this—you can route it under Subscription Management (which is always free) and clearly state that an "orphaned ARM resource is blocking resource group deletion." The support team will run a backend script to forcefully clear the stuck state so you can finally delete the resource group.