Skip to content

Commit cb58c0a

Browse files
author
Abdullah Bell
committed
overhauled upgrade sku article to be more impactful
1 parent 986c676 commit cb58c0a

1 file changed

Lines changed: 175 additions & 27 deletions

File tree

‎articles/bastion/upgrade-sku.md‎

Lines changed: 175 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,57 +1,205 @@
11
---
2-
title: Upgrade or view a SKU - portal
2+
title: View or upgrade an Azure Bastion SKU
33
titleSuffix: Azure Bastion
4-
description: Learn how to view a SKU and upgrade SKU tiers.
4+
description: Learn how to view your current Azure Bastion SKU and upgrade to a higher tier using the Azure portal or Azure CLI.
55
author: abell
66
ms.service: azure-bastion
77
ms.topic: how-to
8-
ms.date: 03/31/2025
8+
ms.date: 02/10/2026
99
ms.author: abell
1010

1111
# Customer intent: As an Azure administrator, I want to view and upgrade my Bastion SKU so that I can enhance the features and capabilities of my secure remote access setup.
1212
---
1313

14-
# View or upgrade a SKU
14+
# View or upgrade an Azure Bastion SKU
1515

16-
This article helps you view and upgrade your Bastion SKU. Once you upgrade, you can't revert back to a lower SKU without deleting and reconfiguring Bastion. For more information about features and SKUs, see [Configuration settings](configuration-settings.md).
16+
This article helps you view your current Azure Bastion SKU and upgrade to a higher tier. You can upgrade using the Azure portal or Azure CLI.
17+
18+
> [!IMPORTANT]
19+
> Once you upgrade, you can't revert to a lower SKU without deleting and reconfiguring Azure Bastion. Plan your upgrade carefully and consider starting with the tier that meets your long-term requirements.
20+
21+
To compare SKU features and determine which tier is right for you, see [Choose the right Azure Bastion SKU](bastion-sku-comparison.md).
1722

