Unable to create the azure database for Mysql servers

Was the region UK South? Because I've had the same issue today.

I was able to create it in UK West without a problem but this is not where I wanted to place it.

The behavior indicates a subscription/region capacity or access issue rather than a problem with the MySQL service itself. Use the following checks and fixes in order:

1. Check the exact error message
   In the failed deployment, open Operation details and note the full text (for example: region is restricted, subscription does not have access, region is out of capacity, specified SKU not supported in this region, or subscription is not registered to use namespace 'Microsoft.DBforMySQL'). The resolution depends on this text.
2. Register the MySQL resource provider for the subscription
   If the error mentions namespace 'Microsoft.DBforMySQL' or subscription access:
   • In Azure portal:
     1. Go to Subscriptions → select the affected subscription.
     2. Under Settings, select Resource providers.
     3. Filter by MySQL.
     4. For Microsoft.DBforMySQL, select Register (or Re-register).
   • Or via CLI:

          az provider register --namespace Microsoft.DBforMySQL
     

   • Or via PowerShell:

          Register-AzResourceProvider -ProviderNamespace Microsoft.DBforMySQL
     

   After registration completes, retry the server creation.
3. Handle regional restrictions / out-of-capacity errors
   If the error mentions:
   • The region is restricted.
   • The region is out of capacity.
   • Provisioning is restricted in this region. Choose a different region.
   • Subscriptions aren't available for provisioning in this region.
   Then the subscription currently cannot create MySQL Flexible Servers in that region. Options:
   • Try a different region that is allowed for the subscription.
   • If a specific region is required, open a support request with issue type Service and subscription limits to request region access for Azure Database for MySQL – Flexible Server.
4. Fix SKU / availability zone issues
   If the error mentions:
   • Specified SKU not supported in this region.
   • The specified VM family isn't supported in this region.
   • Specified Availability Zone not supported in this region.
   Then:
   • Choose a different compute SKU (different vCore tier/size) that is available in that region.
   • Or select a different availability zone, or remove explicit zone selection.
   • If a specific SKU/zone is required, submit a support request to ask for access; requests are reviewed case-by-case.
5. Quota exceeded errors
   If the error indicates not enough quota to provision or update the server:
   • Submit a quota increase request for Azure Database for MySQL – Flexible Server for the target region and vCore family.
6. Azure program subscriptions (limited regions)
   If using an Azure Program subscription (Azure Pass, Azure for Students, Visual Studio/ MSDN, BizSpark, Microsoft for Startups, etc.), some regions are not available for MySQL. In that case:
   • Use one of the supported regions for that offer; or
   • Submit an access request if the documentation for Azure Database for MySQL – Flexible Server allows it for the needed region.
7. If deployments still fail with region-related errors
   If all the above are checked and deployments still fail in multiple regions:
   • Open a Region access support request under Azure Database for MySQL – Flexible Server and specify the region and vCores required.
   • As a temporary workaround, try creating the server in a different subscription (if available) where region access is known to work.

References:

• Quickstart: Create an instance of Azure Database for MySQL with the Azure portal
• Resolve capacity errors for Azure Database for MySQL
• Tutorial: Build a JBoss web app with Azure App Service on Linux and MySQL (azure-portal)