retiring
Azure has an end date
Microsoft lists Azure Anomaly Detector retirement for October 1, 2026.
Time-series anomaly detection API
A drop-in Azure Anomaly Detector replacement for time-series APIs.
Microsoft is retiring Azure Anomaly Detector on October 1, 2026. Go Insights gives you a lower-cost time-series detection API with JSON responses, expected ranges, anomaly flags, seasonality, and root-cause slices.
Watch a metric leave its expected range.
Send the same kind of time-series payload: get the band, anomaly flag, and values you need to alert or explain the change.
isAnomaly: true
$0.12-$0.20 / 1k
Lower overage pricing
Go Insights overage is priced below Azure's public Standard Univariate meter.
JSON API
Built for replacement work
Send timestamps and values. Receive expected values, margins, flags, and period.
OpenAPI
Simple to test
Use the live tester below, then move the same shape into your own job or product.
Azure Anomaly Detector is already in retirement mode.
Microsoft says new Anomaly Detector resources have been blocked since September 20, 2023, and the service retires on October 1, 2026. If an existing app still depends on it, the question is not whether to move. It is how much work the move needs to be.
Read Microsoft's retirement noticeSep 20, 2023New Azure Anomaly Detector resources stopped being available.Oct 1, 2026Microsoft's listed retirement date for the service.API pathMove the detection call before the shutdown becomes a product issue.Price is the main reason to look here.
Azure Standard Univariate public price
$0.314 / 1k
Go Insights paid overage starts at
$0.20 / 1k
Go Insights lowest overage on scale plans
$0.12 / 1k
That puts Go Insights overage roughly 36% to 62% below Azure's listed univariate transaction price, depending on plan. Paid plans include monthly detections that roll over.
Not a bigger platform. A cleaner replacement path.
Azure is broad. Fabric is broader. This page is for the narrower job: keep sending time-series data to an API and get anomaly decisions back without owning the detector.
| Question | Go Insights API | Azure Anomaly Detector |
|---|---|---|
| Status | Available for new users. Built as a standalone anomaly detection API. | Microsoft lists the service as retiring on October 1, 2026. |
| New resources | New API access can be issued. | Microsoft says new resources have been blocked since September 20, 2023. |
| Univariate detection | /timeseries/entire/detect and /timeseries/last/detect. |
Univariate anomaly detection endpoints for batch and last-point use cases. |
| Response shape | Expected values, upper/lower margins, anomaly flags, positive/negative flags, and period. | Expected values, margins, anomaly flags, positive/negative flags, and period. |
| Seasonality | Repeating patterns are learned automatically, so daily, weekly, monthly, and hourly rhythm is part of the baseline. | Designed for time-series anomaly detection with automatic period handling. |
| Pricing | Free plan, then paid plans from $25/month. Overage from $0.20 to $0.12 per 1k. | Azure lists Standard Univariate at $0.314 per 1k transactions. |
| Best fit | Teams replacing an API dependency, adding anomaly detection to a product, or moving away from a retiring service. | Existing Azure users who can keep running until retirement or plan a broader Microsoft Fabric migration. |
Test the replacement flow.
Pick a dataset, adjust sensitivity, and inspect the request and response. The important part is the JSON your application can chart, store, or alert on.
Request
PreparingResponse
actual
expected
expected band
anomaly
JSON inspector
{}
Product and ops metricsSignups, API errors, orders, CPU, and usage-style series.
Hard casesLevel shifts, seasonal spikes, square waves, low-volume movement, and noisy traffic.
Validation samplesMarketing, ecommerce, search, ads, and benchmark-style examples.
Keep the baseline behavior people expect.
Monday traffic is not Saturday traffic. Lunch-hour load is not midnight load. Month-end revenue is not a random spike just because it sits above last Tuesday.
The detector learns the repeating pattern in the series and scores each point against the right expected range. Weekly, monthly, daily, and hourly cycles are handled automatically, so a migration does not turn normal seasonality into false alarms.
Pattern learned before scoring
Expected range follows the cadence of the metric.
period: 7
hourlyIntraday loaddailyWorking patternsweeklyWeekday cyclesmonthlyCalendar effectsLower overage than Azure, with a free plan to test.
Azure lists Standard Univariate at $0.314 per 1,000 transactions. Go Insights overage starts at $0.20 per 1,000 and drops on larger plans. Paid plans include monthly detections that roll over.
Free
$0/mo
For validating payloads and response shape before you move a real workflow.
Starter
$25/mo
For prototypes, internal monitors, and first replacement jobs.
Production
$99/mo
For customer-facing usage, scheduled checks, and higher-volume replacement work.
Scale
$299/mo
For large metric fleets, multi-tenant products, and heavier API traffic.
Azure comparison uses the public Anomaly Detector Standard Univariate price of $0.314 per 1,000 transactions from the Azure Retail Prices API as of June 22, 2026. Prices shown in USD; EUR pricing can use the same headline amounts. See Azure pricing.
Replacing Azure Anomaly Detector?
Send us the kind of series you run today. We’ll test it against the API, show the response shape, and help you decide whether batch, last-point, or attributed detection fits the migration.
Get your free API key
1,000 calls/month free — no card required.