Azure Monitor alerts, routed to the right on-call engineer

How the Azure Monitor integration works

1. Create a Azure Monitor integration in EvoHub On-Call and pick the escalation policy it should notify.
2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into Azure Monitor using the steps below.
3. Each Azure Monitor alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
4. Resolves automatically when the Azure Monitor condition is Resolved.

Set up Azure Monitor

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

# 1. Azure Monitor → Alerts → Action groups → create or edit one
# 2. Add an action of type Webhook:
URI: <your EvoHub integration URL>
Enable common alert schema: Yes   # must — legacy payloads are rejected

# 3. Attach the action group to your alert rules.

Azure Monitor + EvoHub — FAQ

How do I connect Azure Monitor to EvoHub?

In EvoHub, go to On-Call → Integrations, add Azure Monitor, and choose an escalation policy. Then configure Azure Monitor with the integration URL EvoHub shows you — the exact steps are on this page.

Do Azure Monitor alerts resolve automatically in EvoHub?

Resolves automatically when the Azure Monitor condition is Resolved.

How is the Azure Monitor integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.