# Azure Status

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/azure-status

## Quick definition

Azure Status is a public web page from Microsoft that tells you if Azure services are working correctly or having problems. It updates in real time so you can check if an issue you are experiencing is due to an Azure outage or something on your end. You do not need an Azure account to view it. It covers all Azure services across every region in the world.

## Simple meaning

Think of Azure Status like a giant airport departures board for all of Microsoft’s cloud services. You know when you go to an airport and look at the big screen to see if your flight is on time, delayed, or cancelled? Azure Status does the same thing, but instead of flights, it shows services like virtual machines, databases, or web apps. When you use Azure for your business or studies, you depend on these services being available. If something breaks, you need to know if it is a problem with your own setup or a problem with Azure itself. Azure Status is the first place you check. It is a simple page with a list of services and regions. Each service gets a colored icon: green means everything is fine, yellow means there is some degradation or slowness, and red means there is an outage. There is also an orange icon for information or maintenance. You can filter by region or service to narrow down what affects you. The key point is that Azure Status is different from Azure Service Health. Azure Status is a public page showing the overall health of Azure. Azure Service Health is a personalized dashboard inside your Azure subscription that tells you how issues affect your specific resources. Both are useful, but Azure Status is the broad, public view. For a beginner, the important takeaway is this: if your application running on Azure stops working, do not panic. First, go to Azure Status to see if Azure itself has a problem. If it does, you just wait for Microsoft to fix it. If it does not, then you need to start troubleshooting your own code, configuration, or network. This one simple step saves hours of wasted debugging time. Azure Status also has a historical view and an RSS feed so you can stay informed about past and ongoing issues. In short, it is the official health report card for Azure.

## Technical definition

Azure Status, often referred to as the Azure Status Dashboard, is a publicly accessible web page published by Microsoft that provides real-time visibility into the operational health of all Azure services and Azure regions. It serves as the authoritative source for service availability and is used by IT professionals, developers, and system administrators to determine whether service degradation or outages are caused by Microsoft's infrastructure or by other factors. The dashboard is updated continuously and reflects the current state of each service in each region. The underlying infrastructure for Azure Status relies on a network of monitoring probes and telemetry collection systems distributed across all Azure datacenters. These probes continuously perform health checks at multiple layers of the stack, including network connectivity, compute resource availability, storage access, and application-level endpoints. When a probe detects an anomaly, such as increased latency, error rates above a threshold, or total service unavailability, the information is aggregated and processed by a state management system. This system updates the status icons displayed on the Azure Status page. The icons follow a standard color code: green indicates available and healthy, yellow indicates degraded performance or latency, red indicates an outage, and orange indicates planned maintenance or informational messages. Each status entry includes a brief description of the issue, the affected services and regions, and a timestamp. Microsoft also publishes Root Cause Analyses (RCAs) for significant outages after the fact. These RCAs are detailed technical documents explaining what happened, why it happened, and what steps Microsoft is taking to prevent recurrence. From a standards perspective, Azure Status does not conform to a specific industry standard like ITIL, but it aligns with common incident management practices by providing proactive communication. The Service Level Agreements (SLAs) for Azure services refer to the Azure Status dashboard as the official record of uptime calculations. For example, if a service has a 99.99% SLA, any downtime recorded on Azure Status within the billing period is deducted from the SLA calculation. This makes Azure Status not just a monitoring tool but also a legal and financial record. IT professionals integrate Azure Status into their own monitoring systems using the Azure Status RSS feed or third-party tools that scrape the page. However, Microsoft recommends using the Azure Service Health API for programmatic access tied to a subscription. The API provides more granular data specific to the user's deployed resources. Azure Status only shows regional and service-level status, not individual resource status. For that, you need Azure Monitor or Resource Health. Azure Status is the global health indicator for the entire Azure platform, built on a robust telemetry system and serving as the official record for SLA and incident communication.

## Real-life example

