Merge pull request #214964 from cherylmc/patch-9

Add peered vnet information

Author: prmerger-automator[bot]

articles/bastion/bastion-connect-vm-ssh-windows.md

@@ -5,7 +5,7 @@ description: Learn how to use Azure Bastion to connect to Windows VM using SSH.
 author: cherylmc
 ms.service: bastion
 ms.topic: how-to
-ms.date: 08/18/2022
+ms.date: 10/18/2022
 ms.author: cherylmc
 ms.custom: ignite-fall-2021
 ---
@@ -40,6 +40,7 @@ In order to make a connection, the following roles are required:
 * Reader role on the virtual machine
 * Reader role on the NIC with private IP of the virtual machine
 * Reader role on the Azure Bastion resource
+* Reader role on the virtual network of the target virtual machine (if the Bastion deployment is in a peered virtual network).
 
 ### Ports
 
@@ -48,6 +49,8 @@ In order to connect to the Windows VM via SSH, you must have the following ports
 * Inbound port: SSH (22) *or*
 * Inbound port: Custom value (you will then need to specify this custom port when you connect to the VM via Azure Bastion)
 
+See the [Azure Bastion FAQ](bastion-faq.md) for additional requirements.
+
 ### Supported configurations
 
 Currently, Azure Bastion only supports connecting to Windows VMs via SSH using **OpenSSH**.