DevOps Thread

Azure Bastion is a fully managed PaaS service enabling SSH and RDP access to your Virtual Network (Jump-Server/Bastion Host) resources through Azure Portal. In this article, we will discuss how can we configure Azure Bastion service to enable secure SSH or RDP access to our Virtual Network resources without needing an IaaS VM with a public IP exposed to the internet. The service at the writing of this post is in preview mode. Below is the sample architecture diagram of using Azure Bastion service. As you could have noticed, Azure Bastion service enables connection to the Virtual Machines in the Virtual Network over SSL, port 443, directly from Azure portal. The public preview of the service is limited to the following Azure Public regions. West US East US West Europe South Central US Australia East Japan East Though no particular reason I will be deploying my resources in the South Central US region. Now let’s explore how to configure Azure Bastion Service

Comments play an important role in writing readable code and maintaining the working software. In PowerShell, comments begin with a  Hash  ( # ) sign.  #  can be included anywhere but inside a string to make the rest of the line a comment. # This a comment. Single line comment. Get-Service   - Name BITS How to add multi-line comments in PowerShell? Powershell has come a long way since the public release of PowerShell version 1 in 2006. From version 2 onwards PowerShell supports multiline comments. PowerShell multiline comments begin with ' <# ' and ends with ' #> ' <# This is also commented.  Multi-line comment. #> Get-Process   - Name explorer