Issues connecting to Azure VM via Bastion with CIS 2022 Image

Question

Issues connecting to Azure VM via Bastion with CIS 2022 Image

Nana Poku 225

Experiencing difficulties connecting to an windows Azure Windows virtual machine via Bastion. This issue seems to be specific to the CIS 2022 level image (cis-windows-server2022-gen2), as a standard VM image on the same virtual network works without issues.

Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-17T02:44:56.8233333+00:00

Hi Nana Poku,

Could you please check and confirm once by deploying similar VMs in another subscription with another bastion to verify any issue with bastion network or deploy similar new VM and bastion in same Vnet.

Ensure VM is in a running state, and not in Stopped or Failed state.

Make sure NSG inbound rule 3389 is configured in the Target VM to allow bastion.

If the issue persists, try recreating the Bastion network to ensure that the AzureBastionSubnet is correctly configured, the required address space is available, and all necessary network security group (NSG) rules properly set up.

Please check below documentation for more information:

https://stackoverflow.com/questions/77221322/azure-vm-creation-with-bastion

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.
Nana Poku 225 Reputation points

2025-06-17T08:15:35.69+00:00

Checked and confirmed and no issues with the Bastion as normal image on the same vnet connect easily and another VM and Bastion in same subnet also works fine.

Vm is in running state and not stopped or failed state.

Port 3389 is configured on the NSG of the source vm.

I'm also owner of the NIC,VM Bastion and vnet
Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-18T02:45:27.94+00:00

Hi Nana Poku,

If the issue persists, could you please try to re-create bastion network for a CIS 2022 level image Azure Windows VM.

Thank You

Your answer

Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-17T02:44:56.8233333+00:00

Hi Nana Poku,

Could you please check and confirm once by deploying similar VMs in another subscription with another bastion to verify any issue with bastion network or deploy similar new VM and bastion in same Vnet.

Ensure VM is in a running state, and not in Stopped or Failed state.

Make sure NSG inbound rule 3389 is configured in the Target VM to allow bastion.

If the issue persists, try recreating the Bastion network to ensure that the AzureBastionSubnet is correctly configured, the required address space is available, and all necessary network security group (NSG) rules properly set up.

Please check below documentation for more information:

https://stackoverflow.com/questions/77221322/azure-vm-creation-with-bastion

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.
Nana Poku 225 Reputation points

2025-06-17T08:15:35.69+00:00

Checked and confirmed and no issues with the Bastion as normal image on the same vnet connect easily and another VM and Bastion in same subnet also works fine.

Vm is in running state and not stopped or failed state.

Port 3389 is configured on the NSG of the source vm.

I'm also owner of the NIC,VM Bastion and vnet
Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-18T02:45:27.94+00:00

Hi Nana Poku,

If the issue persists, could you please try to re-create bastion network for a CIS 2022 level image Azure Windows VM.

Thank You

Share via

Issues connecting to Azure VM via Bastion with CIS 2022 Image

Your answer