Study guide

10.1 Disk Encryption

Microsoft Certified: Cloud and AI Security Engineer Associate SC-500

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Skills Measured & Weightings 1.3 Study Path, Prerequisites & Exam Strategy

2 Microsoft Entra ID Secure Access

2.1 Privileged Identity Management (PIM) 2.2 Conditional Access Policies 2.3 MFA and Passwordless Authentication 2.4 Application Identities, OAuth Consent & Managed Identities

3 Azure Key Vault Secrets and Keys

3.1 Deploy and Configure Key Vault 3.2 Access Control and Firewall for Key Vault 3.3 Keys, Secrets, Certificates & Defender for Key Vault

4 Governance, Policy & RBAC

4.1 Azure Policy for Security Controls 4.2 Defender for Cloud Compliance & Security Standards 4.3 Resource Locks and Azure RBAC 4.4 Custom Roles, Overprivileged Access, Backup & IaC Security

5 Secure Storage Accounts

5.1 Storage Account Security Fundamentals 5.2 Storage Firewalls and Access Policies 5.3 Defender for Storage

6 Secure Databases

6.1 Azure SQL Platform Security 6.2 Database Auditing 6.3 Defender for Databases

7 Network Security Groups & Virtual Network Manager

7.1 Network Security Groups and Application Security Groups 7.2 Azure Virtual Network Manager Security Admin Rules 7.3 Virtual WAN and VPN Security

8 Private Access, Private Link & Azure Firewall

8.1 Microsoft Entra Private Access 8.2 Private Endpoints and Private Link 8.3 Azure Firewall 8.4 Network Watcher Diagnostics and Effective Rules

9 Security for AI Workloads

9.1 Purview DSPM for AI and Data Overexposure 9.2 Copilot Studio Protection and Agent Management 9.3 Microsoft Entra Agent ID Security 9.4 Defender for AI, Foundry Guardrails & AI Gateway

10 Secure Servers and Virtual Machines

10.1 Disk Encryption 10.2 Azure Bastion and JIT VM Access 10.3 Azure Arc and Defender for Servers 10.4 Trusted Launch, VM Security Features & Machine Configuration

11 Application Platform Security

11.1 Containers: AKS, ACR, ACI, Container Apps & Defender for Containers 11.2 Azure Functions and Logic Apps Security 11.3 Azure App Service Security 11.4 Web Application Firewall and API Management Protection

12 Defender for Cloud Security Posture

12.1 Defender CSPM and Secure Score 12.2 Workload Protection Plans and Multicloud Connectors 12.3 Vulnerability Management and Defender EASM

13 Microsoft Sentinel Activity and Event Collection

13.1 Workspaces, Roles & Content Hub 13.2 Data Connectors, Syslog/CEF & Windows Event Collection 13.3 Custom Tables, Retention & Purview Audit 13.4 Automation Rules and Playbooks

14 Microsoft Security Copilot & Final Review

14.1 Microsoft Security Copilot Workspaces and Roles 14.2 Plugins and Security Agents 14.3 Final Review and Exam-Day Strategy

10.1 Disk Encryption

Key Takeaways Explain This Topic AI

Server-side encryption (SSE) is always on for Azure managed OS and data disks; use platform-managed keys by default or customer-managed keys via a Disk Encryption Set and Key Vault.

Encryption at host extends SSE end-to-end to temp disks, caches, and compute-to-storage data paths without using the guest CPU—Microsoft’s preferred path for new VMs as ADE retires.

Azure Disk Encryption (ADE) encrypts inside the guest with BitLocker or dm-crypt and stores keys in Key Vault, but it is scheduled for retirement on September 15, 2028 and is mutually exclusive with encryption at host.

Confidential disk encryption on confidential VMs binds OS-disk keys to the TPM so protected content is available only inside the attested guest; combine with encryption at host for other disks when needed.

Exam stems that ask which encryption covers temp disks and caches, avoids guest CPU cost, or meets Defender recommendations point to encryption at host—not SSE alone and not ADE for greenfield designs.

Last updated: July 2026

Why Disk Encryption Matters on SC-500

Under Secure compute , the SC-500 blueprint explicitly measures implement and configure disk encryption . Encryption is not one switch—Azure offers several mechanisms that protect different layers of the I/O path. Exam questions almost always test which layer you need , what is encrypted by default , and how Key Vault fits , not the click-path to enable a checkbox.

