[APIM] Rate limits in multi-region deployment

Author: gitName

articles/api-management/rate-limit-by-key-policy.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: reference
-ms.date: 07/23/2024
+ms.date: 03/31/2025
 ms.author: danlep
 ---
 
@@ -63,7 +63,9 @@ To understand the difference between rate limits and quotas, [see Rate limits an
 
 * [!INCLUDE [api-management-rate-limit-key-scope](../../includes/api-management-rate-limit-key-scope.md)]
 * [!INCLUDE [api-management-self-hosted-gateway-rate-limit](../../includes/api-management-self-hosted-gateway-rate-limit.md)] [Learn more](how-to-self-hosted-gateway-on-kubernetes-in-production.md#request-throttling)
-* When `increment-condition` or `increment-count` are defined using expressions, evaluation and increment of rate limit counter are postponed to end of outbound pipeline to allow for policy expressions based on the reponse. Limit exceeded condition is not evaluated at the same time in this case and will be evaluated on next incoming call. This leads to cases where `429 Too Many Requests` status code is returned 1 call later than usual.
+* When `increment-condition` or `increment-count` are defined using expressions, evaluation and increment of the rate limit counter are postponed to the end of outbound pipeline to allow for policy expressions based on the response. Limit exceeded condition is not evaluated at the same time in this case and will be evaluated on next incoming call. This leads to cases where `429 Too Many Requests` status code is returned 1 call later than usual.
+* In a [multi-region](api-management-howto-deploy-multi-region.md) deployment, this policy counts calls separately at each regional gateway in the deployment. The policy doesn't aggregate all call data for the instance. 
+
 
 
 ## Example

articles/api-management/rate-limit-policy.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: reference
-ms.date: 07/23/2024
+ms.date: 03/31/2025
 ms.author: danlep
 ---
 
@@ -87,6 +87,7 @@ To understand the difference between rate limits and quotas, [see Rate limits an
 * This policy can be used only once per policy definition.
 * This policy is only applied when an API is accessed using a subscription key.
 * [!INCLUDE [api-management-self-hosted-gateway-rate-limit](../../includes/api-management-self-hosted-gateway-rate-limit.md)] [Learn more](how-to-self-hosted-gateway-on-kubernetes-in-production.md#request-throttling)
+* In a [multi-region](api-management-howto-deploy-multi-region.md) deployment, this policy counts calls separately at each regional gateway in the deployment. The policy doesn't aggregate all call data for the instance. 
 
 
 ## Example

includes/api-management-multi-region-concepts.md

@@ -2,7 +2,7 @@
 author: dlepow
 ms.service: azure-api-management
 ms.topic: include
-ms.date: 02/12/2024
+ms.date: 03/31/2025
 ms.author: danlep
 ---
 
@@ -20,4 +20,6 @@ ms.author: danlep
 * If a region goes offline, API requests are automatically routed around the failed region to the next closest gateway.
 
 * If the primary region goes offline, the API Management management plane and developer portal become unavailable, but secondary regions continue to serve API requests using the most recent gateway configuration.
+
+* If configured, the [rate-limit](/azure/api-management/rate-limit-policy) and [rate-limit-by-key](/azure/api-management/rate-limit-by-key-policy) policies count calls separately at each regional gateway in the deployment. The policies don't aggregate all call data for the instance.