I'm stuck in the manual "Create a Bastion" Basics screen

Mike 61 Reputation points
2023-08-04T04:14:30.9733333+00:00

Hi All,

I'm studying for the AZ-104 Azure AD Administrator exam and so I'm currently going through a lesson video for manually creating the Bastion server to connect to a virtual machine. (In a prior video lesson I successfully created and signed into the virtual machine using RDP.) Yet the problem I'm encountering with current Bastion lesson, is that in the "Basics" screen of the "Create a Bastion", the "Region" field is empty, including the drop down menu, empty as well. On top of that, the "Virtual network" entry box is grayed with the word "Loading" and when I select, “Create New”. A message displays that I first need to input the “Region” field first. But again the “Region” field is empty.

I’ve gone back through the steps multiple times and I get stuck at this same spot. I’ve also re-created the virtual machine over again and I still get the same issue with the Bastion. In the video lesson the “Region” and the “Virtual network” load instantly. And I’ve re-watched the video and I’ve confirmed I’m doing the exact same steps leading up to where I’m stuck. Which has me confused, so I could really use some input on how I can get the “Create a Bastion” to work using the manual setup steps.

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
0 comments
Accepted answer
  1. KapilAnanth-MSFT 39,461 Reputation points Microsoft Employee
    2023-08-04T04:26:09.2533333+00:00

    @Mike

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

    Our Product Team is aware of this issue. They also assured that they have a fix that is rolling out.

    The approximate ETA for this is around 2-3 weeks .

    For now, the work around is to deploy Bastion using the Preview Azure poral or deploy it from the VNet/VM blade in the regular Azure portal.

    You can also use Azure Powershell or Azure CLI to workaround this

    Thanks for your continued contribution on Q&A and appreciate much for taking the time to share your feedback.

    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 additional answers

Sort by: Most helpful
Most helpful Newest Oldest