An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
Hello Bork,
Since your Managed Redis instance is actively being used, do not delete or recreate the Redis instance.
The problem appears to be with the access removal operation itself. The user assignment is still in Deleting state, while the database remains in Updating state. This also explains why another attempt to delete the assignment is being blocked.
Please check the Activity Log for the Managed Redis resource and find the operation related to removing this user's access. If the operation failed, check the error details and note the correlation ID/request ID if one is provided.
Also check Resource Health and Diagnose and solve problems for the Redis resource.
I would avoid retrying the deletion repeatedly while the previous operation is still pending. If the user remains in Deleting and the database continues to stay in Updating with no operation progressing, the stuck operation will need further investigation through Azure Support.
When raising the support request, include the Activity Log details, approximate time the deletion was initiated, region, current provisioning state, and correlation/request ID if available.
You do not need to delete the Redis instance just to resolve the stuck user assignment.