Default Azure location to resource group region during CLI setup

[garrytrinder]

Is your feature request related to a problem? Please describe.
Currently, the CLI defaults the Azure location to 'westus', even when the selected resource group exists in a different region. This can cause resource misplacement, increased latency, or unexpected costs if the default is not manually overridden.

Priority you would assign to the feature
Medium

Describe the solution you'd like
When a user selects an existing resource group in the CLI, the default Azure location should automatically match the region of the resource group. This will help ensure that newly provisioned resources are created in the intended region without requiring manual input every time.

Describe alternatives you've considered

• Manually editing the configuration or specifying the region each time the command is run
• Always double-checking resource group region in Azure Portal

Available workarounds

• Manually override the region during setup initialization
• Edit the generated configuration afterward

Additional context
Automating the default region selection based on resource group region will provide a smoother experience for users and reduce unintentional mistakes and resource sprawl. This will also make scripting and automated scenarios more reliable.

[sellakumaran]

Thanks @garrytrinder for opening this issue and providing such a clear description of the problem and its impact.

We agree that aligning the default Azure location with the selected resource group's region would improve the CLI experience and help avoid accidental misplacements. Your suggestions and outlined workarounds are helpful, and we’ll review this enhancement as part of our configuration workflow improvements.

We'll update this thread as we assess feasibility and next steps. Thanks again for the thoughtful request!