There is a command group 'az_deployment_group'. This group of commands could 'manage azure resource manager template deployment at resource group'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_deployment_group_create'.The syntax is: az deployment group create --resource-group
                           [--aux-subs]
                           [--aux-tenants]
                           [--confirm-with-what-if]
                           [--handle-extended-json-format]
                           [--mode {complete, incremental}]
                           [--name]
                           [--no-prompt {false, true}]
                           [--no-wait]
                           [--parameters]
                           [--proceed-if-no-change]
                           [--query-string]
                           [--rollback-on-error]
                           [--template-file]
                           [--template-spec]
                           [--template-uri]
                           [--what-if]
                           [--what-if-exclude-change-types {create, delete, deploy, ignore, modify, nochange}]
                           [--what-if-result-format {fullresourcepayloads, resourceidonly}]. The 1th example of the child command would be to use it to 'create a deployment at resource group from a remote template file  using parameters from a local json file', the syntax is: az deployment group create --resource-group testrg --name rollout01 \
    --template-uri https://myresource/azuredeploy.json --parameters @myparameters.json. The 2th example of the child command would be to use it to 'create a deployment at resource group from a local template file  using parameters from a json string', the syntax is: az deployment group create --resource-group testrg --name rollout01 \
    --template-file azuredeploy.json  \
    --parameters '{ \"policyName\": { \"value\": \"policy2\" } }'. The 3th example of the child command would be to use it to 'create a deployment at resource group from a local template file  using parameters from an array string', the syntax is: az deployment group create --resource-group testgroup --template-file demotemplate.json --parameters exampleString='inline string' exampleArray='("value1", "value2")'. The 4th example of the child command would be to use it to 'create a deployment at resource group from a local template  using a parameter file  a remote parameter file  and selectively overriding key value pairs', the syntax is: az deployment group create --resource-group testrg --name rollout01 \
    --template-file azuredeploy.json  --parameters @params.json \
    --parameters https://mysite/params.json --parameters MyValue=This MyArray=@array.json. The 5th example of the child command would be to use it to 'create a deployment at resource group scope from a template spec', the syntax is: az deployment group create --resource-group testrg --template-spec "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/testrg/providers/Microsoft.Resources/templateSpecs/myTemplateSpec/versions/1.0". The 6th example of the child command would be to use it to 'create a deployment at resource group scope from a bicepparam parameter file', the syntax is: az deployment group create --resource-group testrg --parameters parameters.bicepparam. The 7th example of the child command would be to use it to 'create a deployment at resource group across tenants', the syntax is: az deployment group create --resource-group testrg --name rollout01 \
    --template-file azuredeploy.json --parameters @myparameters.json --aux-tenants auxiliary_tenant01 auxiliary_tenant02. The parameter '--resource-group -g' is required. It is used to the resource group to create deployment at.. The parameter '--aux-subs' is optional. auxiliary subscriptions which will be used during deployment across tenants.. The parameter '--aux-tenants' is optional. auxiliary tenants which will be used during deployment across tenants.. The parameter '--confirm-with-what-if -c' is optional. instruct the command to run deployment what-if before executing the deployment. it then prompts you to acknowledge resource changes before it continues.. The parameter '--handle-extended-json-format -j' is optional. support to handle extended template content including multiline and comments in deployment.. The parameter '--mode' is optional. the deployment mode.. The parameter '--name -n' is optional. the deployment name.. The parameter '--no-prompt' is optional. the option to disable the prompt of missing parameters for arm template. when the value is true, the prompt requiring users to provide missing parameter will be ignored. the default value is false.. The parameter '--no-wait' is optional. do not wait for the long-running operation to finish.. The parameter '--parameters -p' is optional. supply deployment parameter values.. The parameter '--proceed-if-no-change' is optional. instruct the command to execute the deployment if the what-if result contains no resource changes. applicable when --confirm-with-what-if is set.. The parameter '--query-string -q' is optional. the query string (a sas token) to be used with the template-uri in the case of linked templates.. The parameter '--rollback-on-error' is optional. the name of a deployment to roll back to on error, or use as a flag to roll back to the last successful deployment.. The parameter '--template-file -f' is optional. the path to the template file or bicep file.. The parameter '--template-spec -s' is optional. the template spec resource id.. The parameter '--template-uri -u' is optional. the uri to the template file.. The parameter '--what-if -w' is optional. instruct the command to run deployment what-if.. The parameter '--what-if-exclude-change-types -x' is optional. space-separated list of resource change types to be excluded from what-if results. applicable when --confirm-with-what-if is set.. The parameter '--what-if-result-format -r' is optional. the format of what-if results. applicable when `--confirm-with-what-if` is set.. 