Skip to content

Commit a6987d1

Browse files
Merge pull request #221013 from baanders/12-9-dh
ADT: Small data history reorg
2 parents 21dcc1b + 286cdeb commit a6987d1

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/digital-twins/concepts-data-history.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,13 @@ Each Azure Digital Twins instance will have its own data history connection targ
5252
* **different tables** in the Azure Data Explorer cluster.
5353
* **the same table** in the Azure Data Explorer cluster. To do this, specify the same Azure Data Explorer table name while [creating the data history connections](how-to-use-data-history.md#set-up-data-history-connection). In the [data history table schema](#data-schema), the `ServiceId` column will contain the URL of the source Azure Digital Twins instance, so you can use this field to resolve which Azure Digital Twins instance emitted each record.
5454

55-
## Required permissions
55+
## Creating a data history connection
56+
57+
Once all the [resources](#resources-and-data-flow) and [permissions](#required-permissions) are set up, you can use the [Azure CLI](/cli/azure/what-is-azure-cli), [Azure portal](https://portal.azure.com), or the [Azure Digital Twins SDK](concepts-apis-sdks.md) to create the data history connection between them. The CLI command set is [az dt data-history](/cli/azure/dt/data-history).
58+
59+
For step-by-step instructions on how to set up a data history connection, see [Use data history with Azure Data Explorer](how-to-use-data-history.md).
60+
61+
### Required permissions
5662

5763
In order to set up a data history connection, your Azure Digital Twins instance must have the following permissions to access the Event Hubs and Azure Data Explorer resources. These roles enable Azure Digital Twins to configure the event hub and Azure Data Explorer database on your behalf (for example, creating a table in the database). These permissions can optionally be removed after data history is set up.
5864
* Event Hubs resource: **Azure Event Hubs Data Owner**
@@ -63,12 +69,6 @@ Later, your Azure Digital Twins instance must have the following permission on t
6369

6470
These permissions can be assigned using the Azure CLI or Azure portal.
6571

66-
## Creating a data history connection
67-
68-
Once all the [resources](#resources-and-data-flow) and [permissions](#required-permissions) are set up, you can use the [Azure CLI](/cli/azure/what-is-azure-cli), [Azure portal](https://portal.azure.com), or the [Azure Digital Twins SDK](concepts-apis-sdks.md) to create the data history connection between them. The CLI command set is [az dt data-history](/cli/azure/dt/data-history).
69-
70-
For instructions on how to set up a data history connection, see [Use data history with Azure Data Explorer](how-to-use-data-history.md).
71-
7272
## Data schema
7373

7474
Time series data for twin property updates is stored in Azure Data Explorer with the following schema:

0 commit comments

Comments
 (0)