Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: 
Azure SQL Managed Instance
This article is a centralized list of the availability of various Azure SQL Managed Instance features in Azure regions.
- To view regional availability of Azure SQL Managed Instance, see Azure global infrastructure products by region.
- To move Azure SQL Managed Instance to another region, see Move resources to new region.
vCore purchasing model hardware availability
Azure SQL Managed Instance hardware is available in all regions, except where indicated. For more information, see vCore purchasing model.
Standard-series (Gen5) availability
Standard-series (Gen5) hardware is available in all public regions worldwide where Azure SQL Managed Instance is available.
Regional supports for memory optimized premium-series hardware and for premium-series hardware with 16-TB storage
Supports for the memory-optimized premium-series hardware and the premium-series hardware with 16-TB storage are currently available in the region only:
- China North 3
Maintenance window availability
Choosing a maintenance window for Azure SQL Managed Instance other than the default is available in all regions.
Zone redundancy
Zone redundancy is supported in the following region:
- China North 3
Note
Limited hardware capacity might temporarily disable zone redundant deployments to create a new instance or modify an existing instance in a supported region.
Blocked zone redundant deployments
If your region supports zone redundancy but you can't create or modify a zone redundant instance, Azure regional capacity constraints likely block the deployment. These constraints affect specific configurations in that region. This limitation isn't caused by your subscription, configuration, or deployment process.
While capacity is constrained, consider the following options:
- Deploy to an alternative Azure region that supports zone redundancy and satisfies your data residency requirements.
- Use an alternative hardware generation or service configuration, if applicable.
- Retry the operation later, when capacity might become available.
If none of these options meet your business needs, contact your account team or Azure support to escalate the request. Provide your business requirements and the expected business impact of the deployment limitation so the request can be prioritized.