UpdatingManagedIdentityFailed - Basic 1 GB

Question

Hi Team,

We need to perform load testing on the Redis cache and ensure it can auto-scale as the load increases.

We attempted autoscaling using an Automation Runbook, after which the Redis cache status changed to UpdatingManagedIdentityFailed - Basic 1 GB. Manual autoscaling attempts are also resulting in the same error.

We require urgent assistance, as we are approaching our production go-live and need to validate autoscaling behavior.

Any guidance or relevant contacts would be greatly appreciated. Thanks in advance.

Answer 1

Hi @Aarti Tare (NON EA SC ALT)

Thank you for your patience.

The issue has been reviewed and resolved with the Product Group’s assistance. The Redis cache was in a transient backend state where an earlier update operation (triggered during the autoscaling attempt via Automation Runbook) had not completed successfully, which caused the resource to enter the “UpdatingManagedIdentityFailed” state. While in this state, any further scale operations (manual or automated) are blocked, resulting in the error indicating that the resource is busy processing a previous request.

The backend team has now cleared the stuck operation and brought the cache instance back to a healthy state. Post-remediation, scaling operations are working as expected.

Next steps:

You should now be able to proceed with scaling activities and continue your load testing.

We recommend validating autoscaling logic carefully (especially when using Automation Runbooks) to avoid overlapping update operations on the Redis resource.

Please let us know if you face any further issues during your validation or need guidance on autoscaling best practices.

Thanks again for your cooperation.