This chapter covers Azure Service Health, a tool for tracking the health of the Azure platform itself, as distinct from monitoring your own resources. AZ-900 tests this under objective 3.3, alongside the broader Azure Monitor coverage from the previous chapter.
Jump to a section
A simple way to picture Azure Service Health
Before heading out, you might check a weather report to know whether conditions could affect your plans — not because you caused the weather, but because it's useful to know about factors outside your control that might impact you. Azure Service Health works similarly: it reports on the health of the underlying Azure platform itself — outages, planned maintenance, and other service-level events — so organizations know when an issue they're experiencing is due to something on Azure's side, not something in their own configuration.
What Azure Service Health does
Azure Service Health provides personalized information about the health of Azure services and regions that are relevant to the resources an organization actually uses, including active issues, planned maintenance, and health advisories.
How it differs from Azure Monitor
Azure Monitor (covered in the previous chapter) tracks the health and performance of an organization's own resources. Azure Service Health, by contrast, tracks the health of the underlying Azure platform and services themselves — helping distinguish between "something is wrong with my configuration" (an Azure Monitor concern) and "something is wrong with the Azure platform itself" (a Service Health concern).
Types of information Service Health provides
Service issues: active problems affecting Azure services.
Planned maintenance: upcoming maintenance that might affect specific services or regions.
Health advisories: changes or issues that might require action, even if they're not an active outage.
Why the distinction matters
When something goes wrong with an application, it's important to know whether the root cause lies in the organization's own configuration (something Azure Monitor would help diagnose) or in the underlying Azure platform itself (something Service Health would confirm) — troubleshooting looks very different depending on which it is.
Check Service Health when investigating an issue
When troubleshooting an unexpected problem, checking Service Health can quickly confirm or rule out whether an underlying Azure platform issue is the cause.
Review personalized health information
Service Health provides information specifically relevant to the services and regions an organization actually uses, rather than a generic status page for all of Azure.
Plan around scheduled maintenance
Reviewing planned maintenance notices helps an organization anticipate and prepare for potential impact ahead of time, rather than being caught by surprise.
Distinguish platform issues from configuration issues
Confirming whether an issue originates from the Azure platform itself (Service Health) or an organization's own resource configuration (Azure Monitor) directs troubleshooting efforts appropriately.
A team investigating unexpected application errors checks Azure Service Health and discovers an active service issue affecting the specific Azure service they depend on, immediately clarifying that the problem is on Azure's side rather than something in their own application configuration.
A separate team reviews upcoming planned maintenance notices in Service Health, allowing them to prepare for a specific service's scheduled maintenance window in advance, rather than being surprised by unexpected behavior when the maintenance actually occurs.
Objective 3.3 expects candidates to distinguish Azure Service Health (the health of the Azure platform itself) from Azure Monitor (the health of an organization's own resources).
A common wrong answer is confusing Service Health with Azure Monitor — Service Health tracks the underlying Azure platform's health; Azure Monitor tracks an organization's own resource performance and health. Another common trap is assuming Service Health only reports active outages — it also covers planned maintenance and broader health advisories.
Stable terms: Azure Service Health, service issue, planned maintenance. Recognizing the distinction between platform-level health (Service Health) and resource-level health (Azure Monitor) is the core exam-relevant idea.
Memory trick: Azure Monitor watches your resources. Azure Service Health watches the Azure platform itself, telling you when a problem is Azure's fault rather than your own configuration.
Azure Service Health provides personalized information about the health of Azure services and regions relevant to an organization's resources.
Service Health tracks the Azure platform's own health, distinct from Azure Monitor's tracking of an organization's own resources.
Service Health covers active service issues, planned maintenance, and broader health advisories.
Checking Service Health helps distinguish platform-level problems from an organization's own configuration issues during troubleshooting.
These come up on the exam all the time. Here's how to tell them apart.
Azure Monitor
Tracks your own resources' health and performance
Helps diagnose issues in your configuration
Data you collect from your own environment
Azure Service Health
Tracks the Azure platform's own health
Helps confirm whether an issue is Azure's fault
Information provided by Azure about its services
Mistake
Azure Service Health and Azure Monitor track the same thing.
Correct
Azure Monitor tracks the health and performance of an organization's own resources. Azure Service Health tracks the health of the underlying Azure platform and services themselves — a different, complementary scope.
Mistake
Service Health only reports on active outages.
Correct
It also provides information about planned maintenance and broader health advisories, not just active service issues.
Mistake
Service Health shows generic information for all of Azure, not specific to what an organization uses.
Correct
Service Health is personalized to the specific services and regions an organization actually uses, rather than presenting a one-size-fits-all view of the entire Azure platform.
It's a tool that provides personalized information about the health of Azure services and regions relevant to an organization's resources — including active service issues, planned maintenance, and health advisories.
Azure Monitor tracks the health and performance of an organization's own resources. Azure Service Health tracks the health of the underlying Azure platform and services themselves — helping determine whether an issue originates from an organization's configuration or from Azure's platform.
No — it also covers planned maintenance notices and broader health advisories, giving a fuller picture of platform health beyond just active incidents.
You've just covered Azure Service Health — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?