Study guide
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring
Key Takeaways Explain This Topic AI
The Azure Monitor Agent collects nothing until a data collection rule is associated with the machine through a data collection rule association.
One machine can have multiple data collection rules, and their data sources are additive rather than mutually exclusive.
Windows security events are filtered with XPath queries and Linux syslog with facility and severity selections, which is the primary cost and noise control.
Ingestion-time transformations written in KQL can drop rows, redact columns, and route data before it is billed and stored.
VNet flow logs and Traffic Analytics supply network security telemetry that data collection rules do not gather from inside the guest.
Last updated: August 2026
Why This Object Exists
The retired Log Analytics agent was configured at the workspace level: every machine reporting to a workspace collected the same things. Azure Monitor Agent (AMA) inverts that with data collection rules (DCRs) — reusable objects that define what to collect and where to send it, bound to specific machines through data collection rule associations (DCRAs) .
The consequence you must internalize: installing the agent collects nothing. A machine with AMA installed and no DCR association produces no data at all. "The agent is installed but the workspace is empty" is almost always a missing association.
Anatomy of a Data Collection Rule
Element Purpose
Data sources What to collect: Windows event logs, Linux syslog, performance counters, IIS logs, custom text or JSON logs, Prometheus metrics
Streams The named schema each data source produces, such as Microsoft-SecurityEvent , Microsoft-Syslog , Microsoft-Perf
Destinations Where it goes: one or more Log Analytics workspaces, Azure Monitor Metrics, or a storage/event hub destination for supported streams
- Data flows Which stream goes to which destination, and which transformation applies
- Transformation ( transformKql ) A KQL statement applied at ingestion , before billing and storage
A data collection endpoint (DCE) is additionally required for scenarios such as custom logs, ingestion over Private Link, and some transformation configurations.
Associations are additive. Give a machine three DCRs — one for security events, one for performance counters, one for a custom application log — and it collects all three. This is how you build a shared security baseline DCR applied to every server, plus narrow DCRs for particular workloads, without duplicating configuration.
- Filtering: Where Cost and Signal Are Decided
- Windows events with XPath
Windows event collection is expressed as XPath queries , which lets you take exactly the event IDs you want: Security!*[System[(EventID=4624 or EventID=4625 or EventID=4672)]]
System!*[System[(Level=1 or Level=2 or Level=3)]]
The Sentinel Windows Security Events via AMA connector wraps this with named tiers — All Events , Common , Minimal , or Custom — where Common and Minimal are curated event-ID sets that Microsoft maintains for security value per gigabyte. Choosing "All Events" on a domain controller is the classic way to burn an ingestion budget in a week.
Linux syslog by facility and severity
Linux collection selects facilities (auth, authpriv, cron, daemon, kern, syslog, user, and the local facilities) and a minimum severity per facility. For security monitoring, auth and authpriv at info level and above carry most of the value; debug on every facility carries almost none at high volume.
Ingestion-time transformations
A transformation is a KQL fragment operating on the incoming stream, applied before the data is stored and billed: source
- | where EventID in (4624, 4625, 4672, 4720, 4726, 4732)
- | extend Account = tolower(Account)
- | project-away UnusedColumn
Use them to drop noisy rows , redact or hash sensitive columns before storage (a privacy control as much as a cost control), normalize values , and route different subsets to different destinations. Because they run at ingestion, a transformation that drops data is irreversible — validate against sample data first.
Collecting Network Security Telemetry
DCRs collect from inside the guest. Network security events largely come from elsewhere, and the exam expects you to combine them:
Source How it is collected What it shows
VNet flow logs (superseding NSG flow logs) Network Watcher writes to a storage account; Traffic Analytics processes into Log Analytics Allowed and denied 5-tuple flows, with threat intelligence enrichment
Azure Firewall logs Diagnostic settings to a workspace Application and network rule hits, IDPS alerts, threat intel matches
- Application Gateway / WAF logs Diagnostic settings Blocked requests, matched rules, request detail
- NVA and firewall syslog / CEF AMA on a Linux forwarder with a syslog/CEF DCR Third-party appliance events
- Guest network events AMA with a Windows event or syslog DCR Host-side connection and authentication events
Performance counters AMA performance data source in a DCR Network interface throughput, connection counts for anomaly baselining
The CEF pattern is the one to remember for third-party devices: appliances forward syslog to a Linux forwarder VM running AMA, and a DCR on that VM collects and parses the CEF stream into the workspace, where Sentinel analytics rules consume it.
Operational Checklist
Create a baseline security DCR (Windows Security Events at the Common tier, Linux auth/authpriv) and associate it with every server through a policy-driven assignment so new machines inherit it.
Add workload-specific DCRs rather than expanding the baseline.
Apply transformations to strip high-volume, low-value rows and to redact personal data before storage.
Enable diagnostic settings on network resources — they are not part of DCRs and are frequently forgotten.
Monitor the pipeline itself: agent health, DCR association coverage, and ingestion volume per table, with an alert for a sudden drop that would indicate collection has silently stopped.