There is a command group 'az_iot_hub_device identity'. This group of commands could 'manage iot devices'. 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_device identity_import'.The syntax is: az iot hub device-identity import [--auth-type {key, login}]
                                  [--hub-name]
                                  [--ibc]
                                  [--ibcu]
                                  [--identity]
                                  [--input-storage-account]
                                  [--login]
                                  [--obc]
                                  [--obcu]
                                  [--osa]
                                  [--resource-group]. The 1th example of the child command would be to use it to 'import all device identities from a blob by providing command parameters for input blob container and storage account as well as output blob container and storage account', the syntax is: az iot hub device-identity import -n {iothub_name} --ibc {input_blob_container_name} --isa {input_storage_account_name} --obc {output_blob_container_name} --osa {output_storage_account_name}. The 2th example of the child command would be to use it to 'import all device identities from a blob using an inline sas uri', the syntax is: az iot hub device-identity import -n {iothub_name} --ibcu {input_sas_uri} --obcu {output_sas_uri}. The 3th example of the child command would be to use it to 'import all device identities from a blob using a file path which contains sas uri', the syntax is: az iot hub device-identity import -n {iothub_name} --ibcu {input_sas_uri_filepath} --obcu {output_sas_uri_filepath}. The 4th example of the child command would be to use it to 'import all device identities from a blob using system assigned identity that has storage blob data contributor roles for both storage accounts  the input blob container and storage account as well as output blob container and storage account are provided as parameters to the command', the syntax is: az iot hub device-identity import -n {iothub_name} --ibc {input_blob_container_name} --isa {input_storage_account_name} --obc {output_blob_container_name} --osa {output_storage_account_name} --identity [system]. The 5th example of the child command would be to use it to 'import all device identities from a blob using system assigned identity that has storage blob data contributor roles for both storage accounts  the blob container uri does not need the blob sas token', the syntax is: az iot hub device-identity import -n {iothub_name} --ibcu {input_sas_uri} --obcu {output_sas_uri} --identity [system]. The 6th example of the child command would be to use it to 'import all device identities from a blob using user assigned managed identity that has storage blob data contributor roles for both storage accounts  the input blob container and storage account as well as output blob container and storage account are provided as parameters to the command', the syntax is: az iot hub device-identity import -n {iothub_name} --ibc {input_blob_container_name} --isa {input_storage_account_name} --obc {output_blob_container_name} --osa {output_storage_account_name} --identity {managed_identity_resource_id}. The 7th example of the child command would be to use it to 'import all device identities from a blob using user assigned managed identity that has storage blob data contributor roles for both storage accounts  the blob container uri does not need the blob sas token', the syntax is: az iot hub device-identity import -n {iothub_name} --ibcu {input_sas_uri} --obcu {output_sas_uri} --identity {managed_identity_resource_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 '--hub-name -n' is optional. iot hub name or hostname. required if --login is not provided.. The parameter '--ibc --input-blob-container' is optional. this blob container stores the file which defines operations to be performed on the identity registry. parameter is ignored when input_blob_container_uri is provided. read access is required for this blob container.. The parameter '--ibcu --input-blob-container-uri' is optional. blob shared access signature uri with read access to a blob container. this blob contains the operations to be performed on the identity registry. note: when using identity-based authentication an https:// uri is still required - but no sas token is necessary. input for this argument can be inline or from a file path.. The parameter '--identity' is optional. managed identity type to determine if system assigned managed identity or user assigned managed identity is used. for system assigned managed identity, use [system]. for user assigned managed identity, provide the user assigned managed identity resource id. this identity requires a storage blob data contributor role for the target storage account and contributor role for the iot hub.. The parameter '--input-storage-account --isa' is optional. name of azure storage account containing the input blob container.only required when input_blob_container_uri is not provided. read access is required.. 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 '--obc --output-blob-container' is optional. this blob container is used to output the status of the device identity import job and the results. only required when input_blob_container_uri is not provided. write access is required for this blob container.. The parameter '--obcu --output-blob-container-uri' is optional. blob shared access signature uri with write access to a blob container. this is used to output the status of the job and the results. note: when using identity-based authentication an https:// uri without the sas token is still required. input for this argument can be inline or from a file path.. The parameter '--osa --output-storage-account' is optional. name of azure storage account containing the output blob container.parameter is ignored when output_blob_container_uri is provided. write access is required.. The parameter '--resource-group -g' is optional. name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. 