Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Azure Time Series Insights is retiring on March 31st 2025 #208

Open
azure-deprecation-automation opened this issue Mar 25, 2022 · 1 comment
Labels
area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:time-series-insights verified All notices that are verified by an official communication
Milestone

Comments

@azure-deprecation-automation

Azure Time Series Insights is retiring on March 31st 2025

Deadline: Mar 31, 2025
Impacted Services:

  • Azure Time Series Insights

More information:

Notice

Here's the official report from Microsoft:

Because Azure Data Explorer now provides a data analytics service for streaming telemetry data, we’ll retire Azure Time Series Insights on 31 March 2025. Please transition to using Azure Data Explorer by that date.

We encourage you to make the switch sooner to gain the richer benefits of Azure Data Explorer. In addition to the current features you already use, here’s a quick comparison between Azure Time Series Insights and Azure Data Explorer:

Features Azure Time Series Insights Azure Data Explorer
Data ingestion Limited to 1MB/s No limits on ingestions (scalable), 200 MB/s/node on a 16-core machine in ADX cluster.
Data Querying TSQ KQL, SQL
Data Visualization TSI Explorer, PBI PBI, Azure Data Explorer Dashboards, Grafana, Kibana and other visualization tools using ODBC/JDBC connectors

Beginning 31 March 2022 no new features will be released for Azure Time Series Insights. All Azure Time Series Insights instances created before the 31 March 2022 date will be supported through 31 March 2025. You can continue to use Azure Time Series Insights or transition to Azure Data Explorer.

Timeline

Phase Date Description
Announcement Mar 22, 2022 Deprecation was announced
Features Mar 31, 2022 No new features will be released for the service
Deprecation Mar 31, 2025 Service will no longer be supported

Impact

Azure Time Series Insights is retiring on March 31st 2025 and migration to Azure Data Explorer is required.

This is for both 1st and 2nd generation of Azure Time Series Insights.

Required Action

A migration guide to Azure Data Explorer is provided here, but at the time of announcement there does not seem to be an alternative for Time Series Insights Explorer.

Here's the official report from Microsoft:

Review pricing and then transition to Azure Data Explorer by 31 March 2025. Use the Azure Data Explorer Cost Estimator for price estimation. After 31 March 2025, Azure Time Series Insights will not be supported.

Contact

You can get in touch through the following options:

  • Get answers from Microsoft Q&A (link).
  • Contact Azure support (link).
@azure-deprecation-automation azure-deprecation-automation added area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:time-series-insights verified All notices that are verified by an official communication labels Mar 25, 2022
@azure-deprecation-automation azure-deprecation-automation added this to the 2025 milestone Mar 25, 2022
@azure-deprecation-automation
Copy link
Author

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

@azure-deprecation azure-deprecation locked and limited conversation to collaborators Mar 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:time-series-insights verified All notices that are verified by an official communication
Development

No branches or pull requests

1 participant