Managed resource group location

Andrew Herbst 1

We'd like to set the location for a managed resource group created during a managed application deployment (i.e. eastus, westus, etc.). It appears that this is possible when invoking via the command line:

az managedapp create -g <myresourcegroupid> -n someapp -l eastus ...

will create the MRG in eastus regardless of myresourcegroupid's location.

However, when deploying via the UI I'm unable to determine how we'd achieve the same functionality -- is this possible?

tbgangav-MSFT 10,381 Reputation points

2022-11-20T15:27:07.12+00:00

Hi @Andrew Herbst ,

Thanks for bringing this up. I was also able to reproduce the issue. IMO it should create managed resource group in the location which we select while we deploy the managed application but that's not the case when we try the deployment from Azure Portal or UI. I have reached out to our internal product team to confirm the same and to get deeper insights. Will keep you updated as I hear more information.
Andrew Herbst 1 Reputation point

2022-12-20T19:24:32.567+00:00

Hi @tbgangav-MSFT -- any updates on this?
Christina Roberts 1 Reputation point

2022-12-20T19:40:13.563+00:00
@tbgangav-MSFT I've been trying to figure this out as well, and have had no luck. There are a few different things that are confusing:

According to https://learn.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/create-uidefinition-overview, it should be possible to override the default location logic in the config section. However, the resource group location continues to be used.

According to https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/createuidefinition-test-cases#use-location-in-outputs, a CreateUIDefinition definition without location in the outputs should fail validation… but it doesn't. I have tried adding location to outputs as indicated in this test case, but it didn't help.

I thought that perhaps I could solve the problem by doing validation on the location of the resource group selected (to enforce that it is in the same location that we want the managed resource group to be in). However, I'm not seeing that the validation mechanism shown here works-- https://learn.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/create-uidefinition-overview.

Do I need to do something in the deployment template itself? Or other ideas on how to either prevent the location from the resource group from being used, or to restrict the selection of resource groups based on location?

Thanks,
Christina