This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 27%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Code: None
Message: There is not enough capacity in the specified region to create the
namespace. Please try an alternate region.
The error above is the one that I'm getting when I'm attempting a create namespace operation in the region. I'm assuming lack of PUs.
Bicep / ARM deployments to existing Premium Event Hubs namespaces in francecentral are also failing with Namespace Allocation Failed [(Scale unit is out of capacity)], even when the deployment is a no-op (no property changes).
Is this transient? Is francecentral having any issues? Is this more of a "consider a long term switch to a different region" thing?
An Azure real-time data ingestion service.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 2%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
I’m reaching out to you on Teams for further process. You can also try selecting a different regions like West Europe or France South often have available Premium capacity. Choose a region from the Location dropdown when creating a namespace or set the location in Bicep/ARM.
Answer accepted by question author
The issue you encountered was due to temporary capacity constraints (Premium Units) in the France Central region, which resulted in namespace creation and deployment failures.
At this moment, capacity has been restored in the region.
We recommend retrying the deployment, and it should now succeed. If the issue persists, please let us know so we can investigate further.