Merge pull request #291694 from matthew-fuller/cloud-init-warning

Update warning to include further information link

Author: prmerger-automator[bot]

articles/operator-nexus/quickstarts-virtual-machine-deployment-arm.md

@@ -26,8 +26,8 @@ Before deploying the virtual machine template, let's review the content to under
 
 :::code language="json" source="includes/virtual-machine/virtual-machine-arm-template.json":::
 
-> [!IMPORTANT]
-> Please ensure that any sensitive data, such as secrets, passwords, private keys, and so on, are encrypted before they are submitted in the userData or networkData fields.
+> [!WARNING]
+> User data will not be encrypted, and any process on the VM can query this data. You should not store confidential information in user data. For more information, see [Azure data security and encryption best practices](/azure/security/fundamentals/data-encryption-best-practices).
 
 Once you have reviewed and saved the template file named ```virtual-machine-arm-template.json```, proceed to the next section to deploy the template.
 

articles/operator-nexus/quickstarts-virtual-machine-deployment-bicep.md

@@ -26,8 +26,8 @@ Before deploying the virtual machine template, let's review the content to under
 
 :::code language="bicep" source="includes/virtual-machine/virtual-machine-bicep-template.bicep":::
 
-> [!IMPORTANT]
-> Please ensure that any sensitive data, such as secrets, passwords, private keys, and so on, are encrypted before they are submitted in the userData or networkData fields.
+> [!WARNING]
+> User data will not be encrypted, and any process on the VM can query this data. You should not store confidential information in user data. For more information, see [Azure data security and encryption best practices](/azure/security/fundamentals/data-encryption-best-practices).
 
 Once you have reviewed and saved the template file named ```virtual-machine-bicep-template.bicep```, proceed to the next section to deploy the template.
 

articles/operator-nexus/quickstarts-virtual-machine-deployment-cli.md

@@ -45,8 +45,8 @@ Before you run the commands, you need to set several variables to define the con
 | ACR_USERNAME               | The username for the Azure Container Registry.                                                        |
 | ACR_PASSWORD               | The password for the Azure Container Registry.                                                        |
 
-> [!IMPORTANT]
-> Please ensure that any sensitive data, such as secrets, passwords, private keys, and so on, are encrypted before they are submitted in the userData or networkData fields.
+> [!WARNING]
+> User data will not be encrypted, and any process on the VM can query this data. You should not store confidential information in user data. For more information, see [Azure data security and encryption best practices](/azure/security/fundamentals/data-encryption-best-practices).
 
 Once you've defined these variables, you can run the Azure CLI command to create the virtual machine. Add the ```--debug``` flag at the end to provide more detailed output for troubleshooting purposes.
 

articles/operator-nexus/quickstarts-virtual-machine-deployment-ps.md

@@ -53,8 +53,8 @@ Before you run the commands, you need to set several variables to define the con
 | NETWORKATTACHMENTNAME            | The name of the Network to attach for workload.      |
 | NETWORKDATA            | The base64 encoded string of cloud-init network data.      |
 
-> [!IMPORTANT]
-> Please ensure that any sensitive data, such as secrets, passwords, private keys, and so on, are encrypted before they are submitted in the userData or networkData fields.
+> [!WARNING]
+> User data will not be encrypted, and any process on the VM can query this data. You should not store confidential information in user data. For more information, see [Azure data security and encryption best practices](/azure/security/fundamentals/data-encryption-best-practices).
 
 Once you've defined these variables, you can run the Azure PowerShell command to create the virtual machine. Add the ```-Debug``` flag at the end to provide more detailed output for troubleshooting purposes.