Treat encryption as part of a layered server security model alongside Bastion/JIT access, Defender for Servers, Trusted Launch, and Machine Configuration (later in this chapter). Disk encryption protects data at rest and in transit between compute and storage; it does not replace identity, network, or runtime threat protection.

The Four Encryption Options (Exam Map)

Microsoft documents four primary options for managed disks and VMs. Memorize this comparison table—it is the backbone of almost every SC-500 encryption stem.

Capability Azure Disk Storage SSE (encryption at rest) Encryption at host Azure Disk Encryption (ADE) Confidential disk encryption

Where it runs Storage clusters Azure VM host Inside guest (BitLocker / dm-crypt) Guest TPM-bound keys on confidential VM sizes

OS & data disks at rest Yes (always) Yes Yes Yes (OS disk; design for confidential workloads)

Temp disks & caches No Yes (temp disks with platform-managed keys) Yes Temp support evolving; often pair with encryption at host for other disks

  • Data flow compute ↔ storage encrypted No Yes Yes Yes
  • Uses guest VM CPU No No Yes Yes for guest-side work

Customer-managed keys Yes via Disk Encryption Set (DES) + Key Vault / Managed HSM Yes when disks use DES Yes via Key Vault secrets/KEKs Yes via DES where supported

Defender “healthy” for modern recommendations Incomplete alone for temp/cache guidance Preferred / healthy for encryption-at-host recommendations Historically healthy for ADE recommendations; migrating away N/A for some ADE-style recommendations

Strategic posture (2026) Default baseline Preferred for new VMs Retiring September 15, 2028 Confidential computing / high-assurance isolation

Mental model for the exam

SSE = “Microsoft encrypts disks when they land on storage” (always true for managed disks).

Encryption at host = “Encrypt earlier—on the host—so temp disks, caches, and the path to storage are covered without taxing the guest.”

ADE = “Encrypt inside the OS like a traditional BitLocker/dm-crypt rollout, with Key Vault holding keys.”

Confidential disk encryption = “Keys are bound so even the host fabric cannot casually read the confidential OS disk content.”

Server-Side Encryption (SSE): Platform-Managed vs Customer-Managed Keys

Server-side encryption of Azure managed disks (also called encryption-at-rest or Azure Storage encryption on disks) is always enabled . You cannot turn it off. By default, Microsoft uses platform-managed keys (PMK) —Azure generates, stores, and rotates the encryption keys.

When compliance or policy requires customer control of keys:

Create a key in Azure Key Vault or Azure Key Vault Managed HSM .

Create a Disk Encryption Set (DES) that references that key.

Associate the DES with OS/data disks (or set it as the default for a subscription/resource group via policy).

Grant the DES’s managed identity permission to use the key ( wrap / unwrap and related key operations).

Exam traps for SSE + CMK:

CMK for disks uses a Disk Encryption Set , not the ADE “enable disk encryption” wizard.

Soft-delete and purge protection on Key Vault are operational best practices for CMK durability; losing key access can make disks unreadable.

SSE alone does not encrypt temporary disks or disk caches —if the stem requires those, you need encryption at host or ADE (legacy).

Encryption at Host: Preferred End-to-End Path

Encryption at host is a VM-level setting. When enabled, the Azure host encrypts data for temp disks and OS/data disk caches at rest on that host, and data remains encrypted as it flows to Azure Storage. It improves on default SSE without consuming guest CPU or relying on BitLocker/dm-crypt inside the VM.

Key exam facts:

Mutual exclusion with ADE: You cannot enable encryption at host on VMs that currently have (or historically had) ADE enabled, and you cannot enable ADE on disks that already use encryption at host. Migration requires new disks/VMs—not an in-place flip.

Scale sets: Enabling on a scale set encrypts new instances automatically; existing instances typically need deallocate/reallocate.

Ultra Disk / Premium SSD v2: Additional restrictions apply; always check size/region support before answering “enable everywhere.”

Performance: No guest CPU tax—prefer over ADE when the goal is performance-neutral encryption of temp/cache paths.

Retirement guidance: Microsoft directs new deployments to encryption at host (or confidential VM OS disk encryption) instead of ADE.

