Skip to content

Commit 4d9cfcf

Browse files
authored
Merge pull request #291108 from dlepow/azlb
[APIM] Scale units in AZs behavior
2 parents e86bf23 + 3a62fce commit 4d9cfcf

File tree

3 files changed

+15
-3
lines changed

3 files changed

+15
-3
lines changed

articles/api-management/high-availability.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,7 @@ Enabling [zone redundancy](../reliability/migrate-api-mgt.md) for an API Managem
3535

3636
When you enable zone redundancy in a region, consider the number of API Management scale [units](upgrade-and-scale.md) that need to be distributed. Minimally, configure the same number of units as the number of availability zones, or a multiple so that the units are distributed evenly across the zones. For example, if you select 3 availability zones in a region, you could have 3 units so that each zone hosts one unit.
3737

38-
> [!NOTE]
39-
> Use [capacity metrics](api-management-capacity.md) and your own testing to decide the number of scale units that will provide the gateway performance for your needs. Learn more about [scaling and upgrading](upgrade-and-scale.md) your service instance.
38+
[!INCLUDE [api-management-az-notes](../../includes/api-management-az-notes.md)]
4039

4140
## Multi-region deployment
4241

articles/reliability/migrate-api-mgt.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ There are no downtime requirements for any of the migration options.
4444

4545
* When you're enabling availability zones in a region, you configure API Management scale [units](../api-management/upgrade-and-scale.md) that you can distribute evenly across the zones. For example, if you configure two zones, you can configure two units, four units, or another multiple of two units.
4646

47-
Adding units incurs additional costs. For details, see [API Management pricing](https://azure.microsoft.com/pricing/details/api-management/).
47+
[!INCLUDE [api-management-az-notes](../../includes/api-management-az-notes.md)]
4848

4949
* If you configured autoscaling for your API Management instance in the primary location, you might need to adjust your autoscale settings after configuring availability zones. The number of API Management units in autoscale rules and limits must be a multiple of the number of zones.
5050

includes/api-management-az-notes.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
author: dlepow
3+
ms.service: azure-api-management
4+
ms.topic: include
5+
ms.date: 11/26/2024
6+
ms.author: danlep
7+
---
8+
9+
> [!NOTE]
10+
> Use [capacity metrics](../articles/api-management/api-management-capacity.md) and your own testing to decide the number of scale units that will provide the gateway performance for your needs. Adding units incurs additional costs. Learn more about [scaling and upgrading](../articles/api-management/upgrade-and-scale.md) your service instance.
11+
12+
> [!NOTE]
13+
> When availability zones are configured for your API Management instance, under normal operating conditions all scale units in all configured zones are active and serve gateway traffic.

0 commit comments

Comments
 (0)