There is a command group 'az_stack_mg'. This group of commands could 'manage deployment stacks at management 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_stack_mg_create'.The syntax is: az stack mg create --deny-settings-mode {denydelete, denywriteanddelete, none}
                   --location
                   --management-group-id
                   --name
                   [--action-on-unmanage {deleteall, deleteresources, detachall}]
                   [--cs]
                   [--delete-all {false, true}]
                   [--delete-resource-groups {false, true}]
                   [--delete-resources {false, true}]
                   [--deny-settings-excluded-actions]
                   [--deny-settings-excluded-principals]
                   [--deployment-subscription]
                   [--description]
                   [--no-wait]
                   [--parameters]
                   [--query-string]
                   [--tags]
                   [--template-file]
                   [--template-spec]
                   [--template-uri]
                   [--yes]. The 1th example of the child command would be to use it to 'create a deployment stack using template file', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-file simpleTemplate.json --location westus2 --description description --deny-settings-mode None. The 2th example of the child command would be to use it to 'create a deployment stack with parameter file and delete resources on unmanage', the syntax is: az stack mg create --name StackName --management-group-id myMg --action-on-unmanage deleteResources --template-file simpleTemplate.json --parameters simpleTemplateParams.json --location westus2 --description description --deny-settings-mode None. The 3th example of the child command would be to use it to 'create a deployment stack with template spec', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-spec TemplateSpecResourceIDWithVersion --location westus2 --description description --deny-settings-mode None. The 4th example of the child command would be to use it to 'create a deployment stack using bicep file and delete all resources on unmanage', the syntax is: az stack mg create --name StackName --management-group-id myMg --action-on-unmanage deleteAll --template-file simple.bicep --location westus2 --description description --deny-settings-mode None. The 5th example of the child command would be to use it to 'create a deployment stack using parameters from key value pairs', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-file simpleTemplate.json --location westus --description description --parameters simpleTemplateParams.json value1=foo value2=bar --deny-settings-mode None. The 6th example of the child command would be to use it to 'create a deployment stack from a local template  using a parameter file  a remote parameter file  and selectively overriding key value pairs', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-file azuredeploy.json --parameters @params.json --parameters https://mysite/params.json --parameters MyValue=This MyArray=@array.json --location westus --deny-settings-mode None. The 7th example of the child command would be to use it to 'create a deployment stack from a local template  using deny settings', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-file azuredeploy.json --deny-settings-mode denyDelete --deny-settings-excluded-actions Microsoft.Compute/virtualMachines/write --deny-settings-excluded-principals "test1 test2" --location westus. The 8th example of the child command would be to use it to 'create a deployment stack from a local template  apply deny settings to child scope', the syntax is: az stack mg create --name StackName --management-group-id myMg --template-file azuredeploy.json --deny-settings-mode denyDelete --deny-settings-excluded-actions Microsoft.Compute/virtualMachines/write --deny-settings-apply-to-child-scopes --location westus. The parameter '--deny-settings-mode --dm' is required. It is used to define which operations are denied on resources managed by the stack.. The parameter '--location -l' is required. It is used to the location to store deployment stack.. The parameter '--management-group-id -m' is required. It is used to the management group id to create stack at.. The parameter '--name -n' is required. It is used to the name of the deployment stack.. The parameter '--action-on-unmanage --aou' is optional. defines what happens to resources that are no longer managed after the stack is updated or deleted.. The parameter '--cs --deny-settings-apply-to-child-scopes' is optional. denysettings will be applied to child scopes.. The parameter '--delete-all' is optional. flag to indicate delete rather than detach for the resources and resource groups.. The parameter '--delete-resource-groups' is optional. flag to indicate delete rather than detach for the resource groups.. The parameter '--delete-resources' is optional. flag to indicate delete rather than detach for the resources.. The parameter '--deny-settings-excluded-actions --ea' is optional. list of role-based management operations that are excluded from the denysettings. up to 200 actions are permitted.. The parameter '--deny-settings-excluded-principals --ep' is optional. list of aad principal ids excluded from the lock. up to 5 principals are permitted.. The parameter '--deployment-subscription --ds' is optional. the scope at which the initial deployment should be created. if a scope is not specified, it will default to the scope of the deployment stack.. The parameter '--description' is optional. the description of deployment stack.. The parameter '--no-wait' is optional. do not wait for the long-running operation to finish.. The parameter '--parameters -p' is optional. parameters may be supplied from a file using the `@{path}` syntax, a json string, or as <key=value> pairs. parameters are evaluated in order, so when a value is assigned twice, the latter value will be used. it is recommended that you supply your parameters file first, and then override selectively using key=value syntax.. 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 '--tags' is optional. space-separated tags: key[=value] [key[=value] ...]. use "" to clear existing tags.. The parameter '--template-file -f' is optional. a path to a template file or bicep file in the file system.. The parameter '--template-spec -s' is optional. the template spec resource id.. The parameter '--template-uri -u' is optional. a uri to a remote template file.. The parameter '--yes' is optional. do not prompt for confirmation.. 