Allow basic port forwarding in Network Security Groups
It'd be really nice if Network Security Groups allowed basic port forwarding without the use of Azure Load Balancers. Being able to use an alternate public port for RDP, for example 23456, and directing the traffic to the native port (3389) in the Azure environment via the network group would make things simpler than having to create a load balancer to sit in front of the NSG and VM.
Thanks for sharing this idea – right now we’re not planning on adding this feature since the role of the NSG is exclusively to filter traffic.
Shawn Anderson commented
Mapping external to different internal ports would really be helpful!
David Tissen commented
Yes this would be great!
At least RDP should not have regular port -- hackers keep on attacking over it!