Study guide

3.6 Azure Monitor and Service Health

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

3.6 Azure Monitor and Service Health

Key Takeaways Explain This Topic AI

Azure Monitor is the umbrella platform that collects, analyzes, and acts on telemetry (metrics and logs) from Azure resources, applications, and on-premises systems.

Metrics are lightweight numeric data stored for 93 days; logs are richer records stored in a Log Analytics workspace and queried with Kusto Query Language (KQL).

Application Insights is the Application Performance Management (APM) feature of Azure Monitor for live web apps; Log Analytics is where you run KQL queries.

Alert rules define WHAT triggers an alert; action groups define WHO is notified and HOW; severity runs from Sev 0 (Critical) to Sev 4 (Verbose).

Service Health has three layers: Azure Status (global, all customers), Service Health (personalized to your subscriptions), and Resource Health (one specific resource).

Last updated: October 2026

Quick Answer: Azure Monitor is the full-stack telemetry platform. Metrics = fast numbers (93-day retention). Logs = detailed records you query with Kusto Query Language (KQL) in Log Analytics . Application Insights = live app performance. Service Health answers "is Azure broken?" at three zoom levels.

Azure Monitor: the telemetry umbrella

Azure Monitor automatically collects two fundamental data types the moment a resource is created — you do not deploy an agent to get them. Knowing the metrics-versus-logs split is a key idea in this section.

Pillar What it is Retention How you read it

Metrics Lightweight, time-series numbers (CPU %, request count, disk IOPS) sampled at one-minute granularity 93 days by default Metrics Explorer, charts, autoscale rules

Logs Verbose, structured event records (traces, errors, sign-ins) Configurable, 30 days up to 2 years (longer with archive) KQL in a Log Analytics workspace

A useful mental model: a metric tells you a number crossed a line ; a log tells you the story of what happened . Autoscaling and most alerts fire on metrics because they are cheap and near-real-time; forensic troubleshooting uses logs.

  • Data sources Azure Monitor ingests
  • Application — your code's performance, via Application Insights
  • Guest OS — metrics/logs from inside a virtual machine (needs the Azure Monitor Agent)
  • Azure resource — platform metrics and resource (diagnostic) logs
  • Azure subscription — Activity Log and Service Health events
  • Azure tenant — Microsoft Entra ID (formerly Azure AD) audit and sign-in logs
  • Log Analytics and KQL

Log Analytics is the tool where you write queries against log data using Kusto Query Language (KQL) . You will not be asked to write KQL on AZ-900, but a classic distractor pairs the word "query logs" with Application Insights. The answer for querying log data is Log Analytics .

Application Insights

Application Insights is the Application Performance Management (APM) feature for live web apps and APIs. It surfaces:

  • Response times, failure rates, and exception stacks
  • Dependency tracking — calls out to SQL, REST APIs, and queues
  • Availability tests — synthetic ping tests from worldwide locations
  • Usage analytics — page views, sessions, and user funnels

Trap: Application Insights monitors your application code . Service Health monitors Microsoft's platform . If a question is about a slow checkout page, the answer is Application Insights, never Service Health.

Alerts: rule + action group

An Azure Monitor alert has two independent halves, and the separation matters.

  • Component Answers the question Example
  • Alert rule What condition fires it? CPU > 90% for 5 minutes
  • Action group Who is told and how ? Email the on-call team, SMS the manager, run a Logic App
  • Severity How urgent? Sev 0 (Critical) → Sev 4 (Verbose)

Three alert types map to the data they watch: metric alerts (a number crosses a threshold), log alerts (a KQL query returns a result), and activity log alerts (a management action such as "VM deleted" occurs). Action groups can automate remediation — calling an Azure Function or Logic App — not just send notifications.

Service Health: three levels of zoom

Azure Service Health tells you when Azure itself has a problem. Picture a zoom lens going from the whole planet down to one disk.

  • Layer Scope Personalized? Where
  • Azure Status Every Azure service, every region, all customers No status.azure.com (public)
  • Service Health Only the services and regions you use Yes Azure portal
  • Resource Health One specific resource (a single VM) Yes The resource's blade

Service Health (the middle layer) tracks four event kinds: service issues (active outages), planned maintenance , health advisories (action-required changes like a deprecation), and security advisories . You can configure Service Health alerts so an outage in your region emails the team automatically.

Resource Health reports four states: Available (healthy), Unavailable (a platform or non-platform event hit it), Degraded (reduced performance), and Unknown (no signal for 10+ minutes).

On the Exam: Memorize the zoom: Azure Status = global / everyone , Service Health = personalized to your subscriptions , Resource Health = one resource . If a question mentions a single named VM, the answer is Resource Health. If it mentions "any maintenance affecting my subscriptions," the answer is Service Health.

Worked example: choosing the right tool

Walk through a realistic decision tree, because AZ-900 phrases these as "a company wants to..." scenarios:

"We want to auto-scale a virtual machine scale set when average CPU exceeds 70%." — This is numeric and near-real-time, so it uses metrics plus an autoscale rule, not logs.

"We need to search six months of historical errors and correlate them across services." — Six months exceeds the 93-day metric window and needs rich querying, so the answer is logs in Log Analytics queried with KQL.

"Email the on-call engineer when a metric breaches a threshold." — An alert rule detects the breach; an action group sends the email.

"Is the slowdown our code or Microsoft's platform?" — Check Application Insights for the app side and Service Health / Resource Health for the platform side.

Notice that metrics, logs, alerts, Application Insights, and Service Health each own a distinct job; the exam rewards you for picking the narrowest tool that fully answers the scenario.

Common AZ-900 traps in this section

"Query logs" always maps to Log Analytics / KQL , never to Application Insights (which generates app telemetry but is not the generic log-query tool).

Service Health is not Azure Monitor. Service Health is about Microsoft's platform outages; Azure Monitor is about your resources and apps.

Metrics ≠ logs. Metrics are numbers kept 93 days; logs are records kept in a workspace for up to two years.

Action group vs alert rule. The rule is the condition ; the group is the response . Questions often hand you one and ask for the other.

The July 20, 2026 AZ-900 outline lists Azure Monitor and Azure Service Health as separate monitoring tools, so learn this split well.