Skip to content

Commit ae50c45

Browse files
authored
Merge pull request #263549 from cherylmc/bastion-subnet
Add AzureBastionSubnet
2 parents 7db44a4 + f02f467 commit ae50c45

File tree

3 files changed

+24
-6
lines changed

3 files changed

+24
-6
lines changed

articles/bastion/quickstart-host-portal.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to deploy Azure Bastion with default settings from the Az
55
author: cherylmc
66
ms.service: bastion
77
ms.topic: quickstart
8-
ms.date: 10/12/2023
8+
ms.date: 01/18/2024
99
ms.author: cherylmc
1010

1111
---
@@ -80,6 +80,14 @@ When you deploy from VM settings, Bastion is automatically configured with the f
8080
| **Name** | Based on the virtual network name |
8181
| **Public IP address name** | Based on the virtual network name |
8282

83+
## Configure the AzureBastionSubnet
84+
85+
When you deploy Azure Bastion, resources are created in a specific subnet which must be named **AzureBastionSubnet**. The name of the subnet lets the system know where to deploy resources. Use the following steps to add the AzureBastionSubnet to your virtual network:
86+
87+
[!INCLUDE [Add AzureBastionSubnet](../../includes/bastion-add-subnet-include.md)]
88+
89+
After adding the AzureBastionSubnet, you can continue to the next section and deploy Bastion.
90+
8391
## <a name="createvmset"></a>Deploy Bastion
8492

8593
When you create an Azure Bastion instance in the portal by using **Deploy Bastion**, you deploy Bastion automatically by using default settings and the Basic SKU. You can't modify, or specify additional values for, a default deployment.
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
author: cherylmc
3+
ms.author: cherylmc
4+
ms.date: 01/18/2024
5+
ms.service: bastion
6+
ms.topic: include
7+
---
8+
9+
1. On the page for your virtual network, in the left pane, select **Subnets** to open the Subnets page.
10+
1. At the top of the page, click **+ Subnet** to open the **Add subnet** pane.
11+
1. For **Name**, you must use **AzureBastionSubnet**.
12+
1. Adjust the IP address range value, if necessary. We recommend that you use a subnet that's /26 or larger, (/26, /25, or /24). Example subnet value: **10.1.1.0/26**.
13+
1. Don't adjust the other values on the page. Click **Save** at the bottom of the page to save the subnet.

includes/bastion-failed-subnet.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,8 @@
22
author: cherylmc
33
ms.service: bastion
44
ms.topic: include
5-
ms.date: 10/03/2023
5+
ms.date: 01/18/2024
66
ms.author: cherylmc
77
---
88

9-
If you get a message that says "Failed to add subnet," you can work around this problem. It sometimes occurs in some regions.
10-
11-
1. Go to the **Subnets** page for your virtual network and add a subnet. The subnet name must be **AzureBastionSubnet**. The subnet address range that you specify must be /26 or larger (for example, /25 or /24).
12-
1. Select **Deploy Bastion**.
9+
If you get a message that says "Failed to add subnet", you need to add the **AzureBastionSubnet** subnet to your virtual network before deploying Bastion. Go to the **Subnets** page for your virtual network and add the AzureBastionSubnet. The subnet name must be **AzureBastionSubnet**. The subnet address range that you specify must be /26 or larger (for example, /25 or /24). After adding this subnet to your virtual network, you can deploy Bastion.

0 commit comments

Comments
 (0)