Skip to content

Commit 9a70d5a

Browse files
authored
Merge pull request #188456 from Sekhar-Kutikuppala/patch-6
Update howto-export-data-legacy.md
2 parents c8b471a + 20ad488 commit 9a70d5a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/iot-central/core/howto-export-data-legacy.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ ms.service: iot-central
1010
---
1111
# Export IoT data to cloud destinations using data export (legacy)
1212

13-
The legacy data export feature is now deprecated and you should plan to migrate to the new [data export feature](howto-export-data.md). The legacy data export lacks important capabilities such as the availability of different data types, filtering, and message transformation. See the following table for a comparison of legacy data export with new data export:
13+
The legacy data export (classic) feature is now deprecated and you should plan to migrate to the new [data export feature](howto-export-data.md). The legacy data export lacks important capabilities such as the availability of different data types, filtering, and message transformation. See the following table for a comparison of legacy data export with new data export:
1414

15-
| Capability | Legacy data export | New data export |
15+
| Capability | Legacy data export (classic) | New data export |
1616
| :------------- | :---------- | :----------- |
1717
| Available data types | Telemetry, devices, device templates | Telemetry, property changes, device connectivity changes, device lifecycle changes, device template lifecycle changes |
1818
| Filtering | None | Depends on the data type exported. For telemetry, filtering by telemetry, message properties, property values |
@@ -24,7 +24,7 @@ The legacy data export feature is now deprecated and you should plan to migrate
2424

2525
## Migration considerations
2626

27-
To migrate a legacy data export to new data export, you should:
27+
To migrate a legacy data export (classic) to new data export, you should:
2828

2929
1. Use a test IoT Central application and create a new data export with the same data type and destination. You can optionally use the enrichments and data transformation functionality to make your export message shape similar to the message shape from your legacy data export.
3030
1. When you've tested your new data export and are ready to go to production, ensure any workflows or dependencies on your active legacy data exports are safely removed.
@@ -65,7 +65,7 @@ In the new data export, you can create a destination and reuse it across differe
6565
> [!Note]
6666
> This article describes the legacy data export features in IoT Central
6767
>
68-
> - Legacy data exports are scheduled to be retired on 31 March 2023. Migrate any legacy data exports to new exports
68+
> - Legacy data exports (classic) are scheduled to be retired. Migrate any legacy data exports to new exports
6969
>
7070
> - For information about the latest data export features, see [Export IoT data to cloud destinations using data export](./howto-export-data.md).
7171

0 commit comments

Comments
 (0)