SSH login failed after VM encryption.

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
Template : https://github.com/Azure/azure-quickstart-templates/tree/master/201-encrypt-running-linux-vm

I am trying to use this template to encrypt running VMs. The VM image is Ubuntu 16.04.0-LTS from Azure, the size of VM are Standard_D2 and Standard_DS3v2, and are created with SSH public key. Before the VM encryption, the SSH private keys works well and no failure when SSH to these machine. But after the VM encryption, the SSH login failed with error message "public denied". Does this template changes the key or the credential?

Start with the 201-encrypt-running-linux-vm template and the reported Ubuntu 16.04 VM configuration. Reproduce the SSH failure before and after encryption, then determine whether the template changes the SSH key or credential and document the confirmed behavior or required fix.

Written by the indexing model from the issue text.