Merge pull request #285307 from baanders/8-22-tsi

ADT: Remove TSI content

Author: JamesJBarnett

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

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "how-to-integrate-time-series-insights.md",
+      "redirect_url": "/azure/digital-twins/how-to-create-data-history-connection",
+      "redirect_document_id": false
+    },
     {
       "source_path": "how-to-manage-routes.md",
       "redirect_url": "/azure/digital-twins/how-to-create-routes",

articles/digital-twins/TOC.yml

@@ -129,8 +129,6 @@
       href: how-to-create-routes.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: Monitor and troubleshoot
     items:
     - name: Monitor your instance

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

@@ -153,5 +153,3 @@ For instance, if you want to represent a property with three fields for roll, pi
 * View the plugin documentation for the Kusto Query Language in Azure Data Explorer: [azure_digital_twins_query_request plugin](/azure/data-explorer/kusto/query/azure-digital-twins-query-request-plugin)
 
 * View sample queries using the plugin, including a walkthrough that runs the queries in an example scenario: [Azure Digital Twins query plugin for Azure Data Explorer: Sample queries and walkthrough](https://github.com/Azure-Samples/azure-digital-twins-getting-started/tree/main/adt-adx-queries) 
-
-* Read about another strategy for analyzing historical data in Azure Digital Twins: [Integrate with Azure Time Series Insights](how-to-integrate-time-series-insights.md)

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

@@ -21,7 +21,7 @@ Azure Digital Twins is typically used together with other services to create fle
 
 Azure Digital Twins can receive data from upstream services such as [IoT Hub](../iot-hub/about-iot-hub.md) or [Logic Apps](../logic-apps/logic-apps-overview.md), which are used to deliver telemetry and notifications. 
 
-Azure Digital Twins can also use [event routes](concepts-route-events.md) to send data to downstream services, such as [Azure Maps](../azure-maps/about-azure-maps.md) and [Time Series Insights](../time-series-insights/overview-what-is-tsi.md), for storage, workflow integration, analytics, and more. 
+Azure Digital Twins can also use [event routes](concepts-route-events.md) to send data to downstream services, such as [Azure Maps](../azure-maps/about-azure-maps.md), for storage, workflow integration, analytics, and more. 
 
 ## Data ingress
 
@@ -41,7 +41,7 @@ There are two main egress options in Azure Digital Twins. Digital twin data can
 
 ### Endpoints
 
-To send Azure Digital Twins data to most Azure services, such as [Azure Maps](../azure-maps/about-azure-maps.md), [Time Series Insights](../time-series-insights/overview-what-is-tsi.md), or [Azure Storage](../storage/common/storage-introduction.md), start by attaching the destination service to an *endpoint*. 
+To send Azure Digital Twins data to most Azure services, such as [Azure Maps](../azure-maps/about-azure-maps.md) or [Azure Storage](../storage/common/storage-introduction.md), start by attaching the destination service to an *endpoint*. 
 
 Endpoints can be instances of any of these Azure services:
 * [Event Hubs](../event-hubs/event-hubs-about.md)
@@ -50,8 +50,6 @@ Endpoints can be instances of any of these Azure services:
 
 The endpoint is attached to an Azure Digital Twins instance using management APIs or the Azure portal, and can carry data along from the instance to other listening services. For more information about Azure Digital Twins endpoints, see [Endpoints and event routes](concepts-route-events.md).
 
-For detailed instructions on how to send Azure Digital Twins data to Azure Maps, see [Use Azure Digital Twins to update an Azure Maps indoor map](how-to-integrate-maps.md). For detailed instructions on how to send Azure Digital Twins data to Time Series Insights, see [Integrate with Time Series Insights](how-to-integrate-time-series-insights.md).
-
 ### 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 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.

articles/digital-twins/concepts-route-events.md

@@ -34,7 +34,7 @@ The following diagram illustrates the flow of event data through a larger IoT so
 
 :::image type="content" source="media/concepts-route-events/routing-workflow.png" alt-text="Diagram of Azure Digital Twins routing data through endpoints to several downstream services." border="false":::
 
-For egress of data outside Azure Digital Twins, typical downstream targets for event routes are Time Series Insights, Azure Maps, storage, and analytics solutions. Azure Digital Twins implements *at least once* delivery for data emitted to egress services. 
+For egress of data outside Azure Digital Twins, typical downstream targets for event routes are Azure Maps, storage, and analytics solutions. Azure Digital Twins implements *at least once* delivery for data emitted to egress services. 
 
 For routing of internal digital twin events within the same Azure Digital Twins solution, continue to the next section.