-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI Support for enabling double encryption for Managed Disks #14107
Comments
JEDI feature request. hi @ramankumarlive next Azure CLI official release date will be July 14th. Let's discuss the timeline offline in email. |
@yungezz Please use this swagger link: Azure/azure-rest-api-specs#9937 |
need bump version |
2 tasks
hi @qwordy why the issue is re-opened? |
Bug of Github |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Resource Provider
Microsoft.Compute
Description of Feature or Work Requested
Double encryption at rest is the continuation of server-side encryption (SSE) at rest with customer managed keys (CMK) that we recently announced in GA for managed disks. SSE with CMK allows customers to encrypt the data stored on managed disks at rest with AES 256 encryption. High security sensitive customers who are concerned of the risk associated with any particular encryption algorithm, implementation , or key being compromised can now opt for additional layer of encryption using a different encryption algorithm/mode using platform managed encryption keys.
To enable two layers of encryption at rest for Managed Disks attached to VMs/VMSS, you must must create a DiskEncryptionSet with encryptionType set as EncryptionAtRestWithPlatformAndCustomerKeys and then associate the DiskEncryptionSet to managed disks.
You can find more details and sample ARM templates here: https://github.com/ramankumarlive/manageddisksdoubleencryptionpreview
Minimum API Version Required
2020-05-01
Swagger Link
Azure/azure-rest-api-specs#9552
Target Date
7/10 for "Enterprise" M4 milestone
The text was updated successfully, but these errors were encountered: