Cannot create Azure Managed Redis (Microsoft.Cache/redisEnterprise)

Hi Serafim Pinto,

Thanks for sharing the detailed troubleshooting steps, that really helps narrow this down.

Since the same configuration works in your dev subscription but consistently fails here with resourceState = CreateFailed and only a generic OperationFailed error, this is very likely not a configuration issue, but instead related to subscription-level enablement or backend capacity constraints.

A few focused checks that should help confirm this:

First, please verify whether the SKUs you’re trying are actually available for this subscription in the target region:

az redisenterprise list-skus --location eastus

If Balanced_B0, B1, or B3 are not listed, it means those SKUs are not enabled for this subscription.

Next, check if there are any quota or usage limits impacting provisioning:

az redisenterprise show-usage --location eastus

Even if limits don’t appear fully consumed, backend capacity constraints can still cause silent failures like the one you’re seeing.

I’d also recommend reviewing the Activity Log (Azure Portal → Monitor → Activity Log) for the failed deployment. Sometimes additional details such as internal error codes or correlation IDs are available there, even when the UI only shows OperationFailed.

As a quick isolation step, you could also try:

• Deploying a different SKU (for example, Enterprise_E10)
• Trying a different region (such as West US)

If those succeed, it helps confirm whether the issue is specific to SKU availability or regional capacity.

Hi Serafim Pinto,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Hello Pilladi,

Thank you for the suggestions, but unfortunately the commands you shared don't exist, they return errors when run.

I ended up upgrading to a paid Azure support plan, which is how I finally discovered the root cause: there is an active service issue affecting Azure Managed Redis and Azure Cache for Redis Enterprise in East US due to capacity constraints.

The impact statement confirms that customers may experience failures when creating or scaling Redis resources in the region.

It's frustrating that this information was only visible after upgrading my support plan. A known regional capacity outage should surface in the deployment error details, not require a paid support tier to diagnose.

For anyone else hitting the same issue: the recommended workaround from Azure is to deploy in a nearby alternative region.

Hi Serafim Pinto,
Thanks for sharing the detailed update , that really helps clarify what was happening here.

It makes sense now why the deployments were consistently failing across SKUs and configurations. Since this is due to a regional capacity constraint in East US, it explains why everything looked correct from a configuration standpoint but still resulted in CreateFailed.

I understand your concern around the visibility of this issue , ideally, such service-side limitations should be reflected more clearly during deployment rather than requiring escalation to identify the root cause. I’ll make sure this feedback is shared internally.

For now, as suggested, using an alternate nearby region would be the best path forward.

Please let me know if you need any help validating the deployment in another region or if you run into any issues there.