Study guide
15.1 Azure Monitor Architecture, AMA & Data Collection Rules
Microsoft Certified: Azure DevOps Engineer Expert AZ-400
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Flow of Work, Traceability & Work Tracking
1.1 Flow of Work, GitHub Flow & Feedback Cycles 1.2 Work Tracking with Azure Boards & GitHub Projects 1.3 End-to-End DevOps Traceability & Quality Tracking
2 Chapter 2: DevOps Metrics, Dashboards & Team Collaboration
2.1 DORA Metrics, Flow Metrics & Dashboard Design 2.2 Lifecycle Metrics Across the Six DevOps Phases 2.3 Work Item Queries, WIQL Charts & Analytics 2.4 Project Documentation: Wikis, Mermaid Diagrams & Release Notes 2.5 Webhooks, Service Hooks & Microsoft Teams ChatOps
3 Chapter 3: Git Branching Strategies & Pull Request Workflows
3.1 Git Branching Models & Strategy Design 3.2 Pull Request Workflows & Merge Strategies 3.3 Branch Policies, Quality Gates & Compliance Restrictions
4 Chapter 4: Repository Management, Optimization & Git Data Operations
4.1 Git LFS Architecture & .gitattributes Tracking 4.2 LFS History Migration, git-fat & File Locking 4.3 Git Repository Scaling, Scalar & Monorepo Governance 4.4 Repository Permissions & Git Tag Governance 4.5 Git Data Recovery & Sensitive-Data Scrubbing
5 Chapter 5: Package Management & Dependency Versioning
5.1 Selecting Package Tools: Azure Artifacts vs. GitHub Packages 5.2 Feed Scoping, Upstream Sources & Pipeline Authentication 5.3 Package Views, Immutability & Quality Promotion 5.4 Dependency Versioning: SemVer, CalVer & Automated Versioning 5.5 Pipeline Artifact Versioning & Artifact Storage Strategy
6 Chapter 6: Pipeline Infrastructure, Agents & Integration
6.1 Selecting a CI/CD Solution: Azure Pipelines vs. GitHub Actions 6.2 GitHub-Azure Pipelines Integration & Hybrid Migration 6.3 Hosted vs. Self-Hosted Agents & Runners 6.4 VMSS Elastic Pools, Container Jobs & Agent Governance 6.5 Pipeline Triggers, Filters & Concurrency Management
7 Chapter 7: YAML Pipeline Architecture & Reusable Elements
7.1 YAML Pipeline Anatomy: Stages, Jobs, Steps & Workspaces 7.2 Job Execution Order: DAG Dependencies, Parallelism & Conditions 7.3 Reusable Elements: Templates, Parameters & Variables 7.4 Variable Groups, Secret Variables & Key Vault Linking 7.5 YAML Environments, Checks & Deployment Approvals
8 Chapter 8: Testing Strategy, Quality Gates & Code Coverage
8.1 Test Strategy Design: Local, Unit & Integration Testing 8.2 Load, Stress & Performance Testing in Pipelines 8.3 Test Execution Tasks, Agents & Results Integration 8.4 Code Coverage Analysis & SonarQube Integration 8.5 Quality Gates, Release Gates & Governance Checks
9 Chapter 9: Modern Deployment Strategies & Zero-Downtime Delivery
9.1 Progressive Delivery: Blue-Green, Canary & Ring Deployments 9.2 Minimizing Downtime: Deployment Slots & Rolling Updates 9.3 Feature Flags with Azure App Configuration & Feature Manager 9.4 Designing the High-Priority Hotfix Path 9.5 Ordered Dependency Deployments, Resiliency & Rollback
10 Chapter 10: Artifact Deployment & Database DevOps
10.1 Containerized Application Delivery: ACR, AKS & Container Apps 10.2 Binary, Web App, Function & Scripted Deployments 10.3 Database DevOps: State-Based & Migration-Based Strategies
11 Chapter 11: Infrastructure as Code (IaC) & Azure Deployment Environments
11.1 Infrastructure as Code Strategy: Bicep, ARM & Terraform 11.2 Desired State Configuration & Azure Machine Configuration 11.3 Azure Deployment Environments (ADE) & Developer Self-Service
12 Chapter 12: Pipeline Maintenance, Health & Modernization
12.1 Pipeline Health, Flaky Tests & Reliability Engineering 12.2 Pipeline Optimization: Caching, Slicing & Concurrency 12.3 Artifact & Build Retention Governance 12.4 Modernizing CI/CD: Classic to YAML Migration
13 Chapter 13: Authentication, Authorization & Identity Governance
13.1 Microsoft Entra Service Principals & Managed Identities 13.2 Service Connections, Workload Identity & Personal Access Tokens 13.3 Azure DevOps Projects, Teams & Permission Evaluation 13.4 Access Levels, GitHub Roles & Outside Collaborators
14 Chapter 14: Secrets Management, Sensitive Data & DevSecOps Scanning
14.1 Azure Key Vault, Secret Variables & Secretless CI/CD 14.2 Security Scanning Strategy, GHAS & Secret Scanning 14.3 CodeQL SAST in Pipelines and Containers 14.4 Software Supply Chain, Container Scanning & Cloud Defender
15 Chapter 15: Telemetry Collection, Azure Monitor & Alerting
15.1 Azure Monitor Architecture, AMA & Data Collection Rules 15.2 Application Insights & Specialized Azure Monitor Insights 15.3 Alerting Rules, Action Groups & GitHub Repository Insights
16 Chapter 16: Telemetry Analysis, Distributed Tracing & SRE Practices
16.1 Distributed Tracing, Application Map & Exception Triage 16.2 KQL Log Analytics, SRE Observability & Error Budgets
15.1 Azure Monitor Architecture, AMA & Data Collection Rules
Key Takeaways Explain This Topic AI
Metrics are a time-series store with sub-minute latency and 93-day non-configurable retention; Logs are a Kusto store with 30 to 730 days interactive retention and up to 12 years of archive.
Choose Metrics for autoscale triggers and sub-minute alerting; choose Logs for correlation, string parsing and multi-resource analysis.
A data collection rule declares what the Azure Monitor Agent collects and where it lands, and one agent can be associated with several rules.
Ingestion-time transformations in a data collection rule drop unwanted rows at the boundary, which is the sanctioned way to control Log Analytics ingestion cost.
Diagnostic settings route platform resource logs and metrics to Log Analytics, a storage account, Event Hubs or a partner destination, and each resource can have several.
Last updated: September 2026
15.1 Azure Monitor Architecture, AMA & Data Collection Rules
Modern DevOps practices rely fundamentally on continuous observability to detect failures before customers do, drive automated canary health gates, and maintain high system reliability. In Microsoft Azure, Azure Monitor serves as the central observability platform that ingests, aggregates, and analyzes telemetry from infrastructure, platforms, and application runtimes.
For the AZ-400 exam, candidates must master the telemetry collection architecture of Azure Monitor, differentiate between time-series metrics and structured log data, navigate the transition to the Azure Monitor Agent (AMA) and Data Collection Rules (DCRs) , instrument applications via Application Insights (contrasting SDK versus codeless approaches), leverage specialized container and virtual machine insights, and configure diagnostic settings to route telemetry across enterprise storage and analytics destinations.
1. Azure Monitor Core Architecture: Metrics vs. Logs
Azure Monitor ingests telemetry from applications, operating systems, cloud resources, and subscription activity. At the core of the Azure Monitor data platform sit two distinct, complementary data stores: Metrics and Logs . Understanding their architectural differences is essential for designing resilient monitoring, alerting, and auto-scaling strategies. [Telemetry Sources]
- (Applications, VMs, PaaS Services, Subscriptions, Arc)
- │
- ┌───────────────────┴───────────────────┐
- ▼ ▼
- [Azure Monitor Metrics] [Azure Monitor Logs]
- Time-series numerical data • Structured records & text
- In-memory time-series store • Log Analytics Workspace (Kusto engine)
- Real-time, sub-minute latency • Rich querying via KQL
- 93-day standard retention • 30 to 730 days (Archive to 12 years)
- Fast alerts & autoscale triggers • Deep troubleshooting & audits
- Architectural Comparison
Dimension Azure Monitor Metrics Azure Monitor Logs (Log Analytics)
Data Structure Lightweight, numerical time-series values with fixed timestamp, metric name, and key-value dimensions Structured records organized into tables with typed columns (strings, dynamic JSON, integers, datetimes)
Storage Engine Proprietary in-memory time-series database optimized for high-speed mathematical aggregation Azure Data Explorer (ADX / Kusto) distributed columnar analytical engine
Ingestion Latency Near real-time (typically under 1 minute from emission to availability) Moderate latency (typically 1 to 3 minutes for ingestion pipeline, schema parsing, and indexing)
Query Mechanism Azure Metrics Explorer, REST API, or metric alert rule expressions Kusto Query Language (KQL) supporting joins, regex parsing, machine learning plugins, and statistical aggregations
Default Retention 93 days (standard, non-configurable) Configurable per workspace/table: 30 to 730 days interactive; up to 12 years in low-cost Archive tier
Primary DevOps Use Cases Real-time metric alerts, Azure Monitor Autoscale rules, performance counters, live operational dashboards Root-cause analysis, security incident investigations (Microsoft Sentinel), CI/CD release gate evaluations, compliance audits
Key Exam Rule: When to Use Which
Choose Metrics when you need sub-minute alerting, automated scaling triggers (e.g., scale out Virtual Machine Scale Sets when CPU > 75%), or lightweight real-time dashboarding.
Choose Logs when you need complex correlation across services, regex parsing of error messages, cross-table joins (e.g., joining application exceptions with Kubernetes pod restarts), or long-term analytical queries using KQL.
2. Data Collection Evolution: Azure Monitor Agent (AMA) & Data Collection Rules (DCRs)
Historically, Azure relied on multiple disparate agents to collect operating system and infrastructure telemetry: the legacy Log Analytics Agent (also known as OMS or MMA - Microsoft Monitoring Agent), the Azure Diagnostic Extension (WAD for Windows, LAD for Linux), and the Telegraf agent .
Important
The legacy Log Analytics agent (MMA/OMS) was officially deprecated and retired on August 31, 2024 . For the AZ-400 exam, any architecture referencing MMA or OMS is obsolete. The only supported, modern standard is the Azure Monitor Agent (AMA) governed by Data Collection Rules (DCRs) .
Azure Monitor Agent (AMA) Capabilities
The Azure Monitor Agent unifies OS-level telemetry collection into a single, secure, performant daemon supporting Windows and Linux across:
Azure Virtual Machines and Virtual Machine Scale Sets (VMSS) .
Hybrid and Multicloud Servers connected through Azure Arc .
Azure Kubernetes Service (AKS) nodes.
Key architectural improvements include:
Managed Identity Authentication : AMA uses system-assigned or user-assigned Managed Identities to authenticate securely with Azure Monitor, eliminating hardcoded workspace IDs and shared primary keys.
Multi-Homing : A single VM running AMA can stream logs and performance data to multiple Log Analytics workspaces across different subscriptions or tenants simultaneously.
Network Isolation : Operates seamlessly over Azure Private Link using Azure Monitor Private Link Scopes (AMPLS).
Data Collection Rules (DCRs) and Data Collection Endpoints (DCEs)
Data Collection Rules (DCRs) are cloud-native Azure Resource Manager (ARM) resources that decouple data collection logic from the host operating system. Instead of configuring agents locally via XML files or portal toggles, a DCR centrally defines:
Data Sources : Which performance counters, Windows Event Logs (System, Application, Security), Linux syslog facilities, or custom log text files to gather.
Stream Transformations (KQL Filtering at Ingestion) : DCRs allow engineers to write KQL transformations that filter, mask, or enrich records before they are ingested into the workspace.
Destinations : Where to send the collected streams—such as one or more Log Analytics Workspaces, Azure Monitor Metrics, or Event Hubs. [Virtual Machine / Azure Arc Host]
- │ (Runs Azure Monitor Agent - AMA)
- ▼
- [Data Collection Rule - DCR]
- │ 1. Collect: Windows Security Events
- │ 2. Transform: source | where EventID == 4625 (Drop successful 4624 logons!)
- ▼
- [Log Analytics Workspace] ──► [Cost Savings: 80% reduction in unneeded ingestion volume]
- Ingestion-Time Filtering for Cost Optimization (Top Exam Scenario)
A classic AZ-400 challenge involves uncontrolled Log Analytics ingestion costs caused by high-volume Windows Security events. By default, collecting the Windows Security log ingests millions of informational Event ID 4624 (Successful Logon) events.
- With DCR stream transformations, DevOps engineers configure a KQL filter directly in the DCR: {
- "properties": {
- "streamDeclarations": {
- "Custom-SecurityStream": {
- "columns": [
- { "name": "TimeGenerated", "type": "datetime" },
- { "name": "EventID", "type": "int" },
- { "name": "Account", "type": "string" },
- { "name": "Message", "type": "string" }
- ]
- }
- },
- "dataFlows": [
- {
- "streams": [ "Microsoft-SecurityEvent" ],
- "destinations": [ "la-workspace-prod" ],
- "transformKql": "source | where EventID == 4625",
- "outputStream": "Microsoft-SecurityEvent"
- }
- ]
- }
- }
This ensures only failed logon attempts (Event ID 4625) are sent over the network and ingested, saving thousands of dollars in monthly log ingestion fees.
Data Collection Endpoints (DCEs)
A Data Collection Endpoint (DCE) is required when using AMA with Azure Private Link (private DNS zones) or when collecting custom log files from virtual machines. The DCE provides the dedicated HTTPS ingestion URL that AMA contacts to pull configuration and transmit data payloads. # Azure CLI: Associate a Data Collection Rule with an Azure VM
- az monitor data-collection rule association create \
- -name "vm-security-dcr-assoc" \
--resource "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-prod/providers/Microsoft.Compute/virtualMachines/vm-payment-01" \
--rule-id "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-prod/providers/Microsoft.Insights/dataCollectionRules/dcr-security-hardened"