How Do You Migrate from Azure Anomaly Detector to Canary Edge?

How Should You Assess Your Current Azure Integration?

Before migrating, audit how you use Azure Anomaly Detector. Answer these three questions:

• Which endpoints do you call? Univariate detect (entire series), univariate detect (last point), or multivariate?
• How do you authenticate? The standard pattern uses the Ocp-Apim-Subscription-Key header.
• What is your request volume? Check Azure Portal metrics to size your Canary Edge plan.

This audit typically takes 30 minutes and prevents surprises during migration.

How Do You Create a Canary Edge Account?

Account setup takes under 2 minutes:

1. Sign up at canaryedge.com/sign-up
2. Go to your dashboard and generate an API key
3. Note your API key for the next step

The free tier includes 10,000 data points per month — enough for testing.

What Code Changes Are Required?

Two lines of code. That is the entire migration for most teams.

# Before (Azure)
endpoint = "https://your-resource.cognitiveservices.azure.com"
headers = {"Ocp-Apim-Subscription-Key": "azure-key-here"}

# After (Canary Edge)
endpoint = "https://api.canaryedge.com"
headers = {"Ocp-Apim-Subscription-Key": "canary-edge-key-here"}

The JSON request body, response schema, and endpoint paths are identical. Your downstream processing pipeline does not need any modifications.

Should You Upload Training Data for Fine-Tuning?

Fine-tuning is optional but significantly improves accuracy. Unlike Azure's one-size-fits-all model, Canary Edge fine-tunes to your specific machines.

1. Go to Dashboard > Machines > Add Machine
2. Upload a CSV of your normal operating data
3. Fine-tuning completes in seconds, not hours

Per-machine fine-tuning is what enables Canary Edge to catch contextual anomalies that Azure missed.

How Should You Run Parallel Testing?

Run Canary Edge alongside Azure for 1-2 weeks before cutting over. Send the same requests to both endpoints and compare detection results.

During parallel testing, verify:

• Detection results match or improve vs Azure
• Latency meets your requirements (Canary Edge is typically 2-3x faster)
• Dashboards and alerting pipelines work correctly
• Billing matches expected usage

How Do You Complete the Cut-Over?

Once parallel testing confirms Canary Edge meets your requirements, remove the Azure endpoint. Total migration time for most teams: under a day.

After cut-over, decommission your Azure Anomaly Detector resource to stop incurring Azure charges.

What Are the Most Common Migration Questions?

Do I need to change my JSON parsing logic? No. The response schema is identical to Azure.

What about multivariate detection? Multivariate detection is available — supporting 2-100 correlated sensor channels with per-channel anomaly attribution. Azure multivariate API compatibility is included via the POST /anomalydetector/v1.1/multivariate/models endpoint.

Can I keep my Azure API key format? Yes, Canary Edge uses the same Ocp-Apim-Subscription-Key header.

Start your free migration now or read the API docs.