Skip to content

Commit e693dd2

Browse files
Merge pull request #313434 from MicrosoftDocs/main
Auto Publish – main to live - 2026-03-19 22:00 UTC
2 parents 43568a9 + 2d88d2c commit e693dd2

89 files changed

Lines changed: 595 additions & 596 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

articles/app-service/app-service-plan-manage.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.assetid: 4859d0d5-3e3c-40cc-96eb-f318b2c51a3d
66
ms.topic: how-to
77
ms.author: msangapu
88
author: msangapu-msft
9-
ms.date: 11/17/2025
9+
ms.date: 03/19/2026
1010
ms.update-cycle: 1095-days
1111
ms.custom: "UpdateFrequency3"
1212

@@ -102,6 +102,19 @@ When creating or manually scaling out an App Service Plan you may experience sit
102102

103103
The preview of App Service Plan Asynchronous enables you to request your target number of instances and the platform scales out to the target number, without you having to modify your original request and retrying. The platform scales to the number of available instances and then triggers the underlying platform to make more instances available. You can make use of this functionality during scale-out operations or at plan creation time. This functionality is supported for all Basic, Standard, and Premium pricing plans.
104104

105+
> [!NOTE]
106+
> This behavior is NOT configurable for App Service Plans created in App Service Environments. App Service Environments create and scale App Service Plans asynchronously by default.
107+
108+
### Scaling up or down App Service Plan SKUs
109+
110+
When using asynchronous scaling, it's possible to scale up or down to a larger or smaller SKU. During this type of operation, no other properties of the App Service Plan can be changed. Scaling up or down to a new SKU may fail if there aren't enough App Service Plan instances available to fully satisfy the request, this is to prevent your App Service Plan having fewer workers than requested.
111+
112+
If a scale up or down operation fails, you can either scale in or out within the current SKU or perform the operation with the minim number of acceptable workers and then scale out asynchronously to the desired target.
113+
114+
### Cancelling an asynchronous scaling operation
115+
116+
An in-progress asynchronous scale operation is canceled only when you explicitly change the TargetWorkerCount property. Changes to other App Service Plan properties don't cancel the operation, including changes to the SKU, or App Service Plan instance count. App Service Plan instance count changes that can't be completed synchronously are ignored unless the TargetWorkerCount is also changed. To explicitly cancel the scale operation, set the TargetWorkerCount to 0.
117+
105118
### [Scale-out (CLI)](#tab/asyncscaleout)
106119
```azurecli-interactive
107120
az appservice plan update -g <resourceGroupName> -n <App Service Plan Name> --async-scaling-enabled true --number-of-workers <number of workers to scale out to>
@@ -111,7 +124,6 @@ az appservice plan update -g <resourceGroupName> -n <App Service Plan Name> --as
111124
```azurecli-interactive
112125
az appservice plan create -g asyncasp -n asyncasplinuxexample --number-of-workers 25 --sku p1v3 --async-scaling-enabled true --location northeurope
113126
```
114-
115127
---
116128

117129
<a name="delete"></a>

articles/azure-functions/durable/durable-functions-error-handling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1328,7 +1328,7 @@ def orchestrator_function(context: df.DurableOrchestrationContext):
13281328
activity_task = context.call_activity('FlakyFunction')
13291329
timeout_task = context.create_timer(deadline)
13301330
1331-
winner = yield context.task_any(activity_task, timeout_task)
1331+
winner = yield context.task_any([activity_task, timeout_task])
13321332
if winner == activity_task:
13331333
timeout_task.cancel()
13341334
return True

articles/azure-functions/durable/durable-functions-http-features.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -194,6 +194,9 @@ public HttpResponseMessage httpStart(
194194

195195
---
196196

197+
> [!TIP]
198+
> If you have multiple HTTP-triggered starter functions in the same function app, configure a unique `route` for each function to avoid route conflicts. Using a parameterized route like `orchestrators/{functionName}` (as shown in several of the preceding examples) lets a single HTTP starter function start any orchestrator by name, which is often the simplest approach.
199+
197200
Starting an orchestrator function by using the HTTP-trigger functions shown previously can be done using any HTTP client. The following cURL command starts an orchestrator function named `DoWork`:
198201

199202
```bash

articles/azure-government/documentation-government-product-roadmap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.topic: conceptual
66
ms.author: russellkirk
77
author: krussell09
88
recommendations: false
9-
ms.date: 03/05/2026
9+
ms.date: 03/19/2026
1010
---
1111
# Microsoft Azure Government Product General Availability(GA) Roadmap
1212

