azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
134 stars 6 forks source link

Classic data export in Azure IoT Central is retiring on March 31st 2023 #210

Open azure-deprecation-automation opened 2 years ago

azure-deprecation-automation commented 2 years ago

Classic data export in Azure IoT Central is retiring on March 31st 2023

Deadline: Mar 31, 2023 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

On 31 March 2023, classic data export (also known as legacy data export) in Azure IoT Central will be retired. Before that date, please migrate to the new data export, which provides more capabilities including filtering and message transformation.

We encourage you to migrate classic data exports in your Azure IoT Central application to new data exports sooner to gain richer benefits of new data exports in Azure IoT Central. Here is a quick comparison between classic data exports (legacy) and new data exports in Azure IoT Central.

Classic data export (legacy) New data export
Data types limited to telemetry, devices, and device templates. Data types include telemetry, property changes, device connectivity, device lifecycle, and device template lifecycle.
No support for filtering. Supports filtering and message enrichments prior to exporting data.

Timeline

Phase Date Description
Announcement Mar 24, 2022 Deprecation was announced
Deprecation Mar 31, 2023 The classic export will no longer work

Impact

Classic data export in Azure IoT Central is retiring on March 31st 2023 and migration to the new data export is required.

Required Action

A migration guide is available here.

Here's the official report from Microsoft:

To avoid disruption to your data exports to Azure IoT Central applications, follow these steps to migrate your existing legacy data exports to new data exports before 31 March 2023.

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 2 years ago

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.