New Azure portal (no endpoints) how to connect to a virtual machine using RDP because of a firewall

Question

I created a virtual machine (not classic, using the Resource Manager) on the new Azure portal, but I need to connect because of the firewall.

I found a bunch of articles explaining how to solve them by editing the endpoint settings for RDP, but there is nothing like that on the new portal!

Incoming and outgoing rules are the firewall rules that I understand, and do not give anything.

I connected to it from home and tried changing the RDP listening port to something not blocked by a firewall with the following shell script power:

Set-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name "PortNumber" -Value 443

By rebooting the virtual machine, the I / O rule -ddd on the portal has changed, but it is still not possible to connect.

Answer 1

• If you created the VM using the resource manager (not classic), you do not have endpoint configurations and you cannot configure the ports as described in Matias answer (to get to your azure virtual machine through the allowed ports in the firewall). Unfortunately, not all VM templates are available for the VM Classic interface. I would really like to know what is the limitation here on the azure.

• VM Matias - , , - . , rdp, , Endpoint.

• , , SSH 443 . :

  • putty your_azurevm_ip: 443 → SSH → , , , L49999 → localhost: 3389

  • SSH- azure VM ( freeSSHd)

  • , SSH, rdp localhost: 49999 SSH- 3389 VM , .

Answer 2

, RDP . Azure VM. RDP Azure VM , . , , 443, SSL/TLS, RDP - .

Answer 3

EndPoint, XXXX- 3389.

Cloud Service/VM, . ( - , , - , ).

, - . , (Network Security Group). "" :

.

Answer 4

​​ :

• azure dashbord, VM , , 443.
• RDP 443 : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber
• VM , 443
• IP: 443
• , Ultra VNC, .