Unable to deploy Web App +Database and Azure Database MySQL flexible Server

Question

I am trying to deploy the Azure resources needed in order to install Open EMR

see blog link:https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/deploying-openemr-on-azure/3741455

however, I am receiving deployment errors from Azure My SQL flexible server ,see below:

{

  "code": "DeploymentFailed",

  "target": "/subscriptions/b9e3cbe3-901a-4c83-8d61-0a6587864703/resourceGroups/my-open-emr-azure/providers/Microsoft.Resources/deployments/MySqlFlexibleServer_6ea05d60c97711f089aa7989a271c97d",

  "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/b9e3cbe3-901a-4c83-8d61-0a6587864703/resourceGroups/my-open-emr-azure/providers/Microsoft.DBforMySQL/flexibleServers/my-open-emr-azure",

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

    }

AND

I am also not able to deploy the Web App + Database :

Error Message: MySQL - Flexible Server is not available for your selection of subscription and location

for Central US?

Can you help with the deployment and install of open EMR on Azure App Services?

Answer 1

To address the deployment errors you are encountering with Azure Database for MySQL flexible server, here are a few troubleshooting steps you can take:

1. Check Subscription and Region Availability: The error message indicates that the MySQL Flexible Server might not be available for your selected subscription and location (Central US). You can verify the availability of Azure Database for MySQL flexible server in different Azure regions by checking the Azure services availability page. If it's not available in Central US, consider deploying in a different region where it is supported.
2. List Deployment Operations: To get more details about the deployment failure, you can list the deployment operations for your resource group. Use the following Azure CLI command to see the specific errors:

      az deployment operation group list \
        --resource-group my-open-emr-azure \
        --name MySqlFlexibleServer_6ea05d60c97711f089aa7989a271c97d
   

   This will provide you with more context on what went wrong during the deployment.
3. Check Resource Limits: Sometimes, deployment failures can occur due to hitting resource limits in your subscription. Ensure that you have not exceeded any quotas for your Azure subscription.
4. Review Error Codes: The error code ResourceDeploymentFailure suggests that the resource write operation failed. You can check the specific error codes and their mitigations in the Azure CLI documentation to see if there are any specific actions you can take to resolve the issue.
5. Consider Using Service Connector: If you are deploying a web app alongside the database, consider using the Service Connector to establish a connection between your Azure App Service and the Azure Database for MySQL flexible server instance. This can simplify the setup process.

If you continue to face issues, you may want to reach out to Azure support for further assistance with your specific deployment scenario.

---

References:

• Troubleshoot Azure Database for MySQL - Flexible Server CLI errors
• Deploy a PHP and Azure Database for MySQL - Flexible Server app on Azure App Service

Answer 2

Hi Pantelitsa Dura,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

The error means your subscription cannot create MySQL Flexible Server in Central US. Either switch to a supported region or contact Azure Support to enable it, then retry the deployment.available for your selection of subscription and location” for Central US.

This is a subscription/region availability restriction for Azure Database for MySQL Flexible Server in Central US, not an OpenEMR template issue. Causes include subscription type limits, regional capacity, or Azure Policy blocking that region.

Please follow below TSG:

1. Use a different region supported by your subscription for both the web app and database, or
2. Try creating a stand-alone MySQL Flexible Server in the same subscription and region. If it fails, the limitation is confirmed.
3. Raise an Azure Support ticket with subscription ID, region, and error details to enable Central US or fix capacity/policy issues.
4. After MySQL Flexible Server is available, re-run the OpenEMR deployment and continue setup.

If the problem persists, feel free to mention it in the comment section.