Imagine you are the manager of a large apartment building. You have dozens of tenants who rely on essential services like water, electricity, and internet. One morning, several tenants call you saying their internet is down. Instead of running to every apartment and checking their routers, you first go to the building's main utility panel in the basement. You look at the big board that shows the status of all utilities for the whole building. If the main internet line breaker is tripped, you know the problem is with the building's provider, not with any individual tenant's equipment. This main utility panel is exactly like Azure Status. It shows you the health of the entire building's infrastructure. If the panel shows that the internet is working fine, then you know the problem is inside a specific apartment, maybe a loose cable or a faulty router. In Azure terms, the apartment building is the cloud platform. The tenants are your applications and services. The utilities are things like compute, storage, networking, and databases. When something goes wrong, you do not start rebuilding your application or changing configuration until you check Azure Status. If Azure Status shows a green light for the service you are using, you know the issue is on your side. You then check your own logs, network, and code. If Azure Status shows a red or yellow light, you wait for Microsoft to fix the issue and you do not waste time. Another part of this analogy is the difference between the public utility panel and a private panel just for your apartment. The public panel (Azure Status) shows the status of services for everyone. But you might also have a private smart panel in your own apartment (Azure Service Health) that shows how those services affect your specific devices. For example, the public panel might say 'Water is available' but your private panel might say 'Water pressure low in unit 4B' because there is a localized issue affecting only your part of the building. Both are useful, but the public panel is the first place to check because it tells you immediately if it is a widespread problem or a local one. If you skip checking the public panel and go straight to fixing your own stuff, you might waste hours troubleshooting a problem that is not yours to fix. This simple habit of checking Azure Status first can save a huge amount of time and frustration, just like checking the main utility panel in the basement first.

## Why it matters

Azure Status matters because it is the single source of truth for service availability in the Microsoft Azure cloud. For IT professionals managing production workloads, knowing whether an outage is internal or external is the first step in incident response. Without Azure Status, teams can spend valuable time troubleshooting their own systems when the root cause is a regional Azure outage. This leads to wasted effort, delayed resolution, and potentially increased business impact. In practice, Azure Status is the first thing a DevOps engineer checks when an alert fires. It directly influences decision-making: if Azure reports a problem, the team can pause their own troubleshooting and communicate to stakeholders that the issue is with the cloud provider. If Azure Status shows green, the team knows to look deeper into their own application, network, or configuration. This clear distinction is critical for maintaining efficient operations and meeting service level objectives. Azure Status is tied to Service Level Agreements (SLAs). If an outage occurs that is documented on Azure Status, the customer may be eligible for SLA credits. Therefore, Azure Status serves as an official record for financial and contractual purposes. Without it, there would be no authoritative way to prove downtime occurred. For security and governance, Azure Status also provides transparency. It allows organizations to plan maintenance windows and understand when services might be impacted. For example, if Azure Status shows planned maintenance for a database service in a specific region, a team can schedule their own maintenance or failover to another region in advance. Azure Status is not a 'nice to have' tool; it is a foundational component of any operational strategy in Azure. It reduces mean time to resolution (MTTR), supports SLA management, and enables proactive planning.

## Why it matters in exams

Azure Status is a topic that appears most directly in the AZ-900 (Azure Fundamentals) and AZ-104 (Azure Administrator) exams. In AZ-900, it is covered under the 'Azure Service Health' and 'Monitoring' objectives. Candidates are expected to understand the difference between Azure Status, Azure Service Health, and Azure Monitor. A typical question might describe a scenario where an application is down, and ask which tool the administrator should use first. The correct answer is often Azure Status if the question implies checking global Azure health, or Azure Service Health if the question implies checking how an outage affects the user's specific subscription. For AZ-104, the topic goes deeper. Candidates must know how to configure alerts based on service health, how to view historical issues, and how to set up notifications for planned maintenance. The exam may present a scenario where an administrator needs to be automatically notified when a specific Azure region experiences a service issue. The solution would involve creating a Service Health alert using Azure Monitor. For the AWS-related exams listed, Azure Status itself is not tested, but the concept of cloud provider status dashboards is transferable. AWS has a similar tool called the AWS Service Health Dashboard. The exam pattern for Azure exams often includes multiple-choice questions that test the candidate's ability to choose between Azure Status and other monitoring tools. For example, a question might list four tools: Azure Status, Azure Service Health, Azure Advisor, and Azure Monitor. The candidate must pick the one that shows the global health of Azure services without needing a subscription. The answer is Azure Status. Another common question type involves troubleshooting: 'Your application is slow. You check Azure Status and it shows green. What should you do next?' The expected answer is to check your own resource metrics and logs. A trap question might ask: 'Which tool provides personalized service health for your subscription?' and list Azure Status as a distractor. The correct answer is Azure Service Health. For the Google Cloud exams listed (like Google ACE or Cloud Digital Leader), the concept is similar but the tool is called Google Cloud Status Dashboard. While Azure Status is not directly on those exams, understanding the role of provider status dashboards is a foundational cloud concept that may appear in the context of 'reliability' or 'operations' objectives. For Azure exams, remember: Azure Status is public, global, and requires no login. Azure Service Health is private, subscription-specific, and requires a login. This distinction is the most frequently tested point.