@@ -241,7 +241,7 @@ For comprehensive information about compliance in Azure Government clouds, see [
241241
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Azure Translator | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: |
242242
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Azure Vision | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: |
243243
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Azure Vision - Face | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | Awaiting Review |
244-
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Content Safety | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | n/a |
244+
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Content Safety | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | Planned |
245245
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Foundry Agent Service | Forecasted | Forecasted | Forecasted | Forecasted |
246246
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Foundry Models | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | n/a |
247247
| Microsoft Graph | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: | :::image alt-text="GA" type="content" source="media/check-mark.svg" border="false"::: |
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"redirections": [
3+
{
4+
"redirect_url": "/azure/bastion/configure-host-scaling",
5+
"source_path_from_root": "/articles/bastion/configure-host-scaling-powershell.md",
6+
"redirect_document_id": true
7+
}
8+
]
9+
}

articles/bastion/TOC.yml

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -89,11 +89,7 @@
8989
- name: Platform
9090
items:
9191
- name: Configure host scaling
92-
items:
93-
- name: Azure portal
94-
href: configure-host-scaling.md
95-
- name: Azure PowerShell
96-
href: configure-host-scaling-powershell.md
92+
href: configure-host-scaling.md
9793
- name: Design architecture
9894
href: design-architecture.md
9995
- name: Availability zones and disaster recovery

articles/bastion/configuration-settings.md

Lines changed: 6 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -67,18 +67,9 @@ Refer to the table below for creating/using public IP addresses for zonal Bastio
6767

6868
## <a name="instance"></a>Instances and host scaling
6969

70-
An instance is an optimized Azure VM that is created when you configure Azure Bastion. It's fully managed by Azure and runs all of the processes needed for Azure Bastion. An instance is also referred to as a scale unit. You connect to client VMs via an Azure Bastion instance. When you configure Azure Bastion using the Basic SKU, two instances are created. If you use the Standard SKU or higher, you can specify the number of instances (with a minimum of two instances). This is called **host scaling**.
70+
An instance is an optimized Azure VM that is created when you configure Azure Bastion. Azure fully manages each instance for you. An instance is also referred to as a scale unit. You connect to client VMs via an Azure Bastion instance. When you configure Azure Bastion using the Basic SKU, two instances are created. If you use the Standard SKU or higher, you can specify the number of instances. This is called **host scaling**.
7171

72-
Each instance can support 20 concurrent RDP connections and 40 concurrent SSH connections for medium workloads (see [Azure subscription limits and quotas](../azure-resource-manager/management/azure-subscription-service-limits.md) for more information). The number of connections per instances depends on what actions you're taking when connected to the client VM. For example, if you're doing something data intensive, it creates a larger load for the instance to process. Once the concurrent sessions are exceeded, another scale unit (instance) is required.
73-
74-
Instances are created in the AzureBastionSubnet. To allow for host scaling, the AzureBastionSubnet should be /26 or larger. Using a smaller subnet limits the number of instances you can create. For more information about the AzureBastionSubnet, see the [subnets](#subnet) section in this article.
75-
76-
You can configure this setting using the following methods:
77-
78-
| Method | Value | Links | Requires Standard SKU or higher|
79-
| --- | --- | --- | ---|
80-
| Azure portal |Instance count | [How-to](configure-host-scaling.md)| Yes |
81-
| Azure PowerShell | ScaleUnit | [How-to](configure-host-scaling-powershell.md) | Yes |
72+
To configure host scaling, see [Configure host scaling](configure-host-scaling.md).
8273

8374
## <a name="ports"></a>Custom ports
8475

@@ -110,6 +101,7 @@ When a user without Azure credentials clicks a shareable link, a webpage opens t
110101

111102
## Next steps
112103

113-
For frequently asked questions, see the [Azure Bastion FAQ](bastion-faq.md).
114-
Choose the right Azure Bastion SKU for your needs by reading [Choose the right Azure Bastion SKUs to meet your needs](bastion-sku-comparison.md).
115-
Review the cost optimization recommendations for Azure Bastion in [Optimize Azure Bastion costs](cost-optimization.md).
104+
* Learn about [frequently asked questions for Azure Bastion](bastion-faq.md).
105+
* Learn about the different [Azure Bastion SKU tiers](bastion-sku-comparison.md) and choose the right one for your requirements.
106+
* Learn how to [optimize Azure Bastion costs](cost-optimization.md) while maintaining secure remote access.
107+
* Learn how to [add more instances (scale units) to Azure Bastion](configure-host-scaling.md).

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

Lines changed: 0 additions & 42 deletions
This file was deleted.
Lines changed: 41 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,61 @@
11
---
2-
title: 'Add scale units for host scaling: Azure portal'
2+
title: Configure host scaling
33
titleSuffix: Azure Bastion
44
description: Learn how to add more instances (scale units) to Azure Bastion.
55
author: abell
66
ms.service: azure-bastion
77
ms.topic: how-to
8-
ms.date: 03/31/2025
8+
ms.date: 03/13/2026
99
ms.author: abell
10-
# Customer intent: As someone with a networking background, I want to configure host scaling using the Azure portal.
10+
# Customer intent: As a network administrator, I want to configure scale units and understand what the impact it will be on my cloud environment.
1111

1212
---
1313

14-
# Configure host scaling using the Azure portal
14+
# Configure host scaling for Azure Bastion
1515

16-
This article helps you add more scale units (instances) to Azure Bastion to accommodate additional concurrent client connections. The steps in this article use the Azure portal. For more information about host scaling, see [Configuration settings](configuration-settings.md#instance). You can also configure host scaling using [PowerShell](configure-host-scaling-powershell.md).
16+
This article helps you configure host scaling for your Azure Bastion deployment. Host scaling lets you adjust the number of instances (scale units) to support more concurrent client connections.
17+
18+
> [!IMPORTANT]
19+
> Host scaling requires the Standard SKU tier or higher. Any changes to scale units disrupt active Bastion connections. Plan changes during maintenance windows.
20+
21+
## Considerations
22+
23+
Each instance can support 20 concurrent RDP connections and 40 concurrent SSH connections for medium workloads (see [Azure subscription limits and quotas](../azure-resource-manager/management/azure-subscription-service-limits.md) for more information). The number of connections per instance depends on what actions you're taking when connected to the client VM. For example, if you're transferring large files or streaming media, data-intensive tasks reduce the number of concurrent connections your instance can handle. When concurrent sessions exceed the instance limit, you need to add another scale unit to handle additional connections.
24+
25+
Instances are created in the AzureBastionSubnet. To allow for host scaling, the AzureBastionSubnet should be /26 or larger. Using a smaller subnet limits the number of instances you can create. For more information about the AzureBastionSubnet, see the [Azure Bastion subnet](configuration-settings.md#subnet) section.
26+
27+
> [!IMPORTANT]
28+
> Host scaling requires the Standard SKU tier or higher. Any changes to scale units will disrupt active Bastion connections.
1729
1830
## Configuration steps
1931

32+
# [Azure portal](#tab/portal)
33+
2034
1. Sign in to the [Azure portal](https://portal.azure.com).
21-
1. In the Azure portal, go to your Bastion host.
22-
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.
35+
1. Go to your Bastion host.
36+
1. On the **Configuration** page, for **SKU**, verify the SKU is **Standard** or higher. If the SKU is Basic, select a higher SKU.
37+
1. Adjust the **Instance count**. Each instance is a scale unit.
2338
1. Select **Apply** to apply changes.
2439

25-
>[!NOTE]
26-
> Any changes to the host scale units will disrupt active bastion connections.
27-
>
40+
# [PowerShell](#tab/powershell)
41+
42+
1. Get the target Bastion resource. Use the following example, modifying the values as needed.
43+
44+
```azurepowershell-interactive
45+
$bastion = Get-AzBastion -Name bastion -ResourceGroupName bastion-rg
46+
```
47+
48+
1. Set the target scale unit, also known as "instance count". In the following example, the scale units are set to 5.
49+
50+
```azurepowershell-interactive
51+
$bastion.ScaleUnit = 5
52+
Set-AzBastion -InputObject $bastion
53+
```
54+
55+
1. Confirm **Y** to overwrite the resource. After the resource is overwritten, the specified value is shown in the output for **Scale Units**.
56+
57+
---
2858

2959
## Next steps
3060

31-
For more information about configuration settings, see [Azure Bastion configuration settings](configuration-settings.md).
61+
* Learn about the [available configuration settings for Azure Bastion](configuration-settings.md).

articles/cost-management-billing/manage/understand-vm-reservation-charges.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.reviewer: primittal
66
ms.service: cost-management-billing
77
ms.subservice: reservations
88
ms.topic: conceptual
9-
ms.date: 01/15/2026
9+
ms.date: 03/19/2026
1010
ms.author: primittal
1111
---
1212

0 commit comments

Comments
 (0)