Merge pull request #112705 from charwen/patch-196

Updated wording for UDR and NSG

Author: PRMerger20

articles/bastion/bastion-create-host-portal.md

@@ -6,7 +6,7 @@ author: cherylmc
 
 ms.service: bastion
 ms.topic: conceptual
-ms.date: 02/03/2020
+ms.date: 04/24/2020
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to create an Azure Bastion host.
 
@@ -45,9 +45,9 @@ 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, or 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. You must use a subnet of at least /27 or larger (/27, /26, and so on).
+    * **Subnet**: The subnet in your virtual network where the new Bastion host will be deployed. The subnet will be dedicated to the Bastion host and must be named as **AzureBastionSubnet**. This subnet must be at least /27 or larger.
 
-       Create the **AzureBastionSubnet** without any route tables or delegations. If you use Network Security Groups on the **AzureBastionSubnet**, refer to the [Work with NSGs](bastion-nsg.md) article.
+       **AzureBastionSubnet** doesn't support [User Defined Routes](../virtual-network/virtual-networks-udr-overview.md#custom-routes), but does support [Network Security Groups](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**: This setting is prepopulated by default to **Standard**. Azure Bastion uses/supports only the Standard Public IP SKU.
@@ -61,4 +61,4 @@ This section helps you create a new Azure Bastion resource from the Azure portal
 
 * Read the [Bastion FAQ](bastion-faq.md) for additional information.
 
-* To use Network Security Groups with the Azure Bastion subnet, see [Work with NSGs](bastion-nsg.md).
+* To use Network Security Groups with the Azure Bastion subnet, see [Work with NSGs](bastion-nsg.md).