There is a command group 'az_iot_hub_job'. This group of commands could 'manage iot hub jobs  v2'. 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_job_create'.The syntax is: az iot hub job create --job-id
                      --job-type {scheduledevicemethod, scheduleupdatetwin}
                      [--auth-type {key, login}]
                      [--duration]
                      [--hub-name]
                      [--interval]
                      [--login]
                      [--mct]
                      [--method-name]
                      [--method-payload]
                      [--method-response-timeout]
                      [--patch]
                      [--query-condition]
                      [--resource-group]
                      [--start]
                      [--ttl]
                      [--wait {false, true}]. The 1th example of the child command would be to use it to 'create and schedule a job to update the twin tags of all devices', the syntax is: az iot hub job create --job-id {job_id} --job-type scheduleUpdateTwin -n {iothub_name} -q "*" --twin-patch '{"tags": {"deviceType": "Type1, Type2, Type3"}}'. The 2th example of the child command would be to use it to 'schedule job and block for result of  completed    failed  or  cancelled   specify poll interval in seconds', the syntax is: az iot hub job create --job-id {job_id} --job-type scheduleUpdateTwin -n {iothub_name} -q "*" --twin-patch '{"tags": {"deviceType": "Type1, Type2, Type3"}}' --wait --poll-interval 30. The 3th example of the child command would be to use it to 'create a job to update a desired twin property on a subset of devices  scheduled to run at an arbitrary future time', the syntax is: az iot hub job create --job-id {job_name} --job-type scheduleUpdateTwin -n {iothub_name} --twin-patch '{"properties":{"desired": {"temperatureF": 65}}}' --start-time "2050-01-08T12:19:56.868Z" --query-condition "deviceId IN ['MyDevice1', 'MyDevice2', 'MyDevice3']". The 4th example of the child command would be to use it to 'create and schedule a job to invoke a device method for a set of devices meeting a query condition', the syntax is: az iot hub job create --job-id {job_name} --job-type scheduleDeviceMethod -n {iothub_name} --method-name setSyncIntervalSec --method-payload 30 --query-condition "properties.reported.settings.syncIntervalSec != 30". The 5th example of the child command would be to use it to 'create and schedule a job to invoke a device method for all devices', the syntax is: az iot hub job create --job-id {job_name} --job-type scheduleDeviceMethod -q "*" -n {iothub_name} --method-name setSyncIntervalSec --method-payload '{"version":"1.0"}'. The parameter '--job-id' is required. It is used to iot hub job id.. The parameter '--job-type --jt' is required. It is used to the type of scheduled job.. 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 '--duration --poll-duration' is optional. total duration in seconds where job status will be checked if --wait flag is passed in.. The parameter '--hub-name -n' is optional. iot hub name or hostname. required if --login is not provided.. The parameter '--interval --poll-interval' is optional. interval in seconds that job status will be checked if --wait flag is passed in.. 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 '--mct --method-connect-timeout' is optional. maximum number of seconds to wait on device connection.. The parameter '--method-name --mn' is optional. target method for invocation.. The parameter '--method-payload --mp' is optional. json payload to be passed to method. must be file path or raw json.. The parameter '--method-response-timeout --mrt' is optional. maximum number of seconds to wait for device method result.. The parameter '--patch --twin-patch' is optional. the desired twin patch. provide file path or raw json.. The parameter '--query-condition -q' is optional. condition for device query to get devices to execute the job on. required if job type is scheduledevicemethod or scheduleupdatetwin. note: the service will prefix "select * from devices where " to the input.. 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 '--start --start-time' is optional. the scheduled start of the job in iso 8601 date time format. if no start time is provided, the job is queued for asap execution. using a custom start time that's in the past may cause the operation to fail.. The parameter '--ttl' is optional. max execution time in seconds, before job is terminated.. The parameter '--wait -w' is optional. block until the created job is in a completed, failed or cancelled state. will regularly poll on interval specified by --poll-interval.. 