Skip to content

Commit cc46222

Browse files
Merge pull request #296295 from isamorris99/patch-25
Update configuration-settings.md
2 parents d0419b0 + 5ba5eb3 commit cc46222

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/bastion/configuration-settings.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: cherylmc
55
ms.author: cherylmc
66
ms.service: azure-bastion
77
ms.topic: concept-article
8-
ms.date: 03/03/2025
8+
ms.date: 03/12/2025
99
ms.custom: references_regions, ignite-2024
1010
---
1111

@@ -19,14 +19,14 @@ A SKU is also known as a Tier. Azure Bastion supports multiple SKU tiers. When y
1919

2020
[!INCLUDE [Azure Bastion SKUs](../../includes/bastion-sku.md)]
2121

22-
### Developer SKU
22+
### Bastion Developer
2323

2424
[!INCLUDE [Developer SKU description](../../includes/bastion-developer-sku-description.md)]
2525

2626
[!INCLUDE [Developer SKU regions](../../includes/bastion-developer-sku-regions.md)]
2727

2828
> [!NOTE]
29-
> VNet peering isn't currently supported for the Developer SKU.
29+
> VNet peering isn't currently supported for Bastion Developer.
3030
3131
### <a name="premium"></a>Premium SKU
3232

@@ -55,7 +55,7 @@ You can always upgrade a SKU to add more features. For more information, see [Up
5555
> For Azure Bastion resources deployed on or after November 2, 2021, the minimum AzureBastionSubnet size is /26 or larger (/25, /24, etc.). All Azure Bastion resources deployed in subnets of size /27 prior to this date are unaffected by this change and will continue to work, but we highly recommend increasing the size of any existing AzureBastionSubnet to /26 in case you choose to take advantage of [host scaling](./configure-host-scaling.md) in the future.
5656
>
5757
58-
When you deploy Azure Bastion using any SKU except the Developer SKU, Bastion requires a dedicated subnet named **AzureBastionSubnet**. You must create this subnet in the same virtual network that you want to deploy Azure Bastion to. The subnet must have the following configuration:
58+
When you deploy Azure Bastion using any SKU except the Bastion Developer offering, Bastion requires a dedicated subnet named **AzureBastionSubnet**. You must create this subnet in the same virtual network that you want to deploy Azure Bastion to. The subnet must have the following configuration:
5959

6060
* Subnet name must be *AzureBastionSubnet*.
6161
* Subnet size must be /26 or larger (/25, /24 etc.).
@@ -73,7 +73,7 @@ You can configure this setting using the following methods:
7373

7474
## <a name="public-ip"></a>Public IP address
7575

76-
Azure Bastion deployments, except [Developer SKU](#developer-sku) and [Private-only](#private-only), require a Public IP address. The Public IP must have the following configuration:
76+
Azure Bastion deployments, except [Bastion Developer](#bastion-developer) and [Private-only](#private-only), require a Public IP address. The Public IP must have the following configuration:
7777

7878
* The Public IP address SKU must be **Standard**.
7979
* The Public IP address assignment/allocation method must be **Static**.

0 commit comments

Comments
 (0)