Kazuyuki Sakemi

Just a workaround works for me. ``` $ResourceGroupName = "xxxxxxxx" $BastionName = "bast-xxxxxxxx" $ResourceId = "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/xxxxxxxx/providers/Microsoft.Compute/virtualMachines/vm-xxxxxxxx" $Token = (Get-AzAccessToken).Token $Headers = @{ 'Content-Type' = 'application/json' 'Authorization' = "Bearer $token" }...

Just adding below code to your profile.ps1, I can use `Connect-MyAzBastionRdp` (or any name you want) cmdlet to connect to a VM. Thanks @awakecoding! ```powershell Function Connect-MyAzBastionRdp() { [CmdletBinding()] param...

As far as I investigated, Azure Portal utilizes Resource Graph to examine whether there's available Bastion to connect the VM. (I don't sure in detail, but it returns a Bastion...