New Azure Managed Redis deployments in East US 2 are failing immediately with only a generic provisioning error: "The resource operation completed with terminal provisioning state 'Failed'" and an inner "OperationFailed" message. Existing caches in the region are working, but new instances cannot be created, so we have temporarily fallen back to the older Azure Cache for Redis service. Has anyone else seen this behavior, and is it related to regional capacity? Microsoft support has not provided a useful response after several days. The latest failed attempt occurred on 2026-08-03 at 14:31:21 UTC, with correlation ID 3bfef3f2-defa-4989-a485-78f552b0ea64.
3 Answers
This looks more like a regional capacity problem than an error in the deployment template. Several teams have reported the same generic failure in different regions, sometimes after many repeated attempts. Deploying in another region, such as Poland Central, has worked consistently for some environments.
There have also been service alerts covering multiple regions, including East US 2, West Europe, North Europe, and several US regions. The practical options appear to be retrying later, choosing a region with available capacity, or continuing with the older Redis service temporarily. Keep the correlation ID and exact timestamp for support because the portal error itself does not reveal much.
We have seen similar failures in West Europe and North Europe. Microsoft indicated that a capacity limitation affects certain infrastructure configurations, especially highly available caches. They suggested trying a B10 SKU or higher, although that workaround did not work for us. If a larger SKU does deploy, it may be possible to scale down afterward.
The larger-SKU workaround has been inconsistent. Our automated tests eventually succeed only occasionally after repeated attempts, so it is not reliable enough for regular deployments.