MySQL Flexible Server deployment fails

Question

Hello, I am using MySQL Flexible Server as our main DB in our project. And sometimes I have to scale it, but it fails in ~30% cases.
There is one of failed message:

And also code that running in Azure Portal (I am doing all of it only in portal)

{  
    "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",  
    "contentVersion": "1.0.0.0",  
    "parameters": {  
        "location": {  
            "value": "Germany West Central"  
        },  
        "serverName": {  
            "value": "name-of-my-database"  
        },  
        "serverEdition": {  
            "value": "GeneralPurpose"  
        },  
        "vCores": {  
            "value": 16  
        },  
        "storageSizeGB": {  
            "value": 20  
        },  
        "haEnabled": {  
            "value": "Disabled"  
        },  
        "backupRetentionDays": {  
            "value": 7  
        },  
        "geoRedundantBackup": {  
            "value": "Disabled"  
        },  
        "storageIops": {  
            "value": 9473  
        },  
        "storageAutogrow": {  
            "value": "Enabled"  
        },  
        "vmName": {  
            "value": "Standard_D16ds_v4"  
        },  
        "standbyAvailabilityZone": {  
            "value": ""  
        }  
    }  
}  

Answer 1

Hello, this issue happens when in your region there is no new quotas for your database. So you have to ask quotas in "Help + Support".

To check that if there is quota for your database run this command in Azure CLI:

az mysql flexible-server update --resource-group your-resource-group-name --name your-database-name --sku-name Standard_B1s --tier Burstable

You will have this response: No available SKUs in this location.

If you just run scaling for your database it will just show error that your deployment failed.

Also Germany West Central have some troubles with new quotas, so I changed databases to West Europe.

Answer 2

This exact error is happening to me now.

Answer 3

It appears to have resolved by itself the next day. This seems to be an Azure environment issue that occurs temporarily.

Answer 4

I am experiencing a similar issue - the error message returned from ARM is not helpful at all. I went to the portal to try and deploy the same thing, in the same region (Central US), and received the following error:

My challenge is: How can I detect this issue via API BEFORE it fails? If a given subscription is not able to deploy a given resource in a given region, there has to be an API to discern that. This subscription shows Central US as an available region to deploy this resource, for MY subscription, using the resource provider API call at https://learn.microsoft.com/en-us/rest/api/resources/providers/get, as well as the doc at https://learn.microsoft.com/en-us/azure/mysql/flexible-server/overview#azure-regions.

How can I automate this?