Last night I created an unmanaged VM, created an rdp connection. and everything worked fine. This morning the rdp connection did not work.  I noted that that the PUBLIC PORT for Remote Desktop, shown in the Management Portal, had changed from last night's value!   I'm guessing the VM was rebooted leading to this surprise. Is this a normal occurrence on Azure? Any way to workaround it?

TIA,

edm2

• Edited by edm2 Wednesday, July 08, 2015 1:01 PM edit

You can also set the port via the portal by going to the endpoints.  By default the Azure portal will define this value as Auto(every reboot gets a new random port) as a security feature.  What I see people doing though is setting a range of ports like 33000-33100 and give each new VM a static endpoint like 33001 for the first VM they create and so on.  This way you can be anywhere in the world, remember your VM name and that port range, and you can log in.  The powershell method will set the same value you provide as the portal method so either way works!

• Marked as answer by edm2 Wednesday, July 08, 2015 11:53 PM