Azure Managed Redis resource stuck in Deleting state for more than 24 hours

A resource remaining in the Deleting state for more than 24 hours is not expected behaviour for azure Managed Redis. In most cases, this indicates that the ARM delete operation has not yet completed successfully, even though the delete request was accepted.

Before taking any further action, I would recommend checking the following:

1. Review the Activity Log for the Redis resource and resource group to determine whether the delete operation is still running, has failed, or is waiting on another operation. Azure Activity Log records control plane operations such as create, update, and delete requests.
2. Check Resource Health and the Diagnose and solve problems blade for the resource. These built-in Azure Managed Redis troubleshooting tools can sometimes surface service-side issues or operation failures that are not obvious from the Overview page.
3. Verify that no resource locks exist at either the resource or resource group level. Although locks typically prevent deletion from starting, validating that no lock-related configuration remains is a useful sanity check.

Avoid submitting additional delete requests or attempting to recreate the resource with the same name while the existing delete operation is still shown as in progress, as this generally does not accelerate cleanup.

Regarding your specific questions:

• Why can this happen? A long-running delete operation usually indicates that the underlying ARM operation has not completed successfully. The exact cause cannot be determined from the information provided alone.

Is there a supported way to force-complete the deletion? There is no documented customer-side operation to force-remove an Azure Managed Redis resource that is already stuck in the Deleting state.

Can you create a new Redis instance? Yes. Creating a new Azure Managed Redis instance with a different name is typically independent of the deletion state of the old resource, provided you are not constrained by subscription quotas or environmental dependencies.

If you can share the status of the delete operation from Activity Log (Succeeded, Failed, or In Progress) along with any operation details or error codes, the community may be able to provide more targeted guidance.

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.

The Redis instance is most likely stuck in the Deleting state due to a backend Azure service issue. There is no supported customer side method to force the deletion. No further action is required from your side other than verifying there are no dependencies and engaging Microsoft Support (or your Azure account team) if the status does not clear. You may proceed with creating a new Redis instance using a different name while Microsoft completes the cleanup of the old resource.

Recommended actions:

Verify that no dependent resources are linked to the Redis instance.

Monitor the resource status for a few additional hours.

Engage Microsoft Support through your account representative or upgrade the support plan if backend assistance is required.