VNET secured VM is not opening with Bastion

Neelam Mourya 60 Reputation points Microsoft Employee
2023-07-06T05:11:00.4033333+00:00

I have setup Virtual network and required subnets in a resource group.
I have created a VNET secured VM, a Bastion subnet and Bastion service. Bastion service is attached with a public IP address.

I am trying to open my VM through bastion, but it gives me below connection error:

APP.DIALOG_HEADER_CONNECTION_ERROR

CLIENT.TEXT_CLIENT_STATUS_301

BAstion error.png
Error page is attached in this thread.

Please let me know if anyone has experienced this issue.

Azure Bastion
Azure Bastion
An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
247 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,268 questions
Accepted answer
  1. KapilAnanth-MSFT 39,461 Reputation points Microsoft Employee
    2023-07-06T09:37:04.3966667+00:00

    @Neelam Mourya

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you are unable to access a VM via Bastion.

    This appears to be a known issue with VNets having a Private DNS Zone "privatelink.azure.com" linked to the VNet.

    • You will be required to create a record in your "privatelink.azure.com" zone with
      • Name = management.privatelink.azure.com
        • Type = CNAME
          • Alias = arm-frontdoor-prod.trafficmanager.net

    Kindly let us know if this helps or you need further assistance on this issue.

    Thanks,

    Kapil

    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest