when the scope is equal to resourceGroup it shouldnt not ask for subscription-id only for resource-group-name

[gabo89]

[gabo89]

was checking the code, we need to pass the subscription-id on scope: resourcegroup but we cant pass the location or it will try to do another stuff, the location is inherated from the location of the resource group itself, so theorically you only can deploy azure resouece in the same location as the resource group in scope: resourceGroup

[SydneyhSmith]

@gabo89 thanks for opening the issue-- do you mind clarifying what you are seeing as the issue? Are you saying we should flag that location isn't used with the resourceGroup scope? Thank you!

[matsest]

Agree that it makes sense that the subscription-id input is not needed when doing a resource group level deployment. Behavior should be similar to how Az PowerShell/CLI handles required parameters for these deployments.

For location this already seems to be in order (not required for resource group, but required for deployments on sub/mg/tenant).

[pedantic-curmudgeon]

I'm running into the same issue where I'm not sure it makes sense that subscription-id is required when performing a resourceGroup deployment. This information isn't required when using the Azure CLI to create a deployment with az deployment group create, for example.

Any chance of this being updated?

And as a workaround, could I just look up the subscription ID from my resource group and pass that in?

Thanks!