Hi,
Most of the times, when deploying App Services such as a webapp to a single region, you simply use the Azure App Service Deploy task, that is currently in version 3.0 and whose a preview of the next version is to come.
However, using the very same task to deploy an App Service to multiple regions, in case you have a HA setup is a little more challenging. Looking at the below screenshot:
you can easily specify the name of the App Service. The problem is that, when working with multiple regions, the name will most probably be the same in the other region, therefore, the task cannot distinguish which service is targeted. So, ideally, we should be able to select the resource group to make this distinction.
It turns out that one can select the resource group when ticking the Deploy to slot option:
but what if you don’t use slots??? Then, the easy fix is to put the value “production” in the Slot field.
Credits to Thomas Browet (@thomas_brw), one of my colleagues, for the tip.
Happy deployments!
Is it really possible to have web apps with the same name in different regions? Wouldn’t the public URL conflict?
LikeLike
I didn’t mention it but this post was addressing the scenario of an ILB ASE only, not public app services.
LikeLike