Merge pull request MicrosoftDocs#35292 from RyanLWilliams/master

Update for using NSGs on Azure Bastion Subnet
tejado · Jul 23, 2019 · 39ff72e · 39ff72e
2 parents 198c3a5 + 4b53de0
commit 39ff72e
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/articles/bastion/bastion-create-host-portal.md b/articles/bastion/bastion-create-host-portal.md
@@ -52,7 +52,7 @@ This section helps you create a new Azure Bastion resource from the Azure portal
  * **Name**: The name of the new Bastion resource
  * **Region**: The Azure public region that the resource will be created in.
  * **Virtual network**: The virtual network in which the Bastion resource will be created in. You can create a new virtual network in the portal during this process, in case you don’t have or don’t want to use an existing virtual network. If you are using an existing virtual network, make sure the existing virtual network has enough free address space to accommodate the Bastion subnet requirements.
- * **Subnet**: The subnet in your virtual network to which the new Bastion host resource will be deployed. You must create a subnet using the name value **AzureBastionSubnet**. This value lets Azure know which subnet to deploy the Bastion resources to. This is different than a Gateway subnet. We highly recommend that you use at least a /27 or larger subnet (/27, /26, and so on). Create the **AzureBastionSubnet** without any Network Security Groups, route tables, or delegations.
+ * **Subnet**: The subnet in your virtual network to which the new Bastion host resource will be deployed. You must create a subnet using the name value **AzureBastionSubnet**. This value lets Azure know which subnet to deploy the Bastion resources to. This is different than a Gateway subnet. We highly recommend that you use at least a /27 or larger subnet (/27, /26, and so on). Create the **AzureBastionSubnet** without any route tables or delegations. When you use Network Security Groups on the **AzureBastionSubnet**, refer to [Work with NSGs](bastion-nsg.md).
  * **Public IP address**: The public IP of the Bastion resource on which RDP/SSH will be accessed (over port 443). Create a new public IP, or use an existing one. The public IP address must be in the same region as the Bastion resource you are creating.
  * **Public IP address name**: The name of the public IP address resource.
  * **Public IP address SKU**: Prepopulated by default to **Standard**. Azure Bastion uses/supports only the Standard Public IP SKU.