Issue with creating MySQL Database on Azure

Question

I tried to create a database on MySQL via Azure. I was told to do so in North America while on my student account. I did so. However, I had two issues. One involved the database being created but ultimately failing because I'm restricted based on region. The other was a policy violation also due to region. I tried to make the database within the regions restricted to me under assignments, but even after using all of them, it would still fail.

Here is the error code for the first error mentioned. This was the closest I got to creating a database.
{

"code": "DeploymentFailed",

"target": "/subscriptions/2cfc0f88-f531-44dd-a538-ee56ac83301e/resourceGroups/RG-CIS9340/providers/Microsoft.Resources/deployments/MySqlFlexibleServer_8cb9fe97da624224bdd5938776cc9203",

"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",

"details": [

{

  "code": "ResourceDeploymentFailure",

  "target": "/subscriptions/2cfc0f88-f531-44dd-a538-ee56ac83301e/resourceGroups/RG-CIS9340/providers/Microsoft.DBforMySQL/flexibleServers/cis9340fall2025-sh",

  "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}

]

}

Answer 1

It appears that you are encountering issues related to regional restrictions when trying to create an Azure Database for MySQL. The error messages you received indicate that your subscription may not have access to create resources in the selected region, which is common for student accounts or certain Azure program offerings.

Here are some steps you can take to resolve the issues:

1. Check Regional Availability: Ensure that the region you are trying to deploy to is available for your subscription type. Some Azure programs have limited access to specific regions.
2. Choose a Different Region: If the region you are attempting to use is restricted, try selecting another region that is available for your subscription. You can refer to the list of regions available for Azure Database for MySQL.
3. Open a Support Request: If you believe you should have access to the region but are still facing issues, consider opening a support request with Azure. Specify the vCores you want to utilize and mention the restrictions you are encountering.
4. Register the MySQL Resource Provider: Ensure that your subscription is registered with the MySQL resource provider. This can be done through the Azure portal, Azure CLI, or Azure PowerShell.

If you continue to face issues, reviewing the deployment operations for more detailed error messages may provide additional insights into what went wrong during the provisioning process.

---

References:

• Resolve capacity errors for Azure Database for MySQL
• Tutorial: Build a JBoss web app with Azure App Service on Linux and MySQL

Answer 2

Hi @Shafayet Hasan

Thank you for contacting Microsoft Q&A. Please find below the detailed steps to address the reported issue.

It looks like you're running into a few hurdles while setting up your MySQL database on Azure. Based on what you’ve mentioned, it seems like the issues might be tied to regional restrictions on your student account, as well as potential naming or SKU requirements for the database. No worries though, here are some steps you can follow to troubleshoot:

1. Check Region Availability Double-check that the region you're trying to use actually supports MySQL and the SKU you’ve chosen. Azure sometimes restricts certain services by region, especially for student accounts, so it’s good to confirm upfront.
2. Stick to Approved Regions Make sure you're creating the database in a region that’s allowed for your student subscription. Azure typically has a list of supported regions for each type of subscription, so it’s worth checking that.
3. Verify Naming Rules The server name you choose needs to be globally unique. If someone else has already claimed that name, the deployment will fail. Try using something more specific or unique to avoid conflicts.
4. Monitor the Deployment Sometimes resource creation takes a little while. You can track the status of the deployment by checking the operations in the Azure portal or using ARM deployment tools to see what’s happening in the background.
5. Check Quotas Occasionally, deployments can fail if you've hit a resource quota limit. If that’s the case, you may need to request a quota increase for your subscription to move forward.
6. Review Error Details If you’re getting a "DeploymentFailed" error, be sure to read through the full error message. It will often give you a more detailed explanation of what went wrong, so you can pinpoint the exact issue.

Reference:

• Create an Azure Database for MySQL server
• Troubleshoot creating Azure Database for MySQL Flexible Server
• ARM Deployment Operations
• Request Quota Increase