## How it appears in exam questions

Azure Status shows up in exam questions primarily in two types of scenarios: tool selection and troubleshooting. In tool selection questions, the scenario describes a need to see the overall health of Azure services across all regions without logging into the Azure portal. The candidate must identify that Azure Status is the correct tool. For example, a question might say: 'You are a junior administrator who receives a report that several users in different companies report an inability to access Azure SQL Database. You have no access to any Azure subscriptions. Which tool can you use to verify the health of Azure SQL Database?' The answer is Azure Status. This tests the candidate's knowledge that the dashboard is public. In troubleshooting questions, the scenario is more elaborate. For instance: 'Your company runs a web application on Azure App Service. Users report slow response times. You log in to the Azure portal and check the metrics for the App Service plan. They show normal CPU and memory usage. What should you do next?' The next step should be to check Azure Status to see if there is a regional degradation. Some questions combine both aspects: 'After checking Azure Status, you see a yellow icon for App Service in the West US region. What does this indicate?' The answer is that the service is experiencing degraded performance, not a full outage. Another pattern involves alert configuration. A question might ask: 'You need to be notified automatically when a critical Azure service in your region goes down. Which service should you use to create an alert?' The answer is Azure Service Health (not Azure Status), because Azure Status is read-only and does not support alerts. A tricky variation might ask: 'You want to send an email to your team when a service issue is detected. You decide to use Azure Status RSS feed. Is this a valid approach?' The answer depends on the context: yes, the RSS feed exists, but Microsoft recommends Azure Service Health alerts for production environments because they are more reliable and customizable. Some questions test the difference between planned and unplanned events. A scenario might describe that an orange icon appears on Azure Status for a specific service. The candidate must know that this indicates planned maintenance or informational messages, not an active outage. The exam uses Azure Status as a distractor against Azure Service Health, a tool in a troubleshooting sequence, and a knowledge point about public vs. private dashboards.

## Example scenario

You are an Azure administrator at a mid-sized e-commerce company. Your company runs its online store on Azure virtual machines with a SQL database backend. One Tuesday morning, you receive a flood of alerts from your monitoring system: customers cannot add items to their shopping cart. The application is unresponsive. Your team begins to panic and starts checking the web server logs, the database connection strings, and the load balancer configuration. After twenty minutes of investigation, your lead developer calls you and says he cannot find anything wrong in the application code. The database connection is fine, and the servers are responding to pings. At this point, you remember your training from the AZ-104 exam. You open a browser and navigate to the Azure Status page. You look at the list of services and see a red icon next to Azure SQL Database in the East US region. You also see a note: 'Azure SQL Database is experiencing data access failures in East US. Engineers are investigating.' You immediately stop all internal troubleshooting. You inform your team that the issue is with Azure itself and that Microsoft is working on it. You post a message on your company's status page for customers. You also know that because this outage is recorded on Azure Status, your company may be eligible for SLA credits. Thirty minutes later, the red icon turns green and the application starts working again. Your team resumes normal operations without having to make any changes to their own systems. This scenario illustrates why Azure Status is the first place to check in any outage. By doing so, you saved your team at least twenty minutes of unnecessary debugging and avoided potentially harmful changes to the application code.

## Common mistakes

