Share via

Error trying to create SQL Managed Instance in West US, but works in other regions using same subscription/

Marrell Sanders 20 Reputation points
2025-05-28T19:25:58.4933333+00:00

When trying to create a SQL Managed Instance in a region I get error "Managed Instance is not available for the chosen subscription and region. Please try again with some other subscription, region", but selecting a different region the error goes away. This is using a pay as you go subscription, and again using the same subscription it's fine if I select a different region. I'm just trying not to split up the regions my resources are using if I don't need to.

Azure SQL Database
Accepted answer
  1. Sina Salam 22,031 Reputation points Volunteer Moderator
    2025-05-29T00:02:01.06+00:00

    Hello Marrell Sanders,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you are having issue where deploying a SQL Managed Instance (MI) in the West US region fails with the error: “Managed Instance is not available for the chosen subscription and region,” even though the same Pay-As-You-Go subscription works fine in other regions.

    This issue is not just about a misconfiguration or subscription type, but rather a combination of regional capacity limitations and subscription-specific availability. Azure regions like West US often experience high demand, and Microsoft may temporarily restrict new deployments of certain services like SQL MI due to capacity constraints. This is especially common in popular or older regions where infrastructure expansion is slower.

    Therefore, while your subscription is valid and supported, the error indicates that West US currently lacks available capacity for SQL Managed Instances under your subscription tier. This is not a permanent restriction, but a dynamic limitation based on current usage and provisioning quotas. You can confirm this by checking your subscription quotas in the Azure portal or using the Azure Quota Troubleshooter to identify and resolve any quota-related issues.

    If maintaining regional consistency is critical for your architecture, the most reliable workaround is to:

    • Deploy in a nearby region like West US 2 or Central US, which may have more capacity.
    • Use Virtual Network Peering to connect resources across regions seamlessly.
    • Or, if SQL MI is not strictly required, consider using Azure SQL Database (single or elastic pool) as a temporary alternative.
    • If you still prefer West US, I recommend submitting a support request to Microsoft to inquire about capacity availability or request a quota increase: Create Azure Support Request.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

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