need a database instance in east-1 near my servers and region

Question

azure will not allow me to provision a database in my region. the nearest source was canadacentral

Answer 1

Hello **David Kroll
It sounds like you’re trying to spin up an Azure MySQL instance in a region that either isn’t recognized by Azure or isn’t enabled on your subscription—hence Canada Central ends up being the “nearest” available region. Here are a few things to check and try:

1. Verify the exact Azure region name:
   Azure doesn’t use AWS-style names like “east-1.” Instead use Azure region codes such as “East US” (eastus), “East US 2” (eastus2), “Central US” (centralus), etc. • Make sure your tool or template is using a valid Azure location parameter.
2. Check service availability for Azure Database for MySQL:
   If you’re using Flexible Server, confirm that the region you want is supported. – Visit the Flexible Server regions table here: https://learn.microsoft.com/azure/mysql/flexible-server/overview#azure-regions
   • If you’re creating a Single Server instance, refer to its region availability.
3. Watch out for subscription or quota restrictions:
   • Some subscriptions (especially newer or free tiers) may not have all regions enabled by default. • If the region you want is supported but still not listed in the portal/CLI, you may need to raise a “Region Access” quota request for Azure Database for MySQL Flexible Server.
   – You can file that under Help + support → New support request → Quota.
4. Sample CLI command for Flexible Server in East US 2

      az mysql flexible-server create --resource-group myResourceGroup --name myMysqlServer --location eastus2 --sku-name Standard_B1ms --admin-user myadmin --admin-password
      
   

5. Reference links,
   https://docs.microsoft.com/azure/reliability/availability-zones-overview
   https://docs.microsoft.com/azure/mysql/flexible-server/quickstart-create-server-cli

Answer 2

Hi David,

From your description I assume you are wanting to deploy Azure SQL Database in East US region. Please correct me if my assumption is wrong.

Please carefully follow my instructions below to create a new Service and subscription limits (quotas) request quota increase to allow access to deploy SQL Database in the region.

1. Navigate to this link to start the process:

https://portal.azure.com/#create/Microsoft.Support

2. Enter quota in the box and click Go

3. Select Others / Service and subscription limits (quotas) and click Next

4. Click Create a support request button, as shown

5. Select Issue type: Service and subscription limits (quotas), Subscription, Quota type: SQL database, click Next

6. Now you should be on Additional details tab. Click Enter details

7. Select Region access, select Location, enter expected number of vCores, and then click Save and continue

8. Finish filling out Additional details tab, click Next, review and click Create. You should receive an automated email within a few minutes.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Answer 3

In public cloud environments, resource availability is tied to the regions supported by the provider. Not every service is available in every region, and this is an inherent part of operating in a public cloud. Cloud providers segment their infrastructure to balance demand, maintain compliance, and optimize performance, which sometimes forces you to deploy resources in a nearby region rather than the one closest to your servers. This can introduce slightly higher latency or cross-region considerations, but it’s a normal aspect of cloud architecture.

Since Azure does not allow provisioning a database in your desired region, the closest alternative is Canada Central (canadacentral). You can provision the database there while keeping your application servers in east-1. You may need to account for network latency, cross-region data transfer costs, and replication strategies to ensure performance and reliability.

This approach - selecting the nearest available region - is standard practice in public cloud deployments and reflects the trade-offs between locality, latency, and service availability.

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin