Problem deleting AI search resource

Question

Deleting an AI search resource "gptkb-xp2warnlhe5i6", return the following error:

gptkb-xp2warnlhe5i6: Unable to delete Search Service: 'gptkb-xp2warnlhe5i6'. LockedSPLResourceFound: Unable to verify management locks on Resource '/subscriptions/99db82a6-c096-4d51-b7cf-47aca779f31b/resourceGroups/rg-rag-0613/providers/Microsoft.Storage/storageAccounts/stxp2warnlhe5i6'. If you still want to delete the search service, manually delete the SPL resource first and try again. RequestId: c3d71d65-346e-4e16-86e4-7370760f6309 (Code: ConflictError)

However, the corresponding storage has already been deleted, and I could not find any remaining locks in the resource group.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

The error you’re encountering indicates that the AI Search Service (gptkb-xp2warnlhe5i6) cannot be deleted because it’s attempting to validate or check management locks on an associated Storage Account (stxp2warnlhe5i6) that has already been deleted. This is a known conflict that can occur when a dependent resource (in this case, the Storage Account) is deleted, yet the AI Search Service retains references to it.

Here’s a step-by-step approach to resolve this issue:

1. Verify in Resource Explorer:

• Go to Azure Resource Explorer to confirm that no remnants of the deleted Storage Account exist in the resource hierarchy.
  • In Resource Explorer, navigate to the search service (Microsoft.Search/searchServices) within your subscription and ensure there are no lock references related to the deleted Storage Account.

1. Force Deletion using Azure CLI:

• Sometimes, manually running a delete command via CLI can bypass certain validation errors.
  • Run the following command in the Azure CLI:

        az search service delete --name gptkb-xp2warnlhe5i6 --resource-group rg-rag-0613 --yes
        
        
    

  • If the service has a Soft Delete enabled, you may need to purge it by running az search service purge --name gptkb-xp2warnlhe5i6 --resource-group rg-rag-0613
• Check for Managed Identity Resources:
  • In some cases, the resource may still hold a Managed Identity or Key Vault reference that needs to be unlinked. Check under Azure Active Directory > Enterprise Applications and remove any related identities or permissions associated with gptkb-xp2warnlhe5i6.
  • This approach should help bypass the lock validation check that’s causing the conflict. Let me know if you encounter any additional errors during these steps.

Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.