Bastion supporting vnet peering for Hub & Spoke design
Please allow us to deploy Bastion in Hub & Spoke vnet design. It makes sense to deploy Bastion in Hub vnet only. Than we can access VMs in spoke vnets from Bastion. Hub & Spoke design is Azure recommended Reference architecture, make sense to support it.
We are currently planning for this!
Red Daniel commented
After an year we haven't support of this!!! MS tries to catch our money for these stupid things!!! In the COVID-19 era we have to connect our infrastructure in Hub&Spoke model!! Please accelerate develop for this feature!! @AzureNetworkingTeam
Limiting the reach of a bastion to a single connected vnet is very cost/user prohibitive especially in a hub and spoke model, as others have requested, we're keen to see this feature supporting this model.
Is there any update on this request?
Mike's Garage commented
Any news about this in roadmap and when in GA?
Last update 09/2019, in planning mode. How about now?
And how about supporting different keyboard layouts?
Mike's IT Garage
It seems like Bastion was released without features that most users require (AAD support, MFA, peering, etc.). I really want to use this product, but with all this stuff missing it's pretty much useless at the moment.
Mitesh Chauhan commented
Ok great product but pretty useless without peering for most environments using best practice hub and spoke architecture...
really curious for an ETA
just a kick since I haven't seen anything new since last thursday, lol :) I need this badly.
Definitely need this. No way am I going to deploy a Bastion in each VNet.
Benjamin Van Brussel commented
Definitely still a requirement. Any updates regarding this?
Rohit Kumar commented
I believe Hub and Spoke Model is used by most of Enterprise Customer and is one of the basic Necessity.
I just also wanted to know is it a Feasible Solution for connecting more than 1000 User
Nathan Aeder commented
Hub and Spoke support would be a requirement for us using Azure Bastion. Any updates on release dates or preview availability?
It's mandatory for us to have this kind of possibilities
Is there any way that a Bastion endpoint can be used as RD Gateway server (eg. in MSTSC advanced settings)?
Can you guys please let us know the time-frame for the release of this feature
Thank you for the fedback, this is part of our backlog. As of now, we don't have a specific ETA to share, but this is prioritized very high in our backlog.
Product Manager, Azure Bastion
Minh Trieu commented
We are also keen on this product, but since it only works on a single VNET its not viable. Is there any rough timelines for when this will be implemented?
Mohammad Nizamuddin commented
Any timeline for this feature please?
This is needed in Hub & Spoke design otherwise we need to duplicate the Azure Bastion in each vnet.