InsufficientCapacity error when creating Azure Cache for Redis (Basic B0–B3) in Sweden Central

Leonel Franchelli 0 Reputation points
2026-08-13T18:20:31.23+00:00

We are unable to create Azure Cache for Redis instances in the Basic tier (B0–B3) in the Sweden Central region. Every deployment fails with:

ERROR CODE: InsufficientCapacity

Details:

  • Earlier today we successfully created one B0 instance, but all subsequent attempts over several hours have failed with the same error.
  • The error occurs regardless of SKU size, we tested both B0 and B3.
  • High availability is disabled on all attempts.

Is there a known capacity constraint for Basic tier Redis in Sweden Central? Is there an ETA for capacity restoration, or a recommended workaround (e.g., alternate zone/region) for this scenario?

Thank you.

Azure Cache for Redis
Azure Cache for Redis

An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.

1 answer

Sort by: Newest
Most helpful Newest Oldest
  1. Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator
    2026-08-23T06:39:19.3+00:00

    Hi @Leonel Franchelli
    Thank you for the update and for sharing the additional details.

    Based on the behavior you described, the InsufficientCapacity errors appear to have been related to temporary regional capacity availability for Azure Cache for Redis in Sweden Central. You were able to provision one B0 instance initially, while subsequent B0 and B3 deployments failed, and the three required B0 instances were eventually provisioned successfully after several days of retries.

    Since the deployments ultimately succeeded without a reported configuration change, this indicates that capacity availability changed over time rather than the issue being caused by the selected Basic tier configuration.

    Recommended approach for similar cases:

    • Retry the deployment after some time, as capacity is dynamic.
    • If the workload allows, consider an alternate supported region.
    • Retain the required SKU/size where possible rather than changing configuration solely to work around a transient capacity condition.

    In this case, the customer has confirmed that the three B0 instances were eventually provisioned successfully, so the issue is now resolved.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.