Azure Service Health
Slide deck explaining Azure Service Health: what it shows, how it differs from Azure Status and Azure Monitor. Covers personalized impact, event types, Resource Health, alerting flow, triage path, and setup best practices.
Azure Service Health
Introduction to Azure Service Health: what it shows, how it differs from Azure Status and Azure Monitor.
Azure Service Health
Introduction to Azure Service Health: what it shows, how it differs from Azure Status and Azure Monitor.
What question does Service Health answer?
Service Health tells you whether Azure platform events affect you. Focus: Azure platform events (Microsoft-side). Goal: 'Does this affect my environment?'. Helps separate platform impact from your own issues.
Personalized impact
Service Health filters events to your subscriptions, services, and regions. Tied to your subscriptions. Relevant services only. Region-aware (where you run workloads). Less noise than a global status view.
Service Health event types
Service Health groups platform events into three practical categories. Service issues: incidents/outages. Planned maintenance: scheduled platform changes. Health advisories: important notices plus recommended actions.
Azure Status vs Azure Service Health
Azure Status is global; Service Health is personalized to you. Azure Status: public plus global view. Service Health: your subscriptions/services/regions. Use Status for broad awareness. Use Service Health to confirm your impact.
Azure Resource Health (resource-level)
Resource Health shows the health of a specific resource, like a Virtual Machine (VM). Focus: one resource at a time. Helps troubleshoot 'this VM is down'. Complements Service Health (platform view).
Service Health vs Azure Monitor
Service Health is platform events; Azure Monitor is your metrics and logs. Service Health: incidents, maintenance, advisories. Azure Monitor: workload telemetry (metrics plus logs). Example telemetry: VM Central Processing Unit (CPU) usage. Best together: cause plus symptoms.
High-level alerting flow
Service Health alerts route platform events to the right people automatically. Service Health event to Azure Activity Log. Alert rule: choose event types plus scope. Action group: email, Short Message Service (SMS), webhook. Outcome: automatic notifications, not manual checks.
Triage path during an incident
Use the right tool in the right order to reduce guesswork. Azure Status: broad/global signal. Service Health: confirm your impact. Azure Monitor: see workload symptoms. Decide next steps based on both views.
Set up Service Health notifications
Alert rules decide when; action groups decide who and how. Pick event types: issues / maintenance / advisories. Scope: subscriptions plus regions plus services. Action group: email, SMS, webhook targets. Verify: the team actually receives the notifications.
Pitfalls + 3-step checklist
Avoid confusion, and make notifications reliable. Azure Status equals global; Service Health equals personalized. Azure Monitor equals telemetry; Service Health equals platform events. Service Health informs; you still respond operationally. Checklist: alert rules to action groups to periodic review.