blocked while provisioning Azure Managed Redis

Question

blocked while provisioning Azure Managed Redis

Suraj Pudale 80 Microsoft Employee

Error:

Code: InsufficientCapacity

Message: Request failed due to insufficient capacity. Retry using a different Azure Managed Redis size or region. (East us 2)

Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T13:58:35.61+00:00

Hi Suraj Pudale,

The InsufficientCapacity error indicates that Azure currently doesn't have enough capacity in East US 2 for the requested Azure Managed Redis configuration.

You can try the following:

1)Retry the deployment after some time.

2)If the issue persists, you can also try a different Redis SKU/size or another supported Azure region.

This is generally a temporary Azure capacity availability issue, rather than a configuration problem with your deployment.
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:01:30.42+00:00

@Himaja Y I’ve retried several times, but I still haven’t had any luck, and I need to use East US 2.
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T14:13:42.0733333+00:00

Hi Suraj Pudale,

Since you have already retried several times and East US 2 is required, we recommend checking if the issue is specific to the selected Redis SKU/size. If possible, please try a different supported SKU/size within East US 2. If the issue still persists, please share the Redis SKU/size and deployment details so we can investigate further.
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:17:00.89+00:00

@Himaja Y Details:

PII has been redacted
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T14:23:59.71+00:00

Hi Suraj Pudale,

Since you have already retried the deployment and East US 2 is required, the error appears to be related to capacity availability for the Balanced_B3 SKU in East US 2.

So, could you please try deploying with a different supported SKU in East US 2?
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:59:26.8133333+00:00

@Himaja Y Balanced_B5 works.. but my code required Balanced_B3
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T15:23:19.42+00:00

When I try to delete Balanced_B5, which we created manually, and then recreate it through the ev2 deployment, I still get the same issue.
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T17:03:57.75+00:00

Hi Suraj Pudale,

Thank you for providing the additional details.

We reviewed the issue and found that there is currently an active Azure service incident affecting Redis Enterprise capacity in the East US 2 region. The incident includes Balanced SKUs among the impacted configurations.

Your scenario is also consistent with the capacity issue, as you are receiving InsufficientCapacity specifically for Balanced_B3, while Balanced_B5 was successfully provisioned in the same region.

Since East US 2 and Balanced_B3 are required for your deployment, using a different SKU or region would not be a suitable solution at this time. The issue appears to be related to the availability of capacity for the requested SKU in East US 2.

We will correlate this issue with the ongoing service incident and continue to monitor the capacity situation. Once the required capacity becomes available, the Balanced_B3 deployment should be retried.

We understand that your EV2 deployment specifically requires Balanced_B3, and we will keep this requirement in consideration while tracking the issue.

Thank you for your patience and understanding.

1 answer

Your answer

Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T13:58:35.61+00:00

Hi Suraj Pudale,

The InsufficientCapacity error indicates that Azure currently doesn't have enough capacity in East US 2 for the requested Azure Managed Redis configuration.

You can try the following:

1)Retry the deployment after some time.

2)If the issue persists, you can also try a different Redis SKU/size or another supported Azure region.

This is generally a temporary Azure capacity availability issue, rather than a configuration problem with your deployment.
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:01:30.42+00:00

@Himaja Y I’ve retried several times, but I still haven’t had any luck, and I need to use East US 2.
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T14:13:42.0733333+00:00

Hi Suraj Pudale,

Since you have already retried several times and East US 2 is required, we recommend checking if the issue is specific to the selected Redis SKU/size. If possible, please try a different supported SKU/size within East US 2. If the issue still persists, please share the Redis SKU/size and deployment details so we can investigate further.
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:17:00.89+00:00

@Himaja Y Details:

PII has been redacted
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T14:23:59.71+00:00

Hi Suraj Pudale,

Since you have already retried the deployment and East US 2 is required, the error appears to be related to capacity availability for the Balanced_B3 SKU in East US 2.

So, could you please try deploying with a different supported SKU in East US 2?
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T14:59:26.8133333+00:00

@Himaja Y Balanced_B5 works.. but my code required Balanced_B3
Suraj Pudale 80 Reputation points Microsoft Employee

2026-08-12T15:23:19.42+00:00

When I try to delete Balanced_B5, which we created manually, and then recreate it through the ev2 deployment, I still get the same issue.
Himaja Y 555 Reputation points Microsoft External Staff Moderator

2026-08-12T17:03:57.75+00:00

Hi Suraj Pudale,

Thank you for providing the additional details.

We reviewed the issue and found that there is currently an active Azure service incident affecting Redis Enterprise capacity in the East US 2 region. The incident includes Balanced SKUs among the impacted configurations.

Your scenario is also consistent with the capacity issue, as you are receiving InsufficientCapacity specifically for Balanced_B3, while Balanced_B5 was successfully provisioned in the same region.

Since East US 2 and Balanced_B3 are required for your deployment, using a different SKU or region would not be a suitable solution at this time. The issue appears to be related to the availability of capacity for the requested SKU in East US 2.

We will correlate this issue with the ongoing service incident and continue to monitor the capacity situation. Once the required capacity becomes available, the Balanced_B3 deployment should be retried.

We understand that your EV2 deployment specifically requires Balanced_B3, and we will keep this requirement in consideration while tracking the issue.

Thank you for your patience and understanding.

Answer 1

Hello @Suraj Pudale ,

I hope you are doing well.

Thank you for your patience related to Azure Managed Redis resource deployment failure in East US 2.

We understand that this issue has been ongoing and appreciate your patience while attempting the deployment multiple times. We sincerely apologize for the inconvenience this has caused to your deployment plans.

As there are no further technical actions currently available from the support side, we are proceeding with archiving the case. Please find below a summary of the investigation and guidance provided for your records.

Issue:

You reported that you were unable to create an Azure Managed Redis instance with the required B3 SKU in the East US 2 region. The deployment continued to fail with the error:

“Request failed due to insufficient capacity.”

Actions taken:

We reviewed the deployment failure and identified that the issue was related to regional Azure service capacity availability, rather than an issue with your configuration or deployment template.

We explained that capacity can change over time as Azure resources are allocated and rebalanced.

We recommended retrying the deployment periodically.

We also suggested considering an alternative SKU/SKU family or deploying the resource in another Azure region, if suitable for your workload.

We recommended monitoring Azure Service Health for updates regarding capacity availability and any related service notifications.

We also clarified that there is currently no specific ETA available for when the required capacity may become available in the affected region.

Outcome:

The latest update available on the case indicates that the deployment was still failing with the insufficient capacity error. Since regional capacity availability is the limiting factor and there are no additional troubleshooting actions that can be performed from the technical support side at this time, we are archiving the case with the above mitigations available for you to retry.

Archiving is a process where we close the case while retaining the option to reopen it if further assistance is required. If capacity becomes available or you have new deployment results or error details, you can reference this case number and we can continue assisting you as appropriate.

We understand that this situation may have impacted your deployment plans, and we truly appreciate your time, patience, and cooperation throughout the case.

Thank you again for your time and cooperation.