Merge pull request #220601 from baanders/12-6-graph-history

ADT: Graph history

Author: v-stsavell

articles/digital-twins/.openpublishing.redirection.digital-twins.json

@@ -35,6 +35,11 @@
       "redirect_url": "/azure/digital-twins/how-to-monitor",
       "redirect_document_id": false
     },
+    {
+      "source_path": "how-to-use-data-history.md",
+      "redirect_url": "/azure/digital-twins/how-to-create-data-history-connection",
+      "redirect_document_id": true
+    },
     {
       "source_path": "how-to-create-app-registration-portal.md",
       "redirect_url": "/azure/digital-twins/how-to-create-app-registration",

articles/digital-twins/TOC.yml

@@ -127,8 +127,8 @@
       href: how-to-create-endpoints.md
     - name: Create routes and filters
       href: how-to-create-routes.md
-    - name: Use data history with Azure Data Explorer
-      href: how-to-use-data-history.md
+    - name: Create a data history connection
+      href: how-to-create-data-history-connection.md
     - name: Integrate with Azure Time Series Insights
       href: how-to-integrate-time-series-insights.md
     - name: Integrate with Azure Maps

articles/digital-twins/concepts-data-explorer-plugin.md

@@ -78,7 +78,7 @@ Before querying with the plugin, you'll need to ingest your Azure Digital Twins
 
 ### Ingesting with data history
 
-The simplest way to ingest IoT data from Azure Digital Twins into Azure Data Explorer is to use the **data history** feature. This feature allows you to set up a connection between your Azure Digital Twins instance and an Azure Data Explorer cluster, and twin property updates are automatically historized to the cluster. This is a good choice if you're using telemetry data to bring your digital twins to life. For more information about this feature, see [Data history (with Azure Data Explorer)](concepts-data-history.md). 
+The simplest way to ingest IoT data from Azure Digital Twins into Azure Data Explorer is to use the **data history** feature. This feature allows you to set up a connection between your Azure Digital Twins instance and an Azure Data Explorer cluster, and graph updates (including twin property updates, twin lifecycle events, and relationship lifecycle events) are automatically historized to the cluster. This is a good choice if you're using telemetry data to bring your digital twins to life. For more information about this feature, see [Data history (with Azure Data Explorer)](concepts-data-history.md). 
 
 ### Direct ingestion
 
@@ -132,7 +132,7 @@ Once the target table is created, you can use the Azure Digital Twins plugin to
 
 #### Example schema
 
-Here's an example of a schema that might be used to represent shared data. The example follows the Azure Data Explorer [data history schema](concepts-data-history.md#data-schema).
+Here's an example of a schema that might be used to represent shared data. The example follows the Azure Data Explorer [data history schema for twin property updates](concepts-data-history.md#twin-property-updates).
 
 | `TimeStamp` | `SourceTimeStamp` | `TwinId` | `ModelId` | `Name` | `Value` | `RelationshipTarget` | `RelationshipID` |
 | --- | --- | --- | --- | --- | --- | --- | --- |

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

@@ -37,7 +37,7 @@ You can also integrate Azure Digital Twins into a [Microsoft Power Platform](/po
 
 You may want to send Azure Digital Twins data to other downstream services for storage or additional processing. 
 
-Digital twin data can be sent to most Azure services using *endpoints*. If your destination is [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), you can use *data history* instead to automatically send twin property updates to an Azure Data Explorer cluster, where they are stored as historical data and can be queried as such. The rest of this section describes these capabilities in more detail.
+Digital twin data can be sent to most Azure services using *endpoints*. If your destination is [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), you can use *data history* instead to automatically send graph updates to an Azure Data Explorer cluster, where they are stored as historical data and can be queried as such. The rest of this section describes these capabilities in more detail.
 
 >[!NOTE]
 >Azure Digital Twins implements *at least once* delivery for data emitted to egress services. 
@@ -57,7 +57,7 @@ For detailed instructions on how to send Azure Digital Twins data to Azure Maps,
 
 ### Data history
 
-To send twin data to [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), set up a [data history connection](concepts-data-history.md) that automatically historizes digital twin property updates from your Azure Digital Twins instance to an Azure Data Explorer cluster. The data history connection requires an [event hub](../event-hubs/event-hubs-about.md), but doesn't require an explicit endpoint.
+To send twin data to [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), set up a [data history connection](concepts-data-history.md) that automatically historizes graph updates from your Azure Digital Twins instance to an Azure Data Explorer cluster. The data history connection requires an [event hub](../event-hubs/event-hubs-about.md), but doesn't require an explicit endpoint.
 
 Once the data has been historized, you can query this data in Azure Data Explorer using the [Azure Digital Twins query plugin for Azure Data Explorer](concepts-data-explorer-plugin.md).
 

articles/digital-twins/concepts-data-ingress-egress.md

@@ -5,7 +5,7 @@ titleSuffix: Azure Digital Twins
 description: Learn about the basics of the Azure Digital Twins query language.
 author: baanders
 ms.author: baanders # Microsoft employees only
-ms.date: 02/28/2022
+ms.date: 01/10/2023
 ms.topic: conceptual
 ms.service: digital-twins
 ms.custom: contperf-fy21q2
@@ -48,7 +48,7 @@ When writing queries for Azure Digital Twins, keep the following considerations
 
 The Azure Digital Twins query language is only for querying the **present** state of your digital twins and relationships.
 
-To run queries on historized digital twin data collected over time, use the [data history](concepts-data-history.md) feature to connect your Azure Digital Twins instance to an [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) cluster. This will automatically historize digital twin property updates to Azure Data Explorer, where they can be queried using the [Azure Digital Twins plugin for Azure Data Explorer](concepts-data-explorer-plugin.md).
+To run queries on historized twin graph data collected over time, use the [data history](concepts-data-history.md) feature to connect your Azure Digital Twins instance to an [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) cluster. This will automatically historize graph updates to Azure Data Explorer, where they can be queried using the [Azure Digital Twins plugin for Azure Data Explorer](concepts-data-explorer-plugin.md).
 
 ## Next steps