There is a command group 'az_dt_data history_connection_create'. This group of commands could 'creates a data history connection between a digital twins instance and supported resources'. 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_dt_data history_connection_create_adx'.The syntax is: az dt data-history connection create adx --adx-cluster-name
                                         --adx-database-name
                                         --cn
                                         --dt-name
                                         --eh
                                         --ehn
                                         [--adx-property-events-table]
                                         [--adx-record-removals {false, true}]
                                         [--adx-relationship-events-table]
                                         [--adx-resource-group]
                                         [--adx-subscription]
                                         [--adx-table-name]
                                         [--adx-twin-events-table]
                                         [--ehc]
                                         [--ehg]
                                         [--ehs]
                                         [--mi-user-assigned]
                                         [--no-wait]
                                         [--resource-group]
                                         [--yes]. The 1th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with the  default event hub consumer group', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace}. The 2th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance using a user assigned identity associated with the digital twin with the  default event hub consumer group', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --mi-user-assigned {resource_id}. The 3th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with a custom azure data explorer table name and event hub consumer group', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --adx-property-events-table {adx_property_events_table_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --eventhub-consumer-group {event_hub_consumer_group}. The 4th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance integrating with an event hub and azure data explorer instances in different resource groups and subscriptions from the target instance', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --adx-resource-group {adx_resource_group} --adx-subscription {adx_subscription} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --eventhub-resource-group {event_hub_resource_group} --eventhub-subscription {event_subscription}. The 5th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with the  default event hub consumer group and skip the role assignment prompts', the syntax is: az dt data-history connection create adx -n {instance_name} -y --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace}. The 6th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with the  default event hub consumer group and enables record property and item removals  an additional column will be added to the table used for storing updates to properties of twins and relationships  defaulted to adtpropertyevents', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --adx-record-removals true. The 7th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with the  default event hub consumer group and creates two extra tables in the azure data explorer database  one table will be for recording twin lifecycle events and the other for relationship lifecycle events', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --adx-twin-events-table {adx_twin_events_table_name} --adx-relationship-events-table {adx_relationship_events_table_name}. The 8th example of the child command would be to use it to 'adds a data history connection to a target digital twins instance with the  default event hub consumer group  uses a custom twin property event table name  and creates two extra tables in the azure data explorer database', the syntax is: az dt data-history connection create adx -n {instance_name} --cn {time_series_database_connection_name} --adx-cluster-name {adx_cluster_name} --adx-database-name {adx_database_name} --eventhub {event_hub} --eventhub-namespace {event_hub_namespace} --adx-property-events-table {adx_property_events_table_name} --adx-twin-events-table {adx_twin_events_table_name} --adx-relationship-events-table {adx_relationship_events_table_name}. The parameter '--adx-cluster-name --adxc' is required. It is used to name of azure data explorer cluster to integrate with.. The parameter '--adx-database-name --adxd' is required. It is used to name of azure data explorer database to integrate with.. The parameter '--cn --conn-name' is required. It is used to name of data history connection.. The parameter '--dt-name --dtn -n' is required. It is used to digital twins instance name.. The parameter '--eh --eventhub' is required. It is used to name of eventhub to integrate with.. The parameter '--ehn --eventhub-namespace' is required. It is used to eventhub namespace identifier.. The parameter '--adx-property-events-table --adxpet' is optional. the name of the azure data explorer table used for storing updates to properties of twins and relationships.. The parameter '--adx-record-removals --adxrr' is optional. specifies whether or not to record twin / relationship property and item removals, including removals of indexed or keyed values (such as map entries, array elements, etc.). setting this property to 'true' will generate an additional column in the property events table in adx.. The parameter '--adx-relationship-events-table --adxret' is optional. the name of the azure data explorer table used for recording relationship lifecycle events. the table will not be created if this property is left unspecified.. The parameter '--adx-resource-group --adxg' is optional. name of azure data explorer resource group. if not provided, will use the digital twin's resource group.. The parameter '--adx-subscription --adxs' is optional. name or id of subscription where the azure data explorer exists. if not provided, will use the subscription that contains the digital twin instance.. The parameter '--adx-table-name --adxt' is optional. the name of the azure data explorer table used for storing updates to properties of twins and relationships.. The parameter '--adx-twin-events-table --adxtet' is optional. the name of the azure data explorer table used for recording twin lifecycle events. the table will not be created if this property is left unspecified.. The parameter '--ehc --eventhub-consumer-group' is optional. the eventhub consumer group to use when adx reads from eventhub.. The parameter '--ehg --eventhub-resource-group' is optional. name of eventhub resource group. if not provided, will use the digital twin's resource group.. The parameter '--ehs --eventhub-subscription' is optional. name or id of subscription where the eventhub exists. if not provided, will use the subscription that contains the digital twin instance.. The parameter '--mi-user-assigned --user' is optional. use an user-assigned managed identity for data history connection authentication. accepts the identity resource id. if not provided, will use system identity instead.. The parameter '--no-wait' is optional. do not wait for the long-running operation to finish.. The parameter '--resource-group -g' is optional. digital twins instance resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--yes -y' is optional. do not prompt for confirmation when assigning required roles.. 