Canary deployment is blocked by Redis Enterprise control-plane conflicts.

Question

Canary deployment is blocked by Redis Enterprise control-plane conflicts.

Suraj Pudale 80 Microsoft Employee

Errors:

"Cannot manage private endpoint connection while cache ... is in 'Succeeded' state. Please wait for the cache to reach a stable state before retrying."
"The cluster is not yet running."
Provider: Microsoft.Cache/redisEnterprise@2025-07-01
Region - Central US EUAP

Himaja Y 465 Reputation points Microsoft External Staff Moderator

2026-08-25T15:36:39.8766667+00:00
Hi @Suraj Pudale ,

Thank you for reaching out to the Microsoft Q&A forum.

Based on the error details, the deployment appears to be blocked by a temporary Redis Enterprise control-plane conflict. Although the Redis Enterprise resource shows a Succeeded provisioning state, the backend cluster has not yet reached a fully stable Running state.

The following messages support this conclusion:

"Wait for cache to reach stable state before retrying"

"Cluster not yet running"

Failure while managing the private endpoint connection

This typically occurs when the Redis Enterprise service is still completing background operations such as cluster initialization, private endpoint configuration, scaling, maintenance, or internal state reconciliation. During this period, additional control-plane operations may be rejected.

Recommended actions:

Verify that the Redis Enterprise cluster status is Running and healthy.

Review the Azure Activity Log for any ongoing or recently completed operations on the Redis Enterprise resource.

Confirm that the private endpoint connection is in an Approved and Succeeded state.

Once the resource reaches a stable state, retry the deployment.

If the issue continues after the cluster is healthy and no operations are in progress, please share the deployment correlation ID, resource ID, and relevant Activity Log entries for further investigation.

At this time, the issue appears to be a transient platform/control-plane state conflict rather than a problem with the deployment template itself.
Himaja Y 465 Reputation points Microsoft External Staff Moderator

2026-08-26T14:06:44.6866667+00:00

Hi @Suraj Pudale ,

We haven’t received a response. Please let us know if you need any additional information or assistance from my side.

1 answer

Your answer

Himaja Y 465 Reputation points Microsoft External Staff Moderator

2026-08-25T15:36:39.8766667+00:00

Hi @Suraj Pudale ,

Thank you for reaching out to the Microsoft Q&A forum.

Based on the error details, the deployment appears to be blocked by a temporary Redis Enterprise control-plane conflict. Although the Redis Enterprise resource shows a Succeeded provisioning state, the backend cluster has not yet reached a fully stable Running state.

The following messages support this conclusion:

"Wait for cache to reach stable state before retrying"

"Cluster not yet running"

Failure while managing the private endpoint connection

This typically occurs when the Redis Enterprise service is still completing background operations such as cluster initialization, private endpoint configuration, scaling, maintenance, or internal state reconciliation. During this period, additional control-plane operations may be rejected.

Recommended actions:

Verify that the Redis Enterprise cluster status is Running and healthy.

Review the Azure Activity Log for any ongoing or recently completed operations on the Redis Enterprise resource.

Confirm that the private endpoint connection is in an Approved and Succeeded state.

Once the resource reaches a stable state, retry the deployment.

If the issue continues after the cluster is healthy and no operations are in progress, please share the deployment correlation ID, resource ID, and relevant Activity Log entries for further investigation.

At this time, the issue appears to be a transient platform/control-plane state conflict rather than a problem with the deployment template itself.
Himaja Y 465 Reputation points Microsoft External Staff Moderator

2026-08-26T14:06:44.6866667+00:00

Hi @Suraj Pudale ,

We haven’t received a response. Please let us know if you need any additional information or assistance from my side.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

This looks like a Redis Enterprise control-plane state conflict, not an application or deployment configuration issue. The cache is reporting Succeeded, but the underlying Redis Enterprise cluster is not yet in a stable/running state, so Azure is blocking private endpoint operations during the Canary deployment. This is particularly plausible with the 2025-07-01 API version and Central US EUAP, where newer control-plane behaviour can surface transient state inconsistencies.

Wait for the Redis Enterprise cluster to reach a stable Running state, then retry the Canary deployment/private endpoint operation. If it remains stuck, check Azure Resource Health/Activity Log for concurrent Redis operations and avoid parallel updates to the cache, private endpoint, or networking resources. If the cluster remains non-running for an extended period, this is likely a platform/control-plane issue requiring an Azure Support ticket with the Redis cache resource ID, correlation ID, and timestamps.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.