Issues creating mysql server using the Azure database for mysql service

KP EDA 0 Reputation points
2025-12-08T22:02:03.12+00:00

Hi,

We just signed up for the Azure ISV Success program few weeks ago though our partner portal and have created a new subscription using the allocated Azure credits. We have created some resources for our application using this subscription in the central US region. Unfortunately, we are not able to create a mysql flexible server in this or many other regions we have tried. The deployment errors out saying that this subscription does not have rights to create database server in that region for all regions we have tried so far. I am including the error screenshot below.

Can you please help us resolve this issue? Our application cannot work without a mysql server.

User's image

Azure Database for MySQL
{count} votes

1 answer

Sort by: Most helpful
  1. Pilladi Padma Sai Manisha 575 Reputation points Microsoft External Staff Moderator
    2025-12-08T22:11:57.32+00:00

    Hi KP EDA,
    Thank you for reaching out to Microsoft QA!
    It sounds like you’re facing issues creating a MySQL flexible server in Azure with your new subscription. This can be frustrating, especially since your application relies on it. Here are some steps and considerations you can take to troubleshoot and hopefully resolve the issue:

    What is causing the error:

    The error Provisioning in requested region is not supported. Your subscription might not have access to create a server in the selected region (Code: ProvisionNotSupportedOnLocation) indicates that this subscription is restricted from creating Azure Database for MySQL - Flexible Server in the regions you tried. This often happens with certain offer types (including some credit-based or benefit/ISV subscriptions) or when there is limited capacity and the platform only allows specific subscriptions to provision MySQL Flexible Server in that region.​

    What you can try right now:

    To quickly confirm scope and rule out configuration issues, please try the following:

    Try deploying a small MySQL Flexible Server in another supported region such as East US or West Europe and see if the behavior is the same.​

    Optionally, verify that the Microsoft.DBforMySQL resource provider is registered for the subscription (this is usually automatic, but it is a quick check).​

    If you see the same ProvisionNotSupportedOnLocation error across multiple regions, it confirms that the limitation is tied to the subscription/offer rather than a specific region configuration.​

    0 comments No 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.