Inventory every autoscale webhook instead of trusting the first portal entry

Source facts

Azure autoscale supports multiple webhook notifications, but Microsoft states that the portal displays only the first webhook even though the additional entries are visible in JSON. The documented configuration exposes a webhooks collection and allows optional properties for each receiver. Its webhook URI requirement is HTTPS. A single visible destination therefore does not establish that only one callback is configured. Microsoft Learn.

Applicability

Use this review when an autoscale setting has been maintained through the portal, command-line tools, or templates. Identify the specific setting and its target resource. Treat notification destinations separately from the scaling rules themselves; this article does not change capacity or threshold decisions.

DSE recommendation

Review the complete serialized notification configuration before approving or removing an autoscale callback destination. Reconcile every receiver with its owner and operational purpose, including entries that are absent from the portal’s first view. Inspect custom properties and authentication configuration without copying secrets into a general inventory. Ask the owner to resolve unknown endpoints before declaring the destination review complete.

Verification

Compare the full configuration before and after an approved edit. Confirm that the intended receiver changed and that unrelated callback entries remain as approved. During a controlled notification exercise, reconcile observed receiver activity with the complete list. Retain a redacted configuration comparison and owner decisions; a screenshot of one webhook is insufficient evidence for this particular inventory check.

Official references

Microsoft Learn: Autoscale email and webhook notifications. Source reviewed September 9, 2026.