Scenario: A regulated app uses Premium SSDs and a temporary disk for staging. Auditors require encryption of temp data and caches, and the app team refuses guest-level encryption agents that burn CPU. Answer: encryption at host (optionally with SSE + CMK via DES on the managed disks).

Azure Disk Encryption (ADE) and Key Vault Integration

Azure Disk Encryption encrypts the OS and data volumes inside the guest :

  • Windows: BitLocker
  • Linux: dm-crypt

ADE integrates with Azure Key Vault to store disk encryption secrets (and optionally a key encryption key / KEK that wraps those secrets). Classic exam setup steps:

Key Vault in the same subscription/region model the workload expects, with appropriate access policies or RBAC for the ADE identity model in use.

Enable ADE on the VM (portal, CLI, PowerShell, or ARM/Bicep).

Confirm volumes show encrypted and that Key Vault holds the BEK/KEK material.

Understand backup/restore and VM extension health—ADE relies on guest extensions and successful unlock at boot.

Critical lifecycle fact for SC-500: ADE is scheduled for retirement on September 15, 2028 . Until then it works; after that date, ADE-enabled workloads may fail to unlock disks after reboot. Microsoft expects migration to encryption at host (or confidential VM disk encryption for confidential sizes). Exam questions may still describe ADE for legacy scenarios, but greenfield designs should not recommend ADE.

When ADE still appears in stems:

Existing VMs already encrypted with BitLocker/dm-crypt via ADE.

A requirement phrased as “guest OS volume encryption with keys in Key Vault” without mentioning host or confidential VMs.

Defender recommendations that historically flagged missing ADE—modern recommendations also recognize encryption at host.

Confidential VMs and Confidential Disk Encryption (Overview)

Confidential VMs (for example DCasv5/ECasv5-class sizes and later families) use hardware-backed trusted execution environments so the guest can protect data in use , not only at rest. Confidential disk encryption binds OS disk encryption keys to the VM’s TPM and releases them only to attested code paths, reducing host/operator visibility into protected disk content.

Exam-level distinctions:

Confidential disk encryption is not the same as ordinary SSE or encryption at host—it targets confidential computing threat models.

You may still use encryption at host for additional disks on a confidential VM.

Choosing security type = Confidential at VM create time is a different decision from Trusted launch (covered in section 10.4).

If the stem says “protect data from the cloud operator / host administrator while processing,” lean confidential computing—not ADE.

Decision Tree: Which Encryption Does the Exam Want?

Use this quick map:

  • Stem language Prefer
  • Default encryption of managed disks; no extra config SSE with platform-managed keys
  • Customer controls keys for disks at rest SSE + CMK via Disk Encryption Set + Key Vault/Managed HSM
  • Temp disks, caches, end-to-end host encryption; no guest CPU Encryption at host
  • Legacy BitLocker/dm-crypt inside the VM; keys in Key Vault ADE (know retirement date)
  • Highest isolation; TPM-bound OS disk on confidential sizes Confidential disk encryption
  • Migrate off ADE before 2028 Encryption at host (new disks/VMs)
  • Combined exam traps

Trap: “Managed disks are unencrypted unless you enable ADE.” False —SSE is always on.

Trap: “CMK for disks is configured the same way as storage-account encryption keys.” Disks use Disk Encryption Sets ; storage accounts have their own encryption settings.

Trap: “Enable both ADE and encryption at host for defense in depth.” Invalid —they are mutually exclusive.

Trap: “SSE alone meets a requirement to encrypt temporary disks.” False —need encryption at host or ADE.

Operations and Policy Alignment

Security engineers implement encryption with Azure Policy and Defender recommendations:

Deploy deny/deployIfNotExists policies that require encryption at host or DES-backed CMK on new VMs/disks.

Watch Defender for Cloud recommendations that flag missing encryption at host or missing ADE/EncryptionAtHost for Windows/Linux VMs.

Coordinate Key Vault network rules, private endpoints, and RBAC so disk encryption identities can still unwrap keys during boot and rekey operations.

Treat key rotation as a joint Key Vault + DES + VM maintenance exercise—not a secret change in isolation.

Disk encryption is necessary but not sufficient: pair it with private management access (Bastion/JIT), Defender for Servers, Trusted Launch, and Machine Configuration baselines covered next.