Merge pull request #277576 from cosh/TSItoFabric

Tsi to fabric

Author: JamesJBarnett

.openpublishing.redirection.json

@@ -1649,6 +1649,11 @@
             "source_path_from_root": "/articles/dns/dns-getstarted-create-recordset.md",
             "redirect_url": "/azure/dns/dns-getstarted-powershell",
             "redirect_document_id": false
+        },
+		{
+            "source_path_from_root": "/articles/time-series-insights/migration-to-adx.md",
+            "redirect_url": "/azure/time-series-insights/migration-to-fabric.md",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/dns/dns-operations-dnszones-cli-nodejs.md",

articles/time-series-insights/TOC.yml

@@ -83,8 +83,8 @@
       href: time-series-insights-parameterized-urls.md
 - name: How-to guides
   items:
-  - name: Migrate to Azure Data Explorer
-    href: migration-to-adx.md
+  - name: Migrate to Fabric Real-Time Intelligence
+    href: migration-to-fabric.md
   - name: Grant data access
     href: concepts-access-policies.md
   - name: Connect to Event Hubs
@@ -127,7 +127,7 @@
       items:
       - name: How to migrate to new API versions
         href: how-to-api-migration.md
-      - name: How to migrate to Azure Data Explorer
+      - name: How to migrate to Fabric Real-Time Intelligence
         href: how-to-tsi-gen2-migration.md
   - name: Azure Time Series Insights Gen1
     items:
@@ -149,7 +149,7 @@
       href: time-series-insights-environment-mitigate-latency.md
     - name: Diagnose and troubleshoot
       href: time-series-insights-diagnose-and-solve-problems.md
-    - name: How to migrate to Azure Data Explorer
+    - name: How to migrate to Fabric Real-Time Intelligence
       href: how-to-tsi-gen1-migration.md
 - name: Reference
   items:

articles/time-series-insights/how-to-tsi-gen1-migration.md

@@ -1,34 +1,50 @@
 ---
-title: 'Time Series Insights Gen1 migration to Azure Data Explorer | Microsoft Docs'
-description: How to migrate Azure Time Series Insights Gen 1 environments to Azure Data Explorer.
+title: 'Time Series Insights Gen1 migration to Real-Time Intelligence in Microsoft Fabric | Microsoft Docs'
+description: How to migrate Azure Time Series Insights Gen 1 environments to Real-Time Intelligence in Microsoft Fabric.
 ms.service: time-series-insights
 author: tedvilutis
 ms.author: tvilutis
 ms.topic: conceptual
-ms.date: 3/15/2022
+ms.date: 6/10/2024
 ms.custom: tvilutis
 ---
 
-# Migrating Time Series Insights Gen1 to Azure Data Explorer
+# Migrating Time Series Insights Gen1 to Real-Time Intelligence in Microsoft Fabric
 
 [!INCLUDE [retirement](../../includes/tsi-retirement.md)]
 
 ## Overview
 
-The recommendation is to set up Azure Data Explorer cluster with a new consumer group from the Event Hub or IoT Hub and wait for retention period to pass and fill Azure Data Explorer with the same data as Time Series Insights environment.
-If telemetry data is required to be exported from Time Series Insights environment, the suggestion is to use Time Series Insights Query API to download the events in batches and serialize in required format. 
-For reference data, Time Series Insights Explorer or Reference Data API can be used to download reference data set and upload it into Azure Data Explorer as another table. Then, materialized views in Azure Data Explorer can be used to join reference data with telemetry data. Use materialized view with arg_max() aggregation function which will get the latest record per entity, as demonstrated in the following example. For more information about materialized views, read the following documentation: [Materialized views use cases](/azure/data-explorer/kusto/management/materialized-views/materialized-view-overview#materialized-views-use-cases).
+[Eventhouse](/fabric/real-time-intelligence/eventhouse) is the time series database in Real-Time Intelligence. It serves as the target for migrating data away from Time Series Insights.
 
-```
-.create materialized-view MVName on table T
-{
-    T
-    | summarize arg_max(Column1,*) by Column2
-}
-```
-## Translate Time Series Insights Queries to KQL
+### Prerequisites
+
+* A [workspace](/fabric/get-started/create-workspaces) with a Microsoft Fabric-enabled [capacity](/fabric/enterprise/licenses#capacity)
+* An [event house](/fabric/real-time-intelligence/create-eventhouse) in your workspace
+
+### Ingest new data
+
+Use the following steps to start ingesting new data into your Eventhouse:
+
+1. Configure your [event hub](/azure/event-hubs/event-hubs-about) with a new consumer group.
+
+2. Consume data from the data source and ingest it into your Eventhouse. Refer to the documentation on how to [ingest data from your event hub](/fabric/real-time-intelligence/get-data-event-hub).
 
-For queries, the recommendation is to use KQL in Azure Data Explorer.
+### Migrate historical data from Time Series Insights
+
+If you need to export data from your Time Series Insights environment, you can use the Time Series Insights Query API to download the events in batches and serialize them in the required format. Depending on where you stored the exported data, you can ingest the data from [Azure Storage](/fabric/real-time-intelligence/get-data-azure-storage), [local files](/fabric/real-time-intelligence/get-data-local-file), or [OneLake](/fabric/real-time-intelligence/get-data-onelake).
+
+### Migrate reference data
+
+Use the following steps to migrate reference data:
+
+1. Use Time Series Insights Explorer or the Reference Data API to download the reference data set.
+
+2. Once you have the reference data set, [upload it to your Eventhouse](/fabric/real-time-intelligence/get-data-local-file) as another table. By uploading the reference data set, you can access and utilize it within your Eventhouse environment.
+
+## Translate Time Series Insights Queries to Kusto Query Language
+
+For queries, the recommendation is to use Kusto Query Language in Eventhouse.
 
 #### Events
 ```TSQ
@@ -154,4 +170,3 @@ _q
     _meas3,
 | sort by _dim0 nulls last, _dim1 nulls last
 ```
-