Azure Disk Encryption for IaaS VMs FAQ
This article provides answers to frequently asked questions (FAQ) about Azure Disk Encryption for Windows and Linux IaaS VMs. For more information about this service, see Azure Disk Encryption for Windows and Linux IaaS VMs.
Where is Azure Disk Encryption in general availability (GA)?
Azure Disk Encryption for Windows and Linux IaaS VMs is in general availability in all Azure public regions.
What user experiences are available with Azure Disk Encryption?
Azure Disk Encryption GA supports Azure Resource Manager templates, Azure PowerShell, and Azure CLI. The different user experiences give you flexibility. You have three different options for enabling disk encryption for your IaaS VMs. For more information on the user experience and step-by-step guidance available in Azure Disk Encryption, see Enable Azure Disk Encryption for Windows and Enable Azure Disk Encryption for Linux.
How much does Azure Disk Encryption cost?
There's no charge for encrypting VM disks with Azure Disk Encryption but there are charges associated with the use of Azure Key Vault. For more information on Azure Key Vault costs, see the Key Vault pricing page.
Which virtual machine tiers does Azure Disk Encryption support?
Azure Disk Encryption is available on standard tier VMs including A, D, DS, G, GS, and F series IaaS VMs. It's also available for VMs with premium storage. It isn't available on basic tier VMs.
What Linux distributions does Azure Disk Encryption support?
Azure Disk Encryption is supported on a subset of the Azure-endorsed Linux distributions, which is itself a subset of all Linux server possible distributions.
Linux server distributions that are not endorsed by Azure do not support Azure Disk Encryption and, of those that are endorsed, only the following distributions and versions support Azure Disk Encryption:
|Linux distribution||Version||Volume type supported for encryption|
|Ubuntu||18.04||OS and data disk|
|Ubuntu||16.04||OS and data disk|
with Azure tuned kernel updated to 4.15 or later
|OS and data disk|
|RHEL||7.6||OS and data disk*|
|RHEL||7.5||OS and data disk*|
|RHEL||7.4||OS and data disk*|
|RHEL||7.3||OS and data disk*|
|RHEL||7.2||OS and data disk*|
|CentOS||7.5||OS and data disk|
|CentOS||7.4||OS and data disk|
|CentOS||7.3||OS and data disk|
|CentOS||7.2n||OS and data disk|
|CentOS||6.8||OS and data disk|
New ADE implementation is supported for RHEL OS and data disk for RHEL7 Pay-As-You-Go images. ADE is currently not supported for RHEL Bring-Your-Own-Subscription (BYOS) images. Please also refer to the Azure Disk Encryption for Linux article for more information.__
How can I start using Azure Disk Encryption?
To get started, read the Azure Disk Encryption overview.
Can I encrypt both boot and data volumes with Azure Disk Encryption?
Yes, you can encrypt boot and data volumes for Windows and Linux IaaS VMs. For Windows VMs, you can't encrypt the data without first encrypting the OS volume. For Linux VMs, it's possible to encrypt the data volume without having to encrypt the OS volume first. After you've encrypted the OS volume for Linux, disabling encryption on an OS volume for Linux IaaS VMs isn't supported. For Linux VMs in a scale set, only the data volume can be encrypted.
Can I encrypt an unmounted volume with Azure Disk Encryption?
No, Azure Disk Encryption only encrypts mounted volumes.
How do I rotate secrets or encryption keys?
To rotate secrets, just call the same command you used originally to enable disk encryption, specifying a different Key Vault. To rotate the key encryption key, call the same command you used originally to enable disk encryption, specifying the new key encryption.
How do I add or remove a key encryption key if I didn't originally use one?
To add a key encryption key, call the enable command again passing the key encryption key parameter. To remove a key encryption key, call the enable command again without the key encryption key parameter.
Does Azure Disk Encryption allow you to bring your own key (BYOK)?
Yes, you can supply your own key encryption keys. These keys are safeguarded in Azure Key Vault, which is the key store for Azure Disk Encryption. For more information on the key encryption keys support scenarios, see Azure Disk Encryption prerequisites.
Can I use an Azure-created key encryption key?
Yes, you can use Azure Key Vault to generate a key encryption key for Azure disk encryption use. These keys are safeguarded in Azure Key Vault, which is the key store for Azure Disk Encryption. For more information on the key encryption key, see Azure Disk Encryption prerequisites.
Can I use an on-premises key management service or HSM to safeguard the encryption keys?
You can't use the on-premises key management service or HSM to safeguard the encryption keys with Azure Disk Encryption. You can only use the Azure Key Vault service to safeguard the encryption keys. For more information on the key encryption key support scenarios, see Azure Disk Encryption prerequisites.
What are the prerequisites to configure Azure Disk Encryption?
There are prerequisites for Azure Disk Encryption. See the Azure Disk Encryption prerequisites article to create a new key vault, or set up an existing key vault for disk encryption access to enable encryption, and safeguard secrets and keys. For more information on the key encryption key support scenarios, see Azure Disk Encryption overview.
What are the prerequisites to configure Azure Disk Encryption with an Azure AD app (previous release)?
There are prerequisites for Azure Disk Encryption. See the Azure Disk Encryption prerequisites article to create an Azure Active Directory application, create a new key vault, or set up an existing key vault for disk encryption access to enable encryption, and safeguard secrets and keys. For more information on the key encryption key support scenarios, see Azure Disk Encryption overview.
Is Azure Disk Encryption using an Azure AD app (previous release) still supported?
Yes. Disk encryption using an Azure AD app is still supported. However, when encrypting new VMs it's recommended that you use the new method rather than encrypting with an Azure AD app.
Can I migrate VMs that were encrypted with an Azure AD app to encryption without an Azure AD app?
Currently, there isn't a direct migration path for machines that were encrypted with an Azure AD app to encryption without an Azure AD app. Additionally, there isn't a direct path from encryption without an Azure AD app to encryption with an AD app.
What version of Azure PowerShell does Azure Disk Encryption support?
Use the latest version of the Azure PowerShell SDK to configure Azure Disk Encryption. Download the latest version of Azure PowerShell. Azure Disk Encryption is not supported by Azure SDK version 1.1.0.
The Linux Azure disk encryption preview extension is deprecated. For details, see Deprecating Azure disk encryption preview extension for Linux IaaS VMs.
Can I apply Azure Disk Encryption on my custom Linux image?
You can't apply Azure Disk Encryption on your custom Linux image. Only the gallery Linux images for the supported distributions called out previously are supported. Custom Linux images aren't currently supported.
Can I apply updates to a Linux Red Hat VM that uses the yum update?
Yes, you can perform a yum update on a Red Hat Linux VM. For more information, see Linux package management behind a firewall.
What is the recommended Azure disk encryption workflow for Linux?
The following workflow is recommended to have the best results on Linux:
- Start from the unmodified stock gallery image corresponding to the needed OS distro and version
- Back up any mounted drives that will be encrypted. This back up allows for recovery if there's a failure, for example if the VM is rebooted before encryption has completed.
- Encrypt (can take several hours or even days depending on VM characteristics and size of any attached data disks)
- Customize, and add software to the image as needed.
If this workflow isn't possible, relying on Storage Service Encryption (SSE) at the platform storage account layer may be an alternative to full disk encryption using dm-crypt.
What is the disk "Bek Volume" or "/mnt/azure_bek_disk"?
"Bek volume" for Windows or "/mnt/azure_bek_disk" for Linux is a local data volume that securely stores the encryption keys for Encrypted Azure IaaS VMs.
Do not delete or edit any contents in this disk. Do not unmount the disk since the encryption key presence is needed for any encryption operations on the IaaS VM.
What encryption method does Azure Disk Encryption use?
On Windows, ADE uses the BitLocker AES256 encryption method (AES256WithDiffuser on versions prior to Windows Server 2012). On Linux, ADE uses the decrypt default of aes-xts-plain64 with a 256-bit volume master key.
If I use EncryptFormatAll and specify all volume types, will it erase the data on the data drives that we already encrypted?
No, data won't be erased from data drives that are already encrypted using Azure Disk Encryption. Similar to how EncryptFormatAll didn't re-encrypt the OS drive, it won't re-encrypt the already encrypted data drive. For more information, see the EncryptFormatAll criteria.
Is XFS filesystem supported?
XFS volumes are supported for data disk encryption only with the EncryptFormalAll. This will reformat the volume, erasing any data previously there. For more information, see the EncryptFormatAll criteria.
Can I backup and restore an encrypted VM?
Azure Backup provides a mechanism to backup and restore encrypted VM's within the same subscription and region. For instructions, please see Back up and restore encrypted virtual machines with Azure Backup. Restoring an encrypted VM to a different region is not currently supported.
Where can I go to ask questions or provide feedback?
You can ask questions or provide feedback on the Azure Disk Encryption forum.
In this document, you learned more about the most frequent questions related to Azure Disk Encryption. For more information about this service, see the following articles:
Send feedback about: