Hi!) Looks like pretty nice piece of stuff but not for its price, IMHO. Old fashioned jump-host VM (B2s size) will be cost much less. And actually It can be published via Azure WVD for providing web-access ;))) And It will be able to connect to hosts in all Vnets with configured interconnection. P.S. Great channel, man! Really informative and helpful. Thanks for your work!) P.P.S. And sorry for my English)
Excellent video. I’m going to follow these instruction to setup the bastion host on an environment I’ve just created. I need to give the SAP installers access to the Linux VM’s through the bastion. You accessed your machine through the Azure portal. I don’t want the installers to use the portal, so how do they connect to the two Linux VM’s?
Travis Roberts So, do I create the SAP application installers an Azure portal account, but use permissions so they cannot access the Azure resource, only use the Bastion to establish an SSH connection to the SUSE VM? Is that how it supposed to be used?
I was hoping that Bastion would provide a secure way for my users to access their VM. However, having them log into Azure and then connecting to a VM seems overly complicated and fraught with potential problems. As a method for technicians and SysAdmins to connect to VMs, I guess it's okay but not very practical for end users.
Guys - you CAN'T just skim over the creation of your VM's. I have followed this to the letter, and I CANNOT add my EXISTING VM to my new bastion subnet. Simply no way. This is a vital detail and you don't even touch upon it. PLEASE, outline the ENTIRE process. I'm on a steep curve here and you HAVE COST me time instead of shortening the time for me to get a GUI working on my new Azure VM. This was CAKE on AWS. Defining a new subnet around my existing VM doesn't work...there's no way to define the IP range such that it works. Conversely, first defining the subnet and THEN attempting to add my existing VM to it doesn't work either. UGGGHHH!!!!! MUST I create a whole new VM AFTER defining my Bastion subnet?????!!!??
Hi!) Looks like pretty nice piece of stuff but not for its price, IMHO. Old fashioned jump-host VM (B2s size) will be cost much less. And actually It can be published via Azure WVD for providing web-access ;))) And It will be able to connect to hosts in all Vnets with configured interconnection.
P.S. Great channel, man! Really informative and helpful. Thanks for your work!)
P.P.S. And sorry for my English)
Thanks and all valid points. With WVD and Windows 10 Multi user there is no RDS licensing and unlimited connections.
Excellent video. I’m going to follow these instruction to setup the bastion host on an environment I’ve just created. I need to give the SAP installers access to the Linux VM’s through the bastion. You accessed your machine through the Azure portal. I don’t want the installers to use the portal, so how do they connect to the two Linux VM’s?
Azure Bastion is a portal-based solution. Connecting with a SSH or RDP client is not an option at this time.
Travis Roberts So, do I create the SAP application installers an Azure portal account, but use permissions so they cannot access the Azure resource, only use the Bastion to establish an SSH connection to the SUSE VM? Is that how it supposed to be used?
I was hoping that Bastion would provide a secure way for my users to access their VM. However, having them log into Azure and then connecting to a VM seems overly complicated and fraught with potential problems. As a method for technicians and SysAdmins to connect to VMs, I guess it's okay but not very practical for end users.
Exactly .. looking for a way to secure my users connecting to the VM..
Do you know if it forwards keyboard shortcuts?
Copy/paste seem to work between local and remote sessions using Chrome. The Windows key changes focus to the local host.
@@Ciraltos Thanks for the quick reply!
Guys - you CAN'T just skim over the creation of your VM's. I have followed this to the letter, and I CANNOT add my EXISTING VM to my new bastion subnet. Simply no way. This is a vital detail and you don't even touch upon it. PLEASE, outline the ENTIRE process. I'm on a steep curve here and you HAVE COST me time instead of shortening the time for me to get a GUI working on my new Azure VM. This was CAKE on AWS. Defining a new subnet around my existing VM doesn't work...there's no way to define the IP range such that it works. Conversely, first defining the subnet and THEN attempting to add my existing VM to it doesn't work either. UGGGHHH!!!!! MUST I create a whole new VM AFTER defining my Bastion subnet?????!!!??
Have you reached out to Microsoft for help on this?