MSDEVBUILD / azure

Azure Service Health and Azure Status

UsersLOADBALANCERAzure region Zone 1 Zone 2 Zone 3 ✓ App stillonline
Is it your code or is Azure having a bad day? Service Health tells you, and alerts you first.

😟 THE PROBLEM

The team debugs its own code for an hour during an Azure regional incident.

😊 THE SOLUTION

Use Service Health and Resource Health alerts.

  • Unsure if Azure has a problem✓ Service Health for your regions
  • Surprised by maintenance✓ Planned maintenance notices
  • Is my VM healthy?✓ Resource Health
🛠️ Solved with: Azure Service Health
Module 3: Management & Governance ⏱ 5 min read Updated 11 Nov 2026

Quick answer

Azure Service Health keeps you informed about the health of Azure itself. It has three parts. Azure status is a global view of the health of all Azure services in all regions. Service Health is a personalised view of incidents, planned maintenance and advisories that affect *your* services and regions. Resource Health shows the health of *your individual* resources, such as a specific VM.

Exam objective: 3.4.2 Describe Azure Service Health. (Skills measured as of July 20, 2026)

Start with a question

Your app is slow. Is it your code, or is Azure having a bad day?

Azure Service Health answers that in seconds.

Explain it like I’m 10

The technical explanation

ViewScopeShows
Azure statusGlobal, publicWidespread incidents across Azure
Service HealthYour subscriptionsService issues, planned maintenance, health and security advisories
Resource HealthYour resourcesCurrent and past availability of each resource

Real-world business scenario

Entertainment

An online ticketing company

The problem
During a slowdown the team spent an hour debugging code, only to discover an Azure regional incident.
What they used
Service Health alerts for their regions and services, sent to the on-call channel, plus Resource Health alerts for databases.
Why that choice
Instant, personalised notifications about platform issues.
The result
The next incident was identified within minutes and traffic was moved to a healthy region.

When to use it and when not to

✓ Use it when…

  • Always set Service Health alerts for production subscriptions.

✕ Think twice when…

  • Relying only on the public status page; it is not personalised.
Ready for more?The full lesson adds the technical explanation, when to use it, interview questions and revision notes.

Interview preparation

Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.

Beginner What is Azure Service Health?

Model answer

A service that tells me when Azure itself has a problem or planned maintenance that could affect my resources, and lets me set alerts for it.

Intermediate What is the difference between Azure status, Service Health and Resource Health?

Model answer

Azure status is the broad, public view of all of Azure. Service Health is personalised to the services and regions I use. Resource Health zooms in on one of my resources, like whether a particular VM is available.

Experienced developer How do you make sure your team hears about Azure incidents quickly?

Model answer

Create Service Health alerts scoped to the subscriptions, services and regions in use, route them through action groups to email, SMS, Teams or the incident tool, and use Resource Health alerts for critical resources. Keep the post-incident reports for root-cause reviews.

Test yourself with exercises

3 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.

Question 1

Question 1 of 3

You want to be notified about planned maintenance that affects the Azure services and regions you use. What should you use?

Question 2

Question 2 of 3

Which component shows whether one specific VM is currently available?

Question 3

Question 3 of 3

Which view shows the health of all Azure services across all regions?

Quick revision

Key points

  • Azure status = global, all services, all regions.
  • Service Health = personalised to your services and regions.
  • Resource Health = your individual resources.
  • Set up Service Health alerts.

Important terminology

Azure status
A public, global page showing the health of all Azure services across regions.
Service Health
A personalised view of service issues, planned maintenance and advisories affecting your subscriptions.
Resource Health
The current and past health of your individual resources.

Common mistakes

  • Using Azure Advisor to find out about Azure outages.

Exam tips

  • "Notified about planned maintenance affecting my regions" = Service Health.
  • "Is my specific VM healthy?" = Resource Health.

Five quick revision questions

  1. 1.Which view shows the health of all Azure services globally?Show

    Azure status.

  2. 2.Which view is personalised to your services and regions?Show

    Service Health.

  3. 3.Which view shows the health of one specific VM?Show

    Resource Health.

  4. 4.Name two event types in Service Health.Show

    Service issues and planned maintenance (also health advisories).

  5. 5.How do you get notified automatically?Show

    Create Service Health alerts with action groups.

Official references

Make it stick: play a quick gameSort It, Match the Pairs, Lightning Round and Who Am I? Earn XP and badges. Play ❯

Finished this lesson? Tick it off. Your progress is saved in this browser.

Next up: Azure Monitor, Log Analytics, Alerts and Application Insights