- **Mistake:** Thinking Azure Status and Azure Service Health are the same thing.
  - Why it is wrong: Azure Status is a public page that shows the health of all Azure services globally. Azure Service Health is a personalized view inside the Azure portal that shows how issues affect your specific subscription. They serve different purposes and use different data sources.
  - Fix: Remember: Azure Status is public and global. Azure Service Health is private and subscription-specific. Use Azure Status for initial checks, use Azure Service Health for detailed, personalized reports.
- **Mistake:** Believing that Azure Status requires an Azure subscription to access.
  - Why it is wrong: Azure Status is a completely public website hosted at status.azure.com. Anyone with an internet connection can view it. No login or subscription is required.
  - Fix: Know that you can check Azure Status from any device, any network, even without an Azure account. It is the first resource to use when you suspect a cloud-wide issue.
- **Mistake:** Using Azure Status to get notifications about service issues.
  - Why it is wrong: Azure Status is a static web page and an RSS feed. It does not support sending alerts to email, SMS, or webhooks. For automated notifications, you must use Azure Service Health alerts.
  - Fix: Do not rely on Azure Status for proactive alerts. Set up Service Health alerts in Azure Monitor if you need to be notified automatically about service issues affecting your subscription.
- **Mistake:** Assuming a green status on Azure Status means all resources in that service are healthy for your application.
  - Why it is wrong: Azure Status shows the general health of a service in a region, but it does not show the health of individual resources. A service can be green globally but your specific virtual machine might be down due to a local hardware failure or configuration error.
  - Fix: Use Azure Resource Health or Azure Monitor at the resource level to check the health of your specific virtual machines, databases, or web apps. Azure Status is only the starting point.
- **Mistake:** Ignoring the orange informational icons on Azure Status.
  - Why it is wrong: Orange icons indicate planned maintenance or informational messages. Ignoring them can lead to surprise downtime if maintenance is performed during your business-critical hours.
  - Fix: Regularly check Azure Status for upcoming maintenance events. Plan your own deployments and failover tests around these maintenance windows to avoid disruption.

## Exam trap

{"trap":"The exam might ask: 'You need to check the health of Azure services that affect your subscription. Which tool should you use?' and list both Azure Status and Azure Service Health as options. Learners choose Azure Status because they remember it is about service health.","why_learners_choose_it":"Learners often memorize that Azure Status is the tool for service health but forget the distinction between public and subscription-specific. They see the words 'check the health of Azure services' and default to Azure Status.","how_to_avoid_it":"Look for keywords in the question that indicate subscription-specific context, such as 'your subscription', 'your resources', or 'personalized view'. If the question mentions your specific subscription, the correct answer is Azure Service Health. If the question says 'public' or 'without logging in', choose Azure Status."}

## Commonly confused with

- **Azure Status vs Azure Service Health:** Azure Service Health is a personalized dashboard within the Azure portal that shows how Azure issues affect your specific subscription and resources. Azure Status is a public page showing the health of all services globally. Service Health includes alerts and RCAs; Azure Status does not. (Example: If you want to know if a regional outage affects your specific database, use Azure Service Health. If you just want to see if Azure worldwide has a problem, use Azure Status.)
- **Azure Status vs Azure Resource Health:** Azure Resource Health is a tool that reports the health of individual Azure resources like a specific virtual machine or database. Azure Status reports on entire services and regions. Resource Health is per-resource, Status is per-service. (Example: Azure Status says 'Virtual Machines are healthy in East US'. But Resource Health for your specific VM might say 'Your VM is unavailable due to host maintenance'.)
- **Azure Status vs Azure Monitor:** Azure Monitor is a comprehensive platform for collecting, analyzing, and acting on telemetry from your Azure and on-premises resources. Azure Status is a simple dashboard that only shows service-level health. Monitor is for detailed metrics and logs; Status is for a quick high-level overview. (Example: Use Azure Monitor to set up a CPU usage alert. Use Azure Status to check if Azure itself is having a problem that might explain unusual metrics.)
- **Azure Status vs AWS Service Health Dashboard:** AWS Service Health Dashboard is the equivalent of Azure Status for Amazon Web Services. Both are public, show regional service health, and use similar color codes. The difference is the cloud provider and the exact URL (status.azure.com vs health.aws.amazon.com). (Example: If you work with both clouds, remember that each has its own public status page. For Azure, it's Azure Status. For AWS, it's the AWS Service Health Dashboard.)

