Event Grid Capacity/Scaling Event Response

Overview

This flow connects Azure scaling and resource-health signals to operational response via Azure Event Grid. It subscribes (subscription-scope webhook) to autoscale events (scale-up/scale-down initiated, completed, failed) and Resource Health availability-changed events. For every event it logs an audit row to Dataverse, opens a Capacity Incident only when the resource is genuinely degraded, and posts a red/green alert to the on-call Teams channel.

Why it matters: scaling and health events usually go unseen until something breaks. Routing them to people - with an incident opened only for real degradation - keeps ops ahead of capacity and reliability issues without alert noise.

Ships Off (demo).

Use Case

An ops/SRE team wants visibility and action on Azure scaling and resource-health events: awareness for every scale action, an auditable history for capacity planning, and an incident record only when a resource is actually unavailable or degraded.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Cost insight

Derive scale-out cost impact from the event count/category over time off the scaling-event table.

Flapping detection

Query recent scaling-event rows by resource to detect rapid scale oscillation.

PagerDuty / ServiceNow

Extend the degraded branch to page or open an external ticket on critical health events.

Tune degradation

Edit the degraded health statuses list to change which statuses open an incident.

Scope

Point the Event Grid resource type/topic at a specific resource group or resource instead of the whole subscription.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@and(greater(length(variables('varHealthStatus')),0), contains(concat(',',toLower(variables('varDegradedStatuses')),','), concat(',',toLower(variables('varHealthStatus')),',')))

coalesce(triggerOutputs()?['body/data/resourceInfo/id'], triggerOutputs()?['body/data/resourceUri'], triggerOutputs()?['body/subject'], '')

coalesce(triggerOutputs()?['body/data/resourceInfo/properties/availabilityState'], triggerOutputs()?['body/data/status'], triggerOutputs()?['body/data/availabilityState'], '')