updated tier to sku.

Author: Abdullah Bell

articles/bastion/bastion-connect-vm-scale-set.md

@@ -25,7 +25,7 @@ This section helps you connect to your virtual machine scale set.
 1. Open the [Azure portal](https://portal.azure.com) and go to **Virtual machine scale sets**. To open the scale sets instances page, click the scale set that contains the instance that you want to connect to.
 1. On the **Scale set instance** page, click the instance that you want to connect to. This opens the page for the instance.
 1. On the instance page, select **Connect** at the top of the page, then choose **Bastion** from the dropdown.
-1. On the **Bastion** page, fill in the required settings. The settings you can select depend on the virtual machine to which you're connecting, and the [Bastion SKU](bastion-sku-comparison.md) tier that you're using. For more information about settings, see [Bastion configuration settings](configuration-settings.md).
+1. On the **Bastion** page, fill in the required settings. The settings you can select depend on the virtual machine to which you're connecting, and the [Bastion SKU](bastion-sku-comparison.md) that you're using. For more information about settings, see [Bastion configuration settings](configuration-settings.md).
 
 1. After filling in the values on the Bastion page, select **Connect** to connect to the instance.
 

articles/bastion/bastion-connect-vm-ssh-linux.md

@@ -25,8 +25,8 @@ Make sure that you have set up an Azure Bastion host for the virtual network in
 
 The connection settings and features that are available depend on the Bastion SKU you're using. Make sure your Bastion deployment is using the required SKU.
 
-* To see the available features and settings per SKU tier, see the [SKUs and features](bastion-overview.md#sku) section of the Bastion overview article.  
-* To check the SKU tier of your Bastion deployment and upgrade if necessary, see [Upgrade a Bastion SKU](upgrade-sku.md).
+* To see the available features and settings per SKU, see the [SKUs and features](bastion-overview.md#sku) section of the Bastion overview article.  
+* To check the SKU of your Bastion deployment and upgrade if necessary, see [Upgrade a Bastion SKU](upgrade-sku.md).
 
 ### Required roles
 
@@ -48,7 +48,7 @@ In order to connect to the Linux VM via SSH, you must have the following ports o
 
 1. In the Azure portal, go to the virtual machine to which you want to connect. At the top of the virtual machine **Overview** page, select **Connect**, then select **Connect via Bastion** from the dropdown. This opens the **Bastion** page. You can go to the Bastion page directly in the left pane.
 
-1. On the **Bastion** page, the settings that you can configure depend on the Bastion [SKU](bastion-overview.md#sku) tier that your bastion host has been configured to use.
+1. On the **Bastion** page, the settings that you can configure depend on the Bastion [SKU](bastion-overview.md#sku) that your bastion host has been configured to use.
 
    * If you're using a SKU higher than the Basic SKU, **Connection Settings** values (ports and protocols) are visible and can be configured.
 

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

@@ -19,7 +19,7 @@ Once you deploy Bastion to your virtual network, you can connect to your VMs via
 
 :::image type="content" source="./media/create-host/host-architecture.png" alt-text="Diagram showing Azure Bastion architecture." lightbox="./media/create-host/host-architecture.png":::
 
-In this article, you create a virtual network (if you don't already have one), deploy Azure Bastion using PowerShell, and connect to a VM. The examples show Bastion deployed using the Standard SKU tier, but you can use a different Bastion SKU, depending on the features you'd like to use. For more information, see [Bastion SKUs](bastion-sku-comparison.md).
+In this article, you create a virtual network (if you don't already have one), deploy Azure Bastion using PowerShell, and connect to a VM. The examples show Bastion deployed using the Standard SKU, but you can use a different Bastion SKU, depending on the features you'd like to use. For more information, see [Bastion SKUs](bastion-sku-comparison.md).
 
 You can also deploy Bastion by using the following other methods:
 
@@ -63,7 +63,7 @@ You can use the following example values when creating this configuration, or yo
 | Subnet Name | FrontEnd |
 | Subnet Name | AzureBastionSubnet|
 | AzureBastionSubnet addresses | A subnet within your virtual network address space with a subnet mask /26 or larger.<br> For example, 10.1.1.0/26.  |
-| Tier/SKU | Standard |
+| SKU | Standard |
 | Public IP address |  Create new |
 | Public IP address name | VNet1-ip  |
 | Public IP address SKU |  Standard  |

articles/bastion/bastion-overview.md

@@ -37,7 +37,7 @@ Azure Bastion offers four SKU tiers:
 * **Premium**: Includes all Standard features plus session recording for compliance and private-only deployment.
 * **Standard**: Includes all Basic features plus scalability and advanced features (native client, shareable links, IP-based connections, custom ports, file transfer).
 * **Basic**: Dedicated deployment with fixed capacity for production environments with moderate connection requirements.
-* **Developer**: Free tier using shared infrastructure recommended for development and testing. Supports one VM at a time. Available in select regions.
+* **Developer**: Free SKU using shared infrastructure recommended for development and testing. Supports one VM at a time. Available in select regions.
 
 For a complete feature comparison and capacity details, see [Choose the right Azure Bastion SKU](bastion-sku-comparison.md).
 

articles/bastion/bastion-sku-comparison.md

@@ -6,7 +6,7 @@ ms.author: abell
 ms.service: azure-bastion
 ms.topic: concept-article
 ms.date: 11/24/2025
-# Customer intent: As a cloud administrator, I want to compare Azure Bastion SKU tiers and understand their features, so that I can select the appropriate tier for my organization's secure remote access requirements.
+# Customer intent: As a cloud administrator, I want to compare Azure Bastion SKU tiers and understand their features, so that I can select the appropriate SKU for my organization's secure remote access requirements.
 ---
 
 # Choose the right Azure Bastion SKU to meet your needs
@@ -58,7 +58,7 @@ Compare the features across all four Azure Bastion SKU tiers:
 
 ## Performance and scalability
 
-The following table shows the capacity and scaling characteristics of each SKU tier:
+The following table shows the capacity and scaling characteristics of each SKU:
 
 | Metric | Developer | Basic | Standard | Premium |
 |--------|-----------|----------|---------|---------|

articles/bastion/configure-host-scaling-powershell.md

@@ -34,8 +34,8 @@ This article helps you add more scale units (instances) to Azure Bastion to acco
 1. Confirm "Y" to overwrite the resource. After the resource is overwritten, the specified value is shown in the output for "Scale Units".
 
    >[!NOTE]
-   > Host scaling instance count requires Standard SKU tier or higher. Any changes to the host scale units will disrupt active bastion connections.
-   >s
+   > Host scaling instance count requires Standard SKU or higher. Any changes to the host scale units will disrupt active bastion connections.
+   >
 
 ## Next steps
 

articles/bastion/configure-host-scaling.md

@@ -19,7 +19,7 @@ This article helps you add more scale units (instances) to Azure Bastion to acco
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. In the Azure portal, go to your Bastion host.
-1. Host scaling instance count requires Standard SKU tier or higher. On the **Configuration** page, for **Tier**, verify the tier is Standard or higher. If the SKU tier is Basic, select a higher SKU. To configure scaling, adjust the instance count. Each instance is a scale unit.
+1. Host scaling instance count requires Standard SKU or higher. On the **Configuration** page, for **SKU**, verify the SKU is Standard or higher. If the SKU is Basic, select a higher SKU. To configure scaling, adjust the instance count. Each instance is a scale unit.
 1. Select **Apply** to apply changes.
 
    >[!NOTE]

articles/bastion/connect-ip-address.md

@@ -19,7 +19,7 @@ IP-based connection lets you connect to your on-premises, non-Azure, and Azure v
 :::image type="content" source="./media/connect-ip-address/architecture.png" alt-text="Diagram that shows the Azure Bastion architecture." lightbox="./media/connect-ip-address/architecture.png":::
 
 > [!NOTE]
-> This configuration requires the Standard SKU tier or higher for Azure Bastion. To upgrade, see [Upgrade a SKU](upgrade-sku.md).
+> This configuration requires the Standard SKU or higher for Azure Bastion. To upgrade, see [Upgrade a SKU](upgrade-sku.md).
 >
 
 **Limitations**
@@ -49,7 +49,7 @@ Before you begin these steps, verify that you have the following environment set
 
 1. In the Azure portal, go to your Bastion deployment.
 
-1. IP based connection requires the Standard SKU tier or higher. On the **Configuration** page, for **Tier**, verify the tier is set to the **Standard** SKU or higher. If the tier is set to the Basic SKU, select a higher SKU from the dropdown.
+1. IP based connection requires the Standard SKU or higher. On the **Configuration** page, for **SKU**, verify the SKU is set to the **Standard** SKU or higher. If the SKU is set to the Basic SKU, select a higher SKU from the dropdown.
 
 1. To enable **IP based connection**, select **IP based connection**.
 

articles/bastion/cost-optimization.md

@@ -26,7 +26,7 @@ Start with the recommended approaches and justify the benefits for your remote a
 
 Azure Bastion uses a dual-component pricing model that combines hourly SKU charges with outbound data transfer costs. Understanding both components helps you optimize total cost of ownership.
 
-**Hourly SKU charges**: Each Bastion deployment incurs hourly charges based on the selected SKU tier, billed continuously from deployment regardless of usage. Additional instances for host scaling have lower hourly rates than the base SKU deployment, making scaling more cost-effective when needed.
+**Hourly SKU charges**: Each Bastion deployment incurs hourly charges based on the selected SKU, billed continuously from deployment regardless of usage. Additional instances for host scaling have lower hourly rates than the base SKU deployment, making scaling more cost-effective when needed.
 
 **Data transfer costs**: Outbound data transfer from Azure Bastion to your client is charged in tiers, with the first 5 GB per month free. Transfer rates decrease at higher volume tiers, rewarding consolidation. Inbound data transfer to Bastion isn't charged.
 
@@ -51,7 +51,7 @@ Azure Bastion offers four SKU tiers with different cost profiles: Developer (fre
 
 | Recommendation | Cost Optimization Benefit |
 |---|---|
-| **Maximize Developer SKU usage** for all development and test environments where single-VM access is acceptable. | Developer SKU eliminates 100% of Bastion costs for nonproduction workloads. No hourly charges, no data transfer fees. Use this tier to reserve budget for production deployments. See [Deploy Bastion from the Azure portal](quickstart-host-portal.md). |
+| **Maximize Developer SKU usage** for all development and test environments where single-VM access is acceptable. | Developer SKU eliminates 100% of Bastion costs for nonproduction workloads. No hourly charges, no data transfer fees. Use this SKU to reserve budget for production deployments. See [Deploy Bastion from the Azure portal](quickstart-host-portal.md). |
 | **Start with Basic SKU** for production environments unless advanced features are required. Upgrade only when you identify specific feature gaps. | Basic SKU minimizes production costs while providing essential capabilities (peering, Kerberos, concurrent connections). Prevents over-provisioning by deploying only needed features. Evaluate actual usage before committing to higher-cost tiers. |
 | **Select Standard SKU** when cost analysis justifies advanced features. Key cost drivers: scaling needs (>2 instances), native client requirements, or operational efficiency from shareable links. | Standard SKU enables cost-effective scaling through host scaling (2-50 instances) with incremental pricing. Variable costs align with actual demand. Advanced features can reduce operational overhead that offsets higher hourly rates. |
 | **Choose Premium SKU** when compliance requirements mandate session recording or when Standard-to-Premium cost difference is negligible compared to total infrastructure spend. | Premium adds minimal cost over Standard while future-proofing deployments. Session recording eliminates need for third-party audit solutions. Private-only deployment can reduce networking costs in highly restricted environments. |
@@ -80,7 +80,7 @@ Get the most value from your Bastion investments by using included features effi
 | **Implement native client support** (Standard SKU and higher) for SSH and RDP connections to improve user experience and reduce browser overhead. | Native client support enables users to connect using local SSH/RDP clients, providing better performance and familiarity. This reduces browser resource consumption and improves connection quality. See [Connect using native client](native-client.md). |
 | **Configure host scaling** (Standard and Premium SKUs) to match instance count with actual concurrent session requirements based on usage patterns. | Dynamic scaling ensures you maintain adequate capacity during peak usage while avoiding over-provisioning during low-demand periods. Each instance supports 20 concurrent RDP and 40 concurrent SSH connections, allowing precise capacity planning. See [Configure host scaling](configure-host-scaling.md). |
 | **Leverage availability zones** where available to improve resilience without deploying redundant Bastion resources across regions. | Zone-redundant deployment provides high availability within a single Bastion resource. You get improved reliability without the cost of multiple regional deployments. See [Bastion and availability zones](/azure/reliability/reliability-bastion). |
-| **Optimize data transfer patterns** by consolidating Bastion deployments and being mindful of outbound data transfer volumes. | The first 5 GB of outbound data transfer per month is free across all your Bastion resources. Consolidating multiple small deployments into fewer larger ones helps you maximize this free tier. Higher data transfer volumes benefit from tiered pricing with decreasing rates at scale. |
+| **Optimize data transfer patterns** by consolidating Bastion deployments and being mindful of outbound data transfer volumes. | The first 5 GB of outbound data transfer per month is free across all your Bastion resources. Consolidating multiple small deployments into fewer larger ones helps you maximize this free SKU. Higher data transfer volumes benefit from tiered pricing with decreasing rates at scale. |
 
 ## Monitor and optimize over time
 
@@ -91,9 +91,9 @@ Remote access needs change as your infrastructure evolves. Set up continuous mon
 | **Configure cost alerts** when Bastion spending approaches predefined budget thresholds. | Proactive notifications prevent budget overruns and enable timely adjustments to deployment strategy. You can respond to cost increases before they impact other initiatives. To create cost alerts, see [Monitor usage and spending with cost alerts](/azure/cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending). |
 | **Conduct quarterly reviews** of Bastion deployments and their usage patterns to identify optimization opportunities. | Regular reviews ensure investments remain aligned with business priorities. You can identify underutilized deployments, consolidation opportunities, or SKU downgrade candidates based on actual feature usage. |
 | **Monitor session patterns** and connection usage to optimize instance counts and identify unused deployments. Use [diagnostic logs](diagnostic-logs.md) and [Azure Monitor metrics](monitor-bastion-reference.md). | Understanding actual usage patterns enables data-driven scaling decisions. You can adjust instance counts based on real session data rather than theoretical requirements, and identify deployments that can be decommissioned. |
-| **Track data transfer costs** alongside hourly SKU charges to understand your complete Bastion spending profile. | Data transfer costs can be significant for high-usage deployments. Monitoring both cost components helps identify optimization opportunities, such as consolidating deployments to maximize free tier benefits or optimizing connection patterns to reduce outbound data transfer. |
+| **Track data transfer costs** alongside hourly SKU charges to understand your complete Bastion spending profile. | Data transfer costs can be significant for high-usage deployments. Monitoring both cost components helps identify optimization opportunities, such as consolidating deployments to maximize free SKU benefits or optimizing connection patterns to reduce outbound data transfer. |
 | **Track deployment return on investment (ROI)** using [cost management best practices](/azure/cost-management-billing/costs/cost-analysis-common-uses) to measure value and implement lifecycle management. | ROI measurement demonstrates deployment value and guides future investment decisions. Regular cleanup of unused or underutilized Bastion resources prevents spending growth that doesn't align with business value while freeing budget for higher-priority networks. |
-| **Review feature utilization** to ensure you're on the appropriate SKU tier for your actual usage patterns. | Feature usage analysis identifies opportunities to downgrade SKUs when advanced capabilities aren't being used. Moving from Premium to Standard, or Standard to Basic when appropriate, can reduce costs while maintaining necessary access. However, SKU downgrades require deleting and recreating Bastion. See [View or upgrade a SKU](upgrade-sku.md). |
+| **Review feature utilization** to ensure you're on the appropriate SKU for your actual usage patterns. | Feature usage analysis identifies opportunities to downgrade SKUs when advanced capabilities aren't being used. Moving from Premium to Standard, or Standard to Basic when appropriate, can reduce costs while maintaining necessary access. However, SKU downgrades require deleting and recreating Bastion. See [View or upgrade a SKU](upgrade-sku.md). |
 
 ## Next steps
 

articles/bastion/create-host-cli.md

@@ -72,7 +72,7 @@ This section helps you deploy Azure Bastion using Azure CLI.
 
 1. Use [az network bastion create](/cli/azure/network/bastion#az-network-bastion-create) to create a new Azure Bastion resource for your virtual network. It takes about 10 minutes for the Bastion resource to create and deploy.
 
-   The following example deploys Bastion using the **Basic** SKU tier. You can also deploy using other SKUs. The SKU determines the features that your Bastion deployment supports. If you don't specify a SKU in your command, the SKU defaults to Standard. For more information, see [Bastion SKUs](bastion-sku-comparison.md).
+   The following example deploys Bastion using the **Basic** SKU. You can also deploy using other SKUs. The SKU determines the features that your Bastion deployment supports. If you don't specify a SKU in your command, the SKU defaults to Standard. For more information, see [Bastion SKUs](bastion-sku-comparison.md).
 
    ```azurecli-interactive
    az network bastion create --name VNet1-bastion --public-ip-address VNet1-ip --resource-group TestRG1 --vnet-name VNet1 --location eastus --sku Basic