Both the Powershell and CLI example commands are written in a manner that assumes that the Key Vault is located in the same resource group as the VM. The value/parameter "MySecureRG" works for constructing the Key Vault ID and URL values, however if the VM and KV do not live in the same RG the command will fail when running " Set-AzureRmVmssDiskEncryptionExtension" or "az vm encryption enable".
This could lead to confusion and questions regarding deployment topology / security best practices. Possibly update syntax to allow for the Key Vault to be located in a different RG but still co-located in the same subscription.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
Hi @cocallaw.
Thanks for taking the time to provide feedback on Azure Disk Encryption! This is an interesting idea, and I want to make sure it gets directly into the hands of the engineering team. Fortunately, we've got dedicated channels for that very purpose. :) See the Feedback for Azure Virtual Machines website. I think it’s important that you submit it directly because that allows you to receive notifications and more closely monitor the progress. I'm closing this issue as there's nothing actionable for the Azure Security Documentation team at this time.
@cocallaw Thanks for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
This is a documentation error, not a product error.
For clarity, the samples should have
$rgNameVM and $rgNameVault
@mestew Can you please take a look. Thanks. :)
Clarifying this with product team to determine what needs to be updated.
@cocallaw & @OffColour
I have these changes currently in the works.
Thanks @mestew
Adding issue https://github.com/Azure/azure-cli/issues/8518 from the Azure CLI for reference
@cocallaw Hey Corey, these changes should go live in the next day or so.
Most helpful comment
@cocallaw & @OffColour
I have these changes currently in the works.