Configure an Azure Bastion entry WITHOUT native client support option

Hello

I'm afraid that, as far as I know, native client is required for our integration (where RDM functions as the "native client", as opposed to a web-based connection).

That being said: are you sure you can't deploy a Bastion over the CLI with native client support? Do you have a link to the feature request? With Azure CLI, I think the relevant parameter is `--enable-tunneling`.

For example, in their docs they have this:

> Update a Azure Bastion host machine to enable native client support.
>
> az network bastion update --name MyBastionHost --resource-group MyResourceGroup --enable-tunneling

And --enable-tunneling is also a parameter for az network bastion create.

Please let me know if you have some questions

Kind regards,

Thanks a lot for this hint! You are right!

"native client support" corresponds to the Tunneling option. I didnt realize that it is the same. I just tested it with this:
If you are curious why I got confused: https://github.com/Azure/azure-powershell/issues/17228
In the official Microsoft documentation for the azure cmdlet's its always just mentioned as "tunneling" but never as "native client support", which I was searching for basically.

Solved it now with this:

Create):
New-AzBastion -ResourceGroupName $rg -Name $name -PublicIpAddressId $publicIpId -VirtualNetworkRgName $vnet_rg -VirtualNetworkName $vnet_name -Sku "Standard" -EnableTunneling $true

or

Update):
Set-AzBastion -InputObject $bastionObj -EnableTunneling $true

Thank you!

Hello

I agree, this is confusing; the whole Azure Bastion rollout has had messy edge cases like this. I'm glad it's working for you. I'll mark the topic resolved but don't hesitate with further questions or comments.

Kind regards,