## Step-by-step breakdown

1. **Identify the user's need** — The process starts when someone suspects an Azure service is not working. This could be triggered by user reports, application alerts, or monitoring system notifications. The first question is whether the problem is inside or outside the user's control.
2. **Navigate to Azure Status page** — Open a web browser and go to status.azure.com. No authentication is required. This page is the official public face of Azure's operational health. It loads quickly and works on mobile devices as well.
3. **View the main dashboard** — The dashboard shows a list of all Azure services and regions. Each combination is marked with a colored icon. Green means available, yellow means degraded, red means outage, orange means maintenance or info. The page also shows the last updated timestamp.
4. **Filter by service or region** — Use the filter options to narrow the view. For example, if you care only about Azure SQL Database in West Europe, apply those filters. This reduces noise and helps you focus on your specific area of interest.
5. **Interpret the status icon and description** — Click on any service name to expand and see a detailed description of the issue. Read the description carefully. For yellow status, it may say 'latency increased' or 'error rates elevated'. For red, it will state 'service unavailable'. Note the start time and any update history.
6. **Make a decision based on the status** — If the status is green, the issue is likely on your side. Proceed to check your own resources, logs, and configurations. If the status is yellow or red, the issue is at the Azure level. Stop internal troubleshooting and wait for Microsoft's resolution, or initiate disaster recovery if needed.
7. **Use the RSS feed for ongoing monitoring** — If you need continuous visibility, subscribe to the Azure Status RSS feed. This feed provides updates on changes to the status page. However, for production workloads, set up Azure Service Health alerts instead because they are more reliable and customizable.
8. **Review historical data and RCAs if needed** — After the event, you can review the historical health on the same page. Microsoft also publishes Root Cause Analyses (RCAs) for significant outages. These documents are useful for post-mortems and for understanding how to improve your own architecture's resilience.

## Practical mini-lesson

Azure Status is often misunderstood as a monitoring tool, but in practice it is more of a reference tool. As an IT professional, you will rarely sit and watch the Azure Status page. Instead, you will visit it when something goes wrong. The key practical skill is knowing when to check it and how to interpret the information quickly. In a real production environment, here is how it works: your monitoring system, such as Azure Monitor or a third-party tool like Datadog, will alert you when a metric exceeds a threshold. For example, you might get an alert that your virtual machine's network latency has spiked above 500 ms. Your first instinct should be to check Azure Status. If Azure Status shows a yellow icon for Virtual Machines in your region, you know the problem is most likely at the Azure networking layer. You can then communicate to your team and stakeholders: 'We are seeing a known Azure issue in our region. Microsoft is aware and working on it.' This buys you time and prevents unnecessary escalation. However, if Azure Status shows green, you know the latency is caused by something inside your environment. You then look at your own network configuration, maybe a bad route table, a misconfigured load balancer, or an application that is sending too many requests. Another important practical use is during planned maintenance. Microsoft posts future maintenance events on Azure Status with an orange icon. As a professional, you should check this at least weekly to plan your own deployments. For example, if you see that Azure SQL Database in East US will undergo maintenance from 2:00 AM to 4:00 AM next Sunday, you can schedule your database failover to a secondary region during that window to keep your application online. What can go wrong? The most common issue is that people treat Azure Status as a real-time alert system and become frustrated when they do not get notifications. Azure Status is not designed for that. It is updated manually or semi-automatically by Microsoft's incident management team. There can be a delay of several minutes between an outage starting and the status page being updated. Therefore, you should never rely solely on Azure Status for time-sensitive detection. Instead, use your own monitoring that checks the actual service endpoints. Finally, there is the matter of SLA credits. If you experience downtime, you need to note the timestamps from Azure Status. That is the official record. Save a screenshot or pull the RSS data. For enterprise customers, this can translate into significant financial credits. The practical professional use of Azure Status is as a communication tool, a decision guide, and an official record, not as a primary monitoring system.

