Merge pull request #253648 from cherylmc/bas-subnet

update for failed subnet issue

Author: v-shils

articles/bastion/quickstart-host-portal.md

@@ -5,7 +5,7 @@ description: Learn how to deploy Bastion with default settings from the Azure po
 author: cherylmc
 ms.service: bastion
 ms.topic: quickstart
-ms.date: 06/08/2023
+ms.date: 10/03/2023
 ms.author: cherylmc
 
 ---
@@ -15,7 +15,7 @@ ms.author: cherylmc
 In this quickstart, you'll learn how to deploy Azure Bastion with default settings to your virtual network using the Azure portal. After Bastion is deployed, you can connect (SSH/RDP) to virtual machines (VM) in the virtual network via Bastion using the private IP address of the VM. The VMs you connect to don't need a public IP address, client software, agent, or a special configuration. For more information about Azure Bastion, see [What is Azure Bastion?](bastion-overview.md)
 
 :::image type="content" source="./media/create-host/host-architecture.png" alt-text="Diagram showing Azure Bastion architecture." lightbox="./media/create-host/host-architecture.png":::
- 
+
 The steps in this article help you do the following:
 
 * Deploy Bastion with default settings from your VM resource using the Azure portal. When you deploy using default settings, the settings are based on the virtual network to which Bastion will be deployed. 
@@ -89,6 +89,10 @@ When you create Azure Bastion using default settings, the settings are configure
 
 1. Bastion begins deploying. This can take around 10 minutes to complete.
 
+   > [!NOTE]
+   > [!INCLUDE [Bastion failed subnet](../../includes/bastion-failed-subnet.md)]
+   >
+
 ## <a name="connect"></a>Connect to a VM
 
 When the Bastion deployment is complete, the screen changes to the **Connect** page.

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

@@ -4,7 +4,7 @@ description: Learn how to deploy Bastion using settings that you specify - Azure
 author: cherylmc
 ms.service: bastion
 ms.topic: tutorial
-ms.date: 06/08/2023
+ms.date: 10/03/2023
 ms.author: cherylmc
 
 ---
@@ -110,7 +110,7 @@ This section helps you deploy Bastion to your VNet. Once Bastion is deployed, yo
 
 1. On the **Subnets** page, select **+Subnet** to open the **Add subnet** page.
 
-1. On the **Add subnet page**, create the 'AzureBastionSubnet' subnet using the following values. Leave the other values as default.
+1. On the **Add subnet page**, create the 'AzureBastionSubnet' subnet using the following values. Leave the other values as default. 
 
    * The subnet name must be **AzureBastionSubnet**.
    * The subnet must be at least **/26 or larger** (/26, /25, /24 etc.) to accommodate features available with the Standard SKU.

includes/bastion-failed-subnet.md

@@ -0,0 +1,9 @@
+---
+author: cherylmc
+ms.service: bastion
+ms.topic: include
+ms.date: 10/03/2023
+ms.author: cherylmc
+---
+
+If you get a message saying "Failed to add subnet", you can work around this issue that sometimes occurs in some regions. Go to the **Subnets** page for your VNet and add a subnet. The subnet name must be **AzureBastionSubnet**. The subnet address range specified must be /26 or larger. (/25, /24 etc.) After you add the subnet, you can **Deploy Bastion**.