There is a command group 'az_iot_hub_configuration'. This group of commands could 'manage iot automatic device management configuration at scale'. 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_iot_hub_configuration_create'.The syntax is: az iot hub configuration create --config-id
                                --content
                                [--auth-type {key, login}]
                                [--cl]
                                [--cmq]
                                [--hub-name]
                                [--lab]
                                [--login]
                                [--metrics]
                                [--pri]
                                [--resource-group]
                                [--target-condition]. The 1th example of the child command would be to use it to 'create a device configuration with a priority of 3 that applies on condition when a device is tagged in building 9 and the environment is  test', the syntax is: az iot hub configuration create -c {config_name} -n {iothub_name} --content device_content.json --target-condition "tags.building=9 and tags.environment='test'" --priority 3. The 2th example of the child command would be to use it to 'create a device configuration with labels and provide user metrics inline  bash syntax example', the syntax is: az iot hub configuration create -c {config_name} -n {iothub_name} --content device_content.json --target-condition "tags.building=9" --labels '{"key0":"value0", "key1":"value1"}' --priority 10 --metrics '{"metrics": {"queries": {"mymetric": "select deviceId from devices where tags.location='US'"}}}'. The 3th example of the child command would be to use it to 'create a module configuration with labels and provide user metrics inline  cmd syntax example', the syntax is: az iot hub configuration create -c {config_name} -n {iothub_name} --content module_content.json --target-condition "from devices.modules where tags.building=9" --labels "{\"key0\":\"value0\", \"key1\":\"value1\"}" --metrics "{\"metrics\": {\"queries\": {\"mymetric\": \"select moduleId from devices.modules where tags.location='US'\"}}}". The 4th example of the child command would be to use it to 'create a module configuration with content and user metrics inline  powershell syntax example', the syntax is: az iot hub configuration create -c {config_name} -n {iothub_name} --content '{\"moduleContent\": {\"properties.desired.chillerWaterSettings\": {\"temperature\": 38, \"pressure\": 78}}}' --target-condition "from devices.modules where tags.building=9" --priority 1 --metrics '{\"metrics\": {\"queries\": {\"mymetric\":\"select moduleId from devices.modules where tags.location=''US''\"}}}'. The 5th example of the child command would be to use it to 'create a device configuration with an alternative input style of labels and metrics  shell agnostic', the syntax is: az iot hub configuration create -c {config_name} -n {iothub_name} --content device_content.json --target-condition "from devices.modules where tags.building=9" --custom-labels key0="value0" key1="value1" --priority 10 --custom-metric-queries mymetric1="select deviceId from devices where tags.location='US'" mymetric2="select *". The parameter '--config-id -c' is required. It is used to target device configuration name. lowercase and the following special characters are allowed: [-+%_*!'].. The parameter '--content -k' is required. It is used to device configuration content. provide file path or raw json.. The parameter '--auth-type' is optional. indicates whether the operation should auto-derive a policy key or use the current azure ad session. if the authentication type is login and the resource hostname is provided, resource lookup will be skipped unless needed.you can configure the default using `az configure --defaults iothub-data-auth-type=<auth-type-value>`.. The parameter '--cl --custom-labels' is optional. an alternative input style (space separated key=value pairs) for --labels and intended to replace it in the future. format example: key1=value1 key2="this is my value".. The parameter '--cmq --custom-metric-queries' is optional. an alternative input style (space separated key=value pairs) for --metrics and intended to replace it in the future. format example: metric1="select deviceid from devices where tags.location='us'" metric2="select *".. The parameter '--hub-name -n' is optional. iot hub name or hostname. required if --login is not provided.. The parameter '--lab --labels' is optional. map of labels to be applied to target configuration. using --custom-labels instead of --labels is recommended.format example: {"key0":"value0", "key1":"value1"}.. The parameter '--login -l' is optional. this command supports an entity connection string with rights to perform action. use to avoid session login via "az login". if both an entity connection string and name are provided the connection string takes priority. required if --hub-name is not provided.. The parameter '--metrics -m' is optional. device configuration metric definitions. provide file path or raw json.using --custom-metric-queries instead of --metrics is recommended.. The parameter '--pri --priority' is optional. weight of the device configuration in case of competing rules (highest wins).. The parameter '--resource-group -g' is optional. name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--target-condition --tc -t' is optional. target condition in which a device or module configuration applies to. configurations with no target condition will target no device or module. use the following format: "tags.environment='test'".. 