Creating AppService with MySQL db fails

Question

Creating basic app service with MySQL db fails in West EU with free subscription. I already created 1 but the second I'm trying to create says the deployment fails. Summary says:

{"code":"DeploymentFailed","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":"BadRequest","message":"Virtual network associated with the link cannot be changed."}]}

In the details list resource privatelink.mysql.database.azure.com/privatelink.mysql.database.azure.com-dblink status ends up with conflict with the given error.

If I try to redeploy and view the script, there are validation issues in versions and resource references but fixing them as validation suggests gives error about the resource references.

Answer 1

@Jyri Annunen , since the Microsoft Q&A community has a policy that the question author cannot accept their own answer. They can only accept answers by others, I'll convert my initial comment to an answer in case you'd like to Accept the answer.

---

Just confirm you're using Create Web App + Database in the following manner?

On the Review + Create screen, you will notice the networking information. Towards the bottom, select Download as a template.

The conflict is with the template trying to create a private link record (privatelink.mysql.database.azure.com-dblink) where it already exists. I can't correlate what you already have versus what you're trying to create, but it could be VNet association with the private link endpoint, or private link endpoint name for the database, or something else.

What I advise is on the template screen, after you click Download as a template, click redeploy, and check the values prepopulated in the template against your existing VNet and Private Link associations.

Answer 2

Hello @Jyri Annunen !

Welcome to Microsoft QnA!

I see you are having trouble creating a second AppService with MySql as Backend

I suggest you do a quick check for :

• Ensure that there are no conflicting resources already deployed in the Virtual Network you are using. For example, make sure there are no existing connections, gateways, or other resources that could conflict with the new deployment.
• Double-check the naming conventions and ensure that all resources, including Virtual Networks, are named uniquely and do not conflict with existing resources.
• Review the limitations and quotas for your Azure subscription, as it's possible that you have reached a limit on the number of resources or certain configurations in your specific subscription type.

It would be helpful to have anu addiional Logs or the JSON messages

I hope this helps!

Kindly mark the answer as Accepted and Upvote in case it helped!

Regards

Answer 3

Workaround for this bug in template creation is in Ryan Hill's comment for his own answer:
"...using Create Web App + Database in the following manner?

On the Review + Create screen, you will notice the networking information. Towards the bottom, select Download as a template.

The conflict is with the template trying to create a private link record (privatelink.mysql.database.azure.com-dblink) where it already exists. I can't correlate what you already have versus what you're trying to create, but it could be VNet association with the private link endpoint, or private link endpoint name for the database, or something else.

What I advise is on the template screen, after you click Download as a template, click redeploy, and check the values prepopulated in the template against your existing VNet and Private Link associations."