## Commands

```
az monitor activity-log list --resource-id /subscriptions/{subscription-id} --query "[?eventName.value=='Azure Portal']"
```
Lists Azure activity logs filtered to show Azure Portal events, useful for checking status changes related to portal service health.

*Exam note: Tests candidate's ability to query Azure Activity Log for service health events, a common scenario in AZ-104 and Azure Fundamentals exams.*

```
Get-AzResourceHealth -ResourceId /subscriptions/{subscription-id}/resourceGroups/{rg-name}/providers/Microsoft.Compute/virtualMachines/{vm-name}
```
Retrieves the resource health status of a specific Azure VM, showing if it's available, degraded, or unavailable.

*Exam note: Appears in AZ-104 to test understanding of Resource Health for individual resources vs. overall Azure Status.*

```
az rest --method get --uri "https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.ResourceHealth/availabilityStatuses?api-version=2020-05-01"
```
Returns availability statuses for all resources in a subscription, allowing programmatic Azure Status checks.

*Exam note: Used in Azure Developer Associate exams to test REST API knowledge for health monitoring.*

```
az monitor metrics list --resource /subscriptions/{sub-id}/resourceGroups/{rg}/providers/Microsoft.Web/sites/{webapp} --metric Http2xx --interval PT1H
```
Monitors HTTP 2xx responses for a web app, helping detect Azure Status issues affecting app availability.

*Exam note: Tests metric-based monitoring skills in AWS developer exams where Azure concepts are compared.*

```
Get-AzServiceHealth -EventType 'ServiceIssue' -Region 'EastUS'
```
Retrieves service health events for the East US region, filtering for service issues that impact Azure Status.

*Exam note: Common in Azure Fundamentals (AZ-900) to assess understanding of regional service health queries.*

```
az security va sql scan --vm-name {vm-name} --resource-group {rg} --workspace-id {ws-id}
```
Performs a vulnerability assessment scan on SQL Server, but can also detect underlying Azure Status issues affecting SQL services.

*Exam note: Appears in AZ-104 to test integration of security scanning with Azure Status monitoring.*

```
New-AzActionGroup -ResourceGroupName {rg} -Name 'StatusAlerts' -ShortName 'Status' -EmailReceiver @{name='Admin';emailAddress='admin@contoso.com'}
```
Creates an action group for Azure Status alerts, sending notifications when service health changes occur.

*Exam note: Tests alert configuration knowledge in Azure Administrator exams, often tied to Status monitoring scenarios.*

## Troubleshooting clues

- **Azure Status dashboard shows 'Unknown' for all services** — symptom: The Azure Status page at status.azure.com displays 'Unknown' for multiple regions and services.. This occurs when there's a DNS resolution failure or browser cache issue preventing the status page from querying Azure's backend health APIs. (Exam clue: Exam questions test that 'Unknown' on Status page typically indicates client-side issues, not actual Azure outages.)
- **Activity log shows 'Degraded' status but service is operational** — symptom: Users report no issues, but the Azure Status page or Resource Health shows 'Degraded' for a virtual network.. Resource Health may report 'Degraded' due to platform-side maintenance or transient network blips that don't affect end-user experience, causing false positives. (Exam clue: Tests ability to differentiate between actual service impact and platform-level indicators in AZ-104.)
- **Azure Status not updating after an outage** — symptom: Azure Status page continues to show 'Good' even after a widespread service disruption is resolved.. The Status page has a propagation delay (typically 5-15 minutes) for updating health data from backend telemetry systems like Azure Monitor. (Exam clue: Exam questions check understanding of Status page latency vs. real-time monitoring tools.)
- **Resource Health shows 'Unavailable' but VM is running** — symptom: A VM's Resource Health status is 'Unavailable', but the VM is accessible and running via RDP or SSH.. Resource Health checks platform-level connectivity and may flag a VM as unavailable if there's a storage or networking issue on the backend, even if the OS is operational. (Exam clue: Tests that Resource Health evaluates underlying platform health, not just OS-level availability.)
- **Azure Status region filter returns no data** — symptom: When filtering Azure Status by a specific region (e.g., 'East US 2'), the page shows no services or blank.. This occurs if the region is not fully deployed for Azure services or if the filter is misapplied by the browser's session storage, causing empty results. (Exam clue: Exams test troubleshooting of regional availability queries and understanding of region deployment phases.)
- **Service health alert fires but no incident found** — symptom: An Azure Monitor alert triggers for 'Service Health' but the Azure Status page shows no ongoing incidents.. Service health alerts can be triggered by planned maintenance events or advisory notifications, which are not always displayed as incidents on the Status dashboard. (Exam clue: Tests differentiation between alert types (incidents vs. advisories) in Azure administration exams.)
- **Azure Status API returns 403 Forbidden** — symptom: When using az rest or PowerShell to query Azure Status data, a 403 error is returned.. The user or service principal lacks the required permissions, specifically the 'Microsoft.ResourceHealth/events/read' or 'Microsoft.ResourceHealth/availabilityStatuses/read' role. (Exam clue: Appears in role-based access control questions in AZ-104 and Google Cloud exams where IAM concepts are compared.)
- **Status history shows gaps in data** — symptom: The Azure Status historical view shows missing time intervals for certain services.. Data gaps can result from regional logging failures, telemetry pipeline issues, or service-specific retention policies that limit historical data to 30 days. (Exam clue: Tests understanding of Status data retention and regional logging consistency.)

