Anomaly Detector frequently asked questions

This article contains answers to frequently asked troubleshooting questions about the Anomaly Detector service.

When will Anomaly Detector be deprecated?

Starting on the 20th of September, 2023 you won’t be able to create new Anomaly Detector resources. The Anomaly Detector service is being retired on the 1st of October, 2026.

When to use Univariate Anomaly Detection?

If your goal is to detect anomalies out of a normal pattern on each individual time series purely based on their own historical data, use the univariate anomaly detector APIs. For example, you want to detect daily revenue anomalies based on revenue data itself, or you want to detect a CPU spike purely based on CPU data.

Can the Anomaly Detector service be used in other platforms or applications?

Anomaly Detector is now integrated into Power BI, Azure Data Explorer, and Azure Synapse. You could also use our service in Azure Machine Learning, and Azure Databricks.

Is Anomaly Detector available in my Azure region?

Anomaly Detector is generally available in many of the Microsoft Azure operated by 21Vianet regions. Choose the region that is best for you and your customers.

Can Anomaly Detector be deployed to the edge?

Use Univariate Anomaly Detector containers to deploy API features on-premises. Docker containers enable you to bring the service closer to your data for compliance, security, or other operational reasons.

Is the Anomaly Detector service zone resilient?

Yes. The Anomaly Detector service is zone-resilient by default.

How do I configure the Anomaly Detector service to be zone-resilient?

No customer configuration is necessary to enable zone-resiliency. Zone-resiliency for Anomaly Detector resources is available by default and managed by the service itself.