Simple Remote Desktop Services deployment

Brass Contributor
I need to expose a windows server vm which is hoated in Azure, to 3 users for temporary use. I could simply setup RDP with public IP and get the users to connect, but I am afraid this is not secure and I could be exposing the vm access.

The use case is too small for a full blown vdi solution because this is for time to time use.

I though about using WebRD to push the rdp app or tje server desktop. This would add another layer of security.

I can not find a clear guide of what i need to deploy this and if i can do it all with 1 single vm which is actually the hoat i am trying to provision access to.
Also, i can not understand what do i need from a service license point of view. From license i already have vm running so i know about these costs. Its more about the rds setup and access.

Thank you.
2 Replies

You could definitely deploy this all in one VM knowing it is for temporary use. The simplest setup would be to put a Network Security Group in front of the VM and only open TCP 3389 to the ip's of where your users are coming from. If this is going to connect to any services on premises I would highly recommend to firewall the traffic. The NSG does not do deep packet inspection it simply deny's or allows traffic based on your rules. 


@Rui Cabral 



there is a dedicated service for that called Azure Bastion.

- User will connect to the portal with there Azure AD credential (MFA enabled as a good practice)

- They will click on the "Bastion" panel of the VM and use the VM credential and this connection will be done over HTTPS.


As another good practice you could also set is to configure NSG on the Bastion subnet and on your VM, for that you could refer to this article:


Just keep in mind that an Azure Bastion could cover the connection to the VM located in only one virtual network. If you have over vnet you will need to create one bastion per vnet.