There is a command group 'az_iot_device_registration'. This group of commands could 'manage iot device registrations for the iot device provisioning service'. 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_device_registration_create'.The syntax is: az iot device registration create --registration-id
                                  [--auth-type {key, login}]
                                  [--certificate-file-path]
                                  [--ck]
                                  [--dps-name]
                                  [--enrollment-group-id]
                                  [--host]
                                  [--id-scope]
                                  [--key]
                                  [--key-file-path]
                                  [--login]
                                  [--pass]
                                  [--payload]
                                  [--resource-group]. The 1th example of the child command would be to use it to 'register an iot device using an individual enrollment', the syntax is: az iot device registration create -n {dps_name} --rid {registration_id}. The 2th example of the child command would be to use it to 'register an iot device using a group enrollment', the syntax is: az iot device registration create -n {dps_name} --rid {registration_id} --gid {group_enrollment_id}. The 3th example of the child command would be to use it to 'register an iot device using an individual enrollment  the device provisioning service id scope  and given symmetric key  this will bypass retrieving the id scope and individal enrollment symmetric key', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --key {symmetric_key}. The 4th example of the child command would be to use it to 'register an iot device using a group enrollment  the device provisioning service id scope  and given enrollment group symmetric key  this will bypass retrieving the id scope and enrollment group symmetric key  the symmetric key used for the device registration will be computed from the given symmetric key', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --gid {group_enrollment_id} --key {symmetric_key} --ck. The 5th example of the child command would be to use it to 'register an iot device using a group enrollment  the device provisioning service id scope  and given symmetric key  this will bypass retrieving the id scope  note that since the symmetric key should be the computed device key  the enrollment group id is not needed', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --key {symmetric_key}. The 6th example of the child command would be to use it to 'register an iot device using an individual enrollment  the device provisioning service id scope  and given certificate and key files  this will bypass retrieving the id scope', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --cp {certificate_file} --kp {key_file}. The 7th example of the child command would be to use it to 'register an iot device using an individual enrollment  the device provisioning service id scope  and given certificate and key files and passphrase for the key file  this will bypass retrieving the id scope', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --cp {certificate_file} --kp {key_file} --pass {passphrase}. The 8th example of the child command would be to use it to 'register an iot device using a group enrollment  the device provisioning service id scope  and given certificate and key files  this will bypass retrieving the id scope  note that the group enrollment id is not needed for x509 attestations and the subject of the certificate file is the registration id', the syntax is: az iot device registration create --id-scope {id_scope} --rid {registration_id} --cp {certificate_file} --kp {key_file}. The parameter '--registration-id --rid' is required. It is used to device registration id or individual enrollment id.. 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 '--certificate-file-path --cp' is optional. path to certificate pem file. required for x509 registrations.. The parameter '--ck --compute-key' is optional. flag to indicate that the symmetric key for the device registration should be computed from the given key with --symmetric-key.. The parameter '--dps-name -n' is optional. name of the azure iot hub device provisioning service. required if --login is not provided or authenticaton arguments and --id-scope are not provided.. The parameter '--enrollment-group-id --gid --group-id' is optional. enrollment group id. only needed to retrieve authentication arguments.. The parameter '--host --provisioning-host' is optional. endpoint pointing to the provisioning host to use.. The parameter '--id-scope --scope' is optional. id scope of the azure iot hub device provisioning service. if provided with authentication arguments, will avoid session login.. The parameter '--key --symmetric-key' is optional. the symmetric shared access key for the device registration.. The parameter '--key-file-path --kp' is optional. path to key pem file. required for x509 registrations.. 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 --dps-name is not provided or authenticaton arguments and --id-scope are not provided.. The parameter '--pass --passphrase' is optional. passphrase for the certificate.. The parameter '--payload' is optional. custom allocation payload as json. specifically for use with custom allocation policies using azure functions.. The parameter '--resource-group -g' is optional. name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. 