1823
[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
1924

20-
## View a SKU
25+
## Prerequisites
26+
27+
Before upgrading your Azure Bastion SKU, verify the following requirements:
28+
29+
- **Permissions**: You need Contributor or Owner role on the resource group containing your Bastion host.
30+
- **Subnet requirements** (Developer SKU upgrade only): A subnet named **AzureBastionSubnet** with a prefix of /26 or larger (/25, /24, etc.) must exist in your virtual network or be created before upgrading.
31+
- **Public IP** (Developer SKU upgrade only): A Standard SKU public IP address with static allocation is required unless you're deploying Premium SKU with private-only configuration.
32+
33+
## Pre-upgrade considerations
34+
35+
### What happens during an upgrade
2136

22-
To view the SKU for your bastion host, use the following steps.
37+
- **Duration**: The upgrade process takes approximately 10 minutes to complete.
38+
- **Active sessions**: Existing connections might be briefly interrupted during the upgrade. Plan the upgrade during a maintenance window when possible.
39+
40+
### Cost implications
41+
42+
Upgrading to a higher SKU increases your hourly costs. Review the [Azure Bastion pricing page](https://azure.microsoft.com/pricing/details/azure-bastion/) to understand the cost difference between tiers before upgrading.
43+
44+
## View your current SKU
45+
46+
# [Portal](#tab/portal)
2347

2448
1. Sign in to the [Azure portal](https://portal.azure.com).
25-
1. In the Azure portal, go to your bastion host.
26-
1. In the left pane, select **Configuration** to open the Configuration page. Click through the different Tier options. Notice that the SKU affects the available features you can select for your bastion host.
49+
1. Go to your Bastion host.
50+
1. In the left pane, select **Configuration**. Your current SKU is displayed in the **Tier** dropdown. You can also see which features are available for each tier by selecting different options.
51+
52+
# [Azure CLI](#tab/cli)
53+
54+
Run the following command to view your current Bastion SKU:
55+
56+
```azurecli
57+
az network bastion show --name <bastion-name> --resource-group <resource-group-name> --query sku.name --output tsv
58+
```
59+
60+
---
61+
62+
## Upgrade from Developer SKU
63+
64+
The Developer SKU uses shared infrastructure. When you upgrade to Basic, Standard, or Premium, Azure Bastion switches to dedicated infrastructure, which requires a dedicated subnet and public IP address.
65+
66+
# [Portal](#tab/portal)
67+
68+
1. **Create the AzureBastionSubnet** (if it doesn't exist):
69+
1. Go to your virtual network in the Azure portal.
70+
1. Select **Subnets** > **+ Subnet**.
71+
1. Enter **AzureBastionSubnet** as the name (this exact name is required).
72+
1. Enter a subnet address range of /26 or larger.
73+
1. Select **Save**.
74+
75+
1. **Upgrade the Bastion host**:
76+
1. Go to your Bastion host.
77+
1. Select **Configuration** in the left pane.
78+
1. For **Tier**, select your target SKU (Basic, Standard, or Premium).
79+
1. For **Public IP address**, select an existing Standard SKU public IP or create a new one.
80+
1. The **Subnet** field automatically populates with your AzureBastionSubnet.
81+
1. (Optional) Enable any additional features you want to configure.
82+
1. Select **Apply**.
83+
84+
The upgrade takes approximately 10 minutes to complete.
85+
86+
# [Azure CLI](#tab/cli)
87+
88+
1. **Create the AzureBastionSubnet** (if it doesn't exist):
2789

28-
## Upgrade from Bastion Developer
90+
```azurecli
91+
az network vnet subnet create \
92+
--resource-group <resource-group-name> \
93+
--vnet-name <vnet-name> \
94+
--name AzureBastionSubnet \
95+
--address-prefixes <subnet-prefix>/26
96+
```
2997

30-
When you upgrade from Bastion Developer to a dedicated deployment SKU, you need to create a public IP address and an Azure Bastion subnet.
98+
1. **Create a public IP address** (if you don't have one):
3199

32-
Use the following steps to upgrade to a higher SKU.
100+
```azurecli
101+
az network public-ip create \
102+
--resource-group <resource-group-name> \
103+
--name <public-ip-name> \
104+
--sku Standard \
105+
--allocation-method Static
106+
```
33107

34-
1. In the Azure portal, go to your virtual network and add a new subnet. The subnet must be named **AzureBastionSubnet** and must be /26 or larger (/25, /24 etc.). This subnet will be used exclusively by Azure Bastion.
35-
1. Next, go to the portal page for your **Bastion** host.
36-
1. On the **Configuration** page, for **Tier**, select the SKU that you want to upgrade to. Notice that the available features change, depending on the SKU you select.
37-
1. Create a new public IP address value unless you have already created one for your bastion host, in which case, select the value.
38-
1. Because you already created the AzureBastionSubnet, the **Subnet** field will automatically populate.
39-
1. You can add features at the same time you upgrade the SKU. You don't need to upgrade the SKU and then go back to add the features as a separate step.
40-
1. Select **Apply** to apply changes. The bastion host updates. This procedure takes about 10 minutes to complete.
108+
1. **Upgrade the Bastion host**:
41109

42-
## Upgrade from the Basic or Standard SKU
110+
```azurecli
111+
az network bastion update \
112+
--name <bastion-name> \
113+
--resource-group <resource-group-name> \
114+
--sku <Standard|Premium>
115+
```
43116

44-
Use the following steps to upgrade to a higher SKU.
117+
> [!NOTE]
118+
> If the update command fails when upgrading from Developer SKU, delete and recreate the Bastion host with the new SKU. The Developer to dedicated infrastructure transition isn't always supported via CLI update.
45119
46-
1. In the Azure portal, go to your Bastion host.
120+
---
121+
122+
## Upgrade from Basic or Standard SKU
123+
124+
Basic, Standard, and Premium SKUs all use the same dedicated infrastructure, so upgrading between these tiers requires only a configuration change.
125+
126+
# [Portal](#tab/portal)
127+
128+
1. Go to your Bastion host in the Azure portal.
129+
1. Select **Configuration** in the left pane.
130+
1. For **Tier**, select the higher SKU you want to upgrade to.
131+
1. (Optional) Enable any additional features available with the new SKU.
132+
1. Select **Apply**.
133+
134+
The upgrade takes approximately 10 minutes to complete.
135+
136+
# [Azure CLI](#tab/cli)
137+
138+
Run the following command to upgrade your Bastion SKU:
139+
140+
```azurecli
141+
az network bastion update \
142+
--name <bastion-name> \
143+
--resource-group <resource-group-name> \
144+
--sku <Standard|Premium>
145+
```
146+
147+
To enable features during the upgrade, add the appropriate parameters. For example, to enable native client support and IP-based connection:
148+
149+
```azurecli
150+
az network bastion update \
151+
--name <bastion-name> \
152+
--resource-group <resource-group-name> \
153+
--sku Standard \
154+
--enable-tunneling true \
155+
--enable-ip-connect true
156+
```
157+
158+
---
159+
160+
## Verify the upgrade
161+
162+
After the upgrade completes, verify that your Bastion host is functioning correctly:
163+
164+
# [Portal](#tab/portal)
165+
166+
1. Go to your Bastion host and select **Configuration**.
167+
1. Verify the **Tier** shows your new SKU.
168+
1. Check that your desired features are enabled.
169+
1. Test a connection to a VM to confirm connectivity.
170+
171+
# [Azure CLI](#tab/cli)
172+
173+
1. Verify the SKU was updated:
174+
175+
```azurecli
176+
az network bastion show \
177+
--name <bastion-name> \
178+
--resource-group <resource-group-name> \
179+
--query "{Name:name, SKU:sku.name, ProvisioningState:provisioningState}" \
180+
--output table
181+
```
182+
183+
1. Confirm the provisioning state shows **Succeeded**.
184+
185+
---
47186

48-
1. On the **Configuration** page, for **Tier**, select a higher SKU.
187+
## Troubleshooting
49188

50-
1. You can add features at the same time you upgrade the SKU. You don't need to upgrade the SKU and then go back to add the features as a separate step.
189+
| Issue | Possible cause | Solution |
190+
|-------|---------------|----------|
191+
| Upgrade fails to start | Insufficient permissions | Verify you have Contributor or Owner role on the resource group. |
192+
| Upgrade fails with subnet error | AzureBastionSubnet doesn't exist or is too small | Create a subnet named **AzureBastionSubnet** with /26 or larger prefix. |
193+
| Upgrade times out | Network or service issues | Wait a few minutes and check the Bastion host status. If still updating, wait for completion. If failed, try again. |
194+
| Features not available after upgrade | Feature not enabled during upgrade | Go to **Configuration** and enable the desired features. |
195+
| Can't connect after upgrade | Temporary service interruption | Wait a few minutes for the service to stabilize, then try again. |
51196

52-
1. Select **Apply** to apply changes. The bastion host updates. This procedure takes about 10 minutes to complete.
197+
If issues persist, check the [Azure Bastion FAQ](bastion-faq.md) or [contact Azure support](https://azure.microsoft.com/support/).
53198

54199
## Next steps
55200

56-
* See [Configuration settings](configuration-settings.md).
57-
* Read the [Bastion FAQ](bastion-faq.md).
201+
- [Choose the right Azure Bastion SKU](bastion-sku-comparison.md)
202+
- [Configure host scaling](configure-host-scaling.md)
203+
- [Configure session recording](session-recording.md) (Premium SKU)
204+
- [Deploy private-only Bastion](private-only-deployment.md) (Premium SKU)
205+
- [About Bastion configuration settings](configuration-settings.md)

0 commit comments

Comments
 (0)