## Memory tip

Azure Status is public, global, and no login needed. Think 'Public Status Page' (PSP). Azure Service Health is private, subscription-specific, and needs login. Think 'Private Health Portal' (PHP). The letters are different, and so are the tools.

## FAQ

**Is Azure Status the same as Azure Service Health?**

No. Azure Status is a public page showing the overall health of all Azure services. Azure Service Health is a personalized dashboard inside your Azure subscription that shows how issues affect your specific resources.

**Do I need an Azure subscription to view Azure Status?**

No. Azure Status is publicly accessible at status.azure.com without any login or subscription.

**Can I set up alerts based on Azure Status?**

Not directly. Azure Status does not support alerting. To get notified about service issues affecting your subscription, use Azure Service Health alerts in Azure Monitor.

**What does a yellow icon on Azure Status mean?**

A yellow icon means the service is experiencing degraded performance. It could be higher latency, increased error rates, or other non-critical issues. It is not a full outage.

**What does an orange icon on Azure Status mean?**

An orange icon indicates planned maintenance or an informational message. It is not an active problem but something you should be aware of, such as upcoming updates.

**How often is Azure Status updated?**

Azure Status is updated in real time as Microsoft's monitoring systems detect changes in service health. However, there can be a delay of a few minutes between an issue starting and the status page reflecting it.

**Can Azure Status be used for SLA credit claims?**

Yes. The timestamps and status information on Azure Status are considered the official record of service availability for SLA purposes. You should document the issue using Azure Status data if you plan to request credits.

## Summary

Azure Status is the official public health dashboard for all Microsoft Azure services and regions. It provides a real-time view of service availability using a simple color-coded system: green for healthy, yellow for degraded, red for outage, and orange for maintenance. Its primary value for IT professionals and certification candidates is as the first place to check during an incident, allowing teams to quickly distinguish between Azure-wide problems and local issues. This distinction saves time, reduces mean time to resolution, and supports proper incident communication. In the context of Azure exams, the most important concept is the difference between Azure Status (public, global, no login) and Azure Service Health (private, subscription-specific, requires login). Exam questions frequently test this distinction through tool selection and troubleshooting scenarios. Azure Status also serves as the official record for SLA credit claims, making it not just an operational tool but also a contractual one. For learners aiming for certifications like AZ-900 or AZ-104, mastering Azure Status means understanding its role in the monitoring ecosystem, knowing when to use it, and recognizing its limitations such as the lack of alerting capabilities. A simple memory hook: Public Status Page (Azure Status) vs. Private Health Portal (Azure Service Health). By building this foundational knowledge, you prepare yourself for both exam questions and real-world cloud operations.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/azure-status