Study guide

14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs

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

14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs

Key Takeaways Explain This Topic AI

Agentless machine scanning snapshots the VM's root and data disks and analyses them out of band, so it needs no agent, no network access, and imposes no performance cost on the workload.

Agentless scanning is delivered by Defender CSPM and Defender for Servers Plan 2, is on by default when either plan is enabled, and runs once every 24 hours on a fixed schedule.

Only running VMs are scanned — a machine that is deallocated when the scan runs is skipped — and coverage stops at 4 TB of total disk, 14 disks, or an unsupported disk type such as UltraSSD_LRS.

Microsoft Defender Vulnerability Management is the built-in vulnerability assessment solution in Defender for Cloud, replacing the earlier Qualys-based scanner, with premium capabilities such as security baselines assessment gated behind Defender for Servers Plan 2.

Agentless scanning also delivers software inventory, secret scanning, malware scanning, and EDR configuration assessment, but cannot replace the real-time detection and response an endpoint agent provides.

Last updated: August 2026

Two Ways to See Inside a Machine

Approach Mechanism Strengths Limits

Agent-based (Defender for Endpoint sensor) Software running in the OS Real-time behavioural detection, response actions, live response Requires deployment, upgrades, and OS support; can be disabled by an attacker with local admin

Agentless machine scanning Snapshot of the managed disk analysed in a Microsoft-managed environment No agent, no network access needed, no performance impact, covers machines the agent never reached Point-in-time; no runtime detection or response

They are complementary. Agentless scanning solves coverage — it finds the machines your deployment tooling missed. The agent solves detection and response . A serious environment runs both; the exam expects you to say which one a given requirement needs.

How Agentless Machine Scanning Works

Defender for Cloud takes a snapshot of the machine's root and data disks using its own read-only permissions on the subscription.

The copied snapshot stays in the same region as the VM and is analysed out of band in a regional, volatile, isolated scanning environment — nothing executes on the workload itself.

Once the metadata is extracted, the copied snapshot is deleted immediately ; scan data is not retained longer than the few minutes needed to collect it.

Results are written back as Defender for Cloud recommendations, security findings, and cloud security graph data, consolidated with agent-based results.

Enablement: agentless scanning is a setting on the Defender CSPM plan and on Defender for Servers Plan 2 , and it is on by default when either plan is enabled . Turning it on for one plan turns it on for both. You can enable or disable scanning as a whole, but you cannot switch off individual scan types . It also covers AWS EC2 and GCP compute instances reached through the multicloud connectors described earlier.

Scheduling: scans run once every 24 hours on a fixed schedule , and only running VMs are scanned — a machine that is deallocated when the scan window comes round is simply skipped. That single fact explains most "why is this VM missing from findings" scenarios.

What agentless scanning produces:

  • Output Value
  • Vulnerability findings CVEs on installed OS and application packages, via Defender Vulnerability Management
  • Software inventory Full list of installed applications and versions, queryable in Inventory

Secret scanning Plaintext SSH keys, cloud credentials, and connection strings found on disk — a direct lateral-movement finding

Malware scanning Detection of known malicious files using Microsoft Defender Antivirus signatures (Defender for Servers Plan 2)

EDR configuration assessment Whether the machine runs an endpoint detection and response solution at all, and whether its Defender for Endpoint settings are correct

Kubernetes node coverage Vulnerability assessment and malware scanning for VMs running as Kubernetes nodes, in commercial clouds

The secret scanning output is the one security teams underestimate. Finding an unprotected private key on a web server disk turns an abstract "vulnerable machine" recommendation into a concrete attack path: internet-exposed VM → SSH key on disk → lateral movement to a database server. Defender CSPM's attack path analysis renders exactly that chain. The EDR configuration assessment is the quiet complement: it finds the machines where the agent is absent or misconfigured, which is the gap agentless scanning exists to close.

Requirements, Limits, and Permissions

Coverage claims fail on the details, so know the boundaries:

Area What is supported

Azure disks Maximum 4 TB total across all disks (above that, only the OS disk is scanned, and only if it is under 4 TB); maximum 14 disks ; virtual machine scale sets in Flexible orchestration

Encryption Unencrypted disks, platform-managed keys (PMK), and customer-managed keys (CMK)

AWS / GCP EC2 and Auto Scale instances (PMK and CMK); GCP compute instances and instance groups with Google-managed keys or CMEK

Unsupported disk types UltraSSD_LRS , PremiumV2_LRS , and AKS ephemeral OS disks — if any disk on the VM matches, the whole VM is skipped

Unsupported file systems UFS, ReFS, and ZFS, plus OracleASM, DRBD, and Linux_Raid_Member layouts and DM_Verity_Hash /swap volumes

Unsupported resources Databricks VMs

Permissions are worth a moment because they show why this is safe to enable. In Azure, the built-in VM scanner operator role grants only read-level disk and VM actions — Microsoft.Compute/disks/read , disks/beginGetAccess/action , and the VM and scale-set read actions — and Defender for Cloud adds them automatically when you enable scanning. Extending coverage to CMK-encrypted disks requires granting the Microsoft Defender for Cloud Servers Scanner Resource Provider Key Get, Key Wrap, and Key Unwrap on the relevant key vaults, or the Key Vault Crypto Service Encryption User role on vaults that use Azure RBAC. On AWS the equivalent is the VmScanner role in the CloudFormation stack; on GCP, a custom role plus the CMEK encrypter/decrypter role.

Microsoft Defender Vulnerability Management

Microsoft Defender Vulnerability Management (MDVM) is the integrated vulnerability assessment solution in Defender for Cloud, and it has replaced the older Qualys-powered built-in scanner. It works both through the Defender for Endpoint agent and through agentless scanning.

Core capabilities , available with Defender for Servers Plan 1 and Plan 2:

Continuous vulnerability discovery and assessment across OS and applications.

Risk-based prioritization that weighs exploit availability, active threat campaigns, and business context rather than raw CVSS.

Findings surfaced through the "Machines should have vulnerability findings resolved" recommendation, with per-machine and per-CVE drill-down.

Integration into Secure Score and attack path analysis.

Premium capabilities , included with Defender for Servers Plan 2 :

  • Capability What it adds
  • Security baselines assessment Measures machines against industry baselines (for example CIS) and reports drift
  • Browser extensions inventory Enumerates installed extensions and their risk
  • Digital certificate assessment Finds expiring, weak, or untrusted certificates on machines
  • Network share analysis Identifies internally exposed shares with weak configuration
  • Blocking vulnerable applications Prevents execution of applications with known critical vulnerabilities
  • Choosing the Right Answer on Exam Scenarios

"We must assess every VM, including ones where agent deployment repeatedly fails" → agentless scanning .

"We need to detect a live process injection and isolate the machine" → Defender for Endpoint via Defender for Servers ; agentless cannot do this.

"Find hardcoded credentials sitting on server disks" → agentless secret scanning .

"Tell us which servers have no EDR solution installed at all" → agentless EDR configuration assessment .

"Report drift from a CIS baseline on Windows Server" → security baselines assessment (Defender for Servers Plan 2) , or machine configuration where the requirement is Azure Policy compliance rather than vulnerability reporting.

"Block applications with critical CVEs from running" → Defender for Servers Plan 2 premium MDVM .

"Assess a container image before it is deployed" → Defender for Containers registry scanning, not machine scanning.

Finally, remember the operational point that makes any of this useful: findings must be exported and owned. Route vulnerability recommendations through continuous export to Log Analytics, apply governance rules to assign owners and due dates, and alert in Sentinel when a machine with an internet-exposed public IP acquires a critical, exploitable finding.