how to allow my IP to access the RDP using port 3389

Question

how to allow my IP to access the RDP using port 3389

Bashir Salama 0

our customer who is using our software asked us to block RDP access to the server from anywhere, as a part of their security measurements, the step i took was to allow secured access to the server only on port 3389, so now the RDP is not accessible from anywhere as needed, so we have returned back to access the server from the Azure portal but the portal shows an error and not allowing to access the vm, although the software which is published on that server is working fine so the server is running, but it is only blocking all accesses, is there a way to revert the updates we have done, or steps to access the vm from the portal smoothly. i can provide more details if needed,

Jerald Felix 9,015 Reputation points

2025-10-22T10:48:02.29+00:00
Hello Bashir Salama,

It sounds like your Network Security Group (NSG) or Azure Firewall rules may have become too restrictive, blocking Remote Desktop Protocol (RDP) access (port 3389) — even from the Azure portal. Don’t worry, you can safely restore access by following these steps:

Step 1: Verify that the VM is running

Since your application is still accessible, the VM itself is healthy. Go to your Azure Portal → Virtual Machines → Overview and confirm the Status = Running.

Step 2: Use “Reset NSG Rules” from Azure Portal

In the VM’s left menu, choose “Connect → RDP.”

If RDP fails, go to “Networking” → Network Interface → NSG (Network Security Group).

Under Inbound Security Rules, create a rule like this:

Name: AllowRDPFromMyIP

**Port:** 3389 **Protocol:** TCP **Source:** *My IP address* (it automatically detects your current public IP) **Priority:** Lower than any Deny rule (e.g., 100) **Action:** Allow

This ensures that only your machine can connect via RDP, maintaining security.

Step 3: Check Azure Firewall (if used)

If your VM is behind Azure Firewall or a custom route:

Go to Firewall → Rules → Network Rules Collection.

Add a rule allowing Inbound TCP 3389 from your public IP to the VM’s private IP.

Step 4: If RDP is still blocked

You can temporarily use Azure Bastion:

In your VM page, select Connect → Bastion.

Deploy Bastion if not yet configured (takes 2–3 minutes).

Connect to your VM directly through the browser without opening port 3389 publicly. (Bastion is safer for long-term administration.)

Optional Step: Revert earlier blocking changes

If you used PowerShell or CLI to deny 3389, you can undo it:

az network nsg rule delete \ --resource-group <yourRG> \ --nsg-name <yourNSG> \ --name <rule-name>

Then recreate the allow rule as shown in Step 2.

After applying these changes, retry RDP from your local computer using the VM’s Public IP and ensure your system firewall allows outbound port 3389. I believe this detail walkthrough helps you resolve your issue. Kindly accept the answer and support the community.

Best Regards,

Jerald Felix
Bashir Salama 0 Reputation points

2025-10-22T11:30:56.0833333+00:00

thanks for your answer we tried actually some of these steps, here is what we get

and then

but then
Praveen Bandaru 8,930 Reputation points Microsoft External Staff Moderator

2025-10-23T09:50:26.86+00:00

Hello Bashir Salama

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries. Also, please check your private messages and share the necessary details so we can investigate the issue further.

Hope the above answer helps! Please let us know do you have any further queries.

Please do not forget to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

2 answers

Your answer

Bashir Salama 0 Reputation points

2025-10-22T11:30:56.0833333+00:00

thanks for your answer we tried actually some of these steps, here is what we get

and then

but then
Praveen Bandaru 8,930 Reputation points Microsoft External Staff Moderator

2025-10-23T09:50:26.86+00:00

Hello Bashir Salama

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries. Also, please check your private messages and share the necessary details so we can investigate the issue further.

Hope the above answer helps! Please let us know do you have any further queries.

Please do not forget to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 1

Praveen Bandaru 8,930 Microsoft External Staff Moderator

Hello Bashir Salama

Thank you for your response. please check the below information for further investigation:

Please check if there is any NSG attached to the Bastion subnet and ensure it does not block any traffic.
Also, kindly review the NSG rules at both the NIC and subnet levels of the VM to confirm that the Bastion subnet's private range is not being blocked.
And also, please let me know any route table is associated to VM or Bastion subnets.

Hope the above answer helps! Please let us know do you have any further queries.

Please do not forget to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Praveen Bandaru 8,930 Reputation points Microsoft External Staff Moderator

2025-10-28T18:25:32.6+00:00

Hello Bashir Salama
Based on my analysis, I can see that you are unable to connect to RDP using the public IP as well. It appears the issue may be related to the VM team. I suggest checking with the VM team, and I will also look into this internally.

Answer 2

Hello Bashir Salama,

I understand your problem.

Could you please let me know following?

Is there a firewall (Azure or any third party fw) in your environment and is it the next hop for traffic to internet and private IP address.

You can verify by checking if there is any ROute table associated to your VM subnet and routes inside the route table, you can post the screenshot for reference.

If there is a NVA of Azure firewall, you would have to allow the traffic there as well.

Since you are trying to access from Bastion, check any NSG or Route table on your Bastion subnet.

NSG can block the traffic, whereas an incorrectly configured route table can misroute/blackhole your traffic.

You can have NSG flow logs enabled on your VM NSG to see whether the traffic is hitting to this VM or not and take action accordingly.
Most probably there would be one mode NSG (subnet level and NIC level) which is blocking the traffic.
You can check ip flow verify from VM using Azure portal to see what the next hop for 0.0.0.0/0 or any public and private address is.
Please let me know if this helps and upvote the answer to help the community.

You can check

Share via

how to allow my IP to access the RDP using port 3389

2 answers

Your answer