Azure Bastion Service–End User Experience

In this blog post we will be discussing the end user experience for the Azure Bastion Service.

In the previous post, we provisioned an Azure Bastion Service in our VNET. The environment looks as below now.


The key thing in this architecture is, all inbound traffic to the network is HTTPs. Using RDP over the internet is not secure. By eliminating RDP in the external network secure the way end users connect to the server.

The Bastion resource group looks as below.


There are two resources in the resource group. Once resource for Bastion and a public IP.

Now let’s have a look at how we can connect to a VM in the network.

Click on a VM in the same VNET that Azure Bastion Service was provisioned.


Then on the right hand side, select Bastion.


Then enter the local admin username and the password.

You might need to allow pop  up s for Azure Portal and Bastion here. Once allowed you will see a new popup window open with Bastion.


Logging in to the server experience is really easy. At the moment it’s limited to the Azure portal. But Microsoft has mentioned that they will provide the direct RDP via Bastion using the native RDP client.

About sameeraman
I'm a proactive and enthusiastic Microsoft Azure and Identity Consultant working in Perth Australia. My aim is to resolve customer problems and provide them with the best IT systems that satisfy their requirements while maintaining the minimum cost.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: