Back to Blog
MigrationMarch 15, 20265 min read

Azure Anomaly Detector is Retiring: What You Need to Know

Microsoft announced in early 2026 that Azure Anomaly Detector will be retired on October 1, 2026. If you're running anomaly detection pipelines on Azure, you need a migration plan now.

What's Happening

Azure Anomaly Detector, part of Azure Cognitive Services, has been a popular choice for time-series anomaly detection since its launch in 2019. Microsoft has decided to retire the service as part of a broader consolidation of their AI portfolio.

After October 1, 2026: - The API endpoints will stop responding - Existing models and configurations will be deleted - There is no "legacy mode" or extension period

Who's Affected

Any team using the Azure Anomaly Detector REST API or SDK, including: - Industrial IoT monitoring pipelines - Financial transaction fraud detection - Infrastructure health monitoring - SLA compliance systems

Your Migration Options

**Option 1: Build your own** — Train and deploy custom models using Azure ML or open-source tools like Prophet or ARIMA. This gives you full control but requires ML expertise and ongoing maintenance.

**Option 2: Switch to another cloud provider** — AWS offers Lookout for Equipment (also retiring October 2026) and Lookout for Metrics. Google Cloud has no direct equivalent.

**Option 3: Use Canary Edge** — We built Canary Edge specifically for this migration. Our API accepts the same JSON schema as Azure Anomaly Detector, so in many cases you only need to change the endpoint URL and API key. No code changes, no retraining, no downtime.

Migration Timeline

We recommend starting your migration at least 60 days before the October deadline:

  1. **Now:** Evaluate alternatives and run parallel testing
  2. **July 2026:** Begin routing production traffic to your new provider
  3. **August 2026:** Complete migration and decommission Azure resources
  4. **September 2026:** Buffer month for any issues

How Canary Edge Helps

Our migration path is designed to be zero-friction:

  1. Sign up and get an API key (2 minutes)
  2. Replace your Azure endpoint URL with `api.canaryedge.com`
  3. Swap your Azure subscription key for a Canary Edge API key
  4. Your existing code works unchanged

The response format is identical, so your downstream processing pipeline doesn't need any modifications.

Read the full [Azure Migration Guide](/migrate) for step-by-step instructions.

All Posts