Trying to setup action groupwith Cloud Service (classic) - health alerts not reporting

Question

Hi

I'm not sure if I've misconfigured something - I'm not an azure pro!

We have a cloud service (classic app) which is generating health alerts when I stop / start it - i.e. I can see the events in the Azure portal (Service Health->Resource Health->(service name) )

But these aren't getting sent to the webhook / email action group I setup

In Azure I've added an Alert rule (Alerts->Alert rule)

• for the Resource - selected my Cloud Service (classic)
• Alert Conditions - All selected
• Actions -> my action group (which just sends to a webhook & my email (which i got the creation email for))

Is it something to do with classic service not supporting this feature? or do stop/start health alerts not generate emails? Or is there something i need to do to generate health alerts ??

Thanks in advance!

Answer 1

Does Azure Cloud Service (classic) support health alerts through action groups?

Azure Cloud Service (classic) has limited functionality for modern alerting features. While you can see resource health alerts in the Azure portal, not all types of health events generate notifications via action groups. Specifically, stop/start operations on a Cloud Service (classic) may not trigger actionable alerts that send notifications. This limitation is inherent to the classic deployment model, which lacks full integration with modern Azure Monitor features.

---

Are stop/start operations supposed to trigger health alerts?

Stop/start operations typically generate resource health events visible under Service Health -> Resource Health in the Azure portal. However, these events might not automatically translate into Azure Monitor alerts unless explicitly configured. Azure Resource Health events for classic resources often do not provide the granularity or flexibility to define alert rules tied to specific lifecycle actions (stop/start).

---

Did I misconfigure the alert rule or action group?

It doesn't sound like the issue lies with your action group configuration. Since you are receiving the creation email for the action group and have correctly associated it with a webhook and email, the configuration seems fine. The