Merge pull request #310807 from shpathak-msft/patch-14

prmerger-automator[bot] · web-flow · commit 7b3f58a8b8c3 · 2026-01-28T01:07:59.000Z
Revise geo-replication data transfer and sync notes
diff --git a/articles/redis/how-to-active-geo-replication.md b/articles/redis/how-to-active-geo-replication.md
@@ -18,9 +18,10 @@ In this article, you learn how to configure an active geo-replicated cache using
 Active geo-replication groups up to five instances of Azure Managed Redis into a single cache that spans across Azure regions. All instances act as the local, primary caches. An application decides which instance or instances to use for read and write requests.
 
 > [!NOTE]
-> Data transfer between Azure regions is charged at standard [bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/).
+> * Using active geo-replication produces data transfer between Azure regions. These bandwidth charges are currently absorbed by Azure Managed Redis and not passed on to customers.
+> Billing can change in the future. For more information, see [bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/).
 >
-> Data sync among replicas follows eventual consistency. The service does not provide SLA on sync time. Please design your system without relying on the  timeliness of data sync.
+> * Data sync among replicas follows eventual consistency. The service does not provide SLA on sync time. Please design your system without relying on the timeliness of data sync.
 >
 
 ## How active geo-replication works

Original file line number	Diff line number	Diff line change
`@@ -18,9 +18,10 @@ In this article, you learn how to configure an active geo-replicated cache using`
`18`	`18`	`Active geo-replication groups up to five instances of Azure Managed Redis into a single cache that spans across Azure regions. All instances act as the local, primary caches. An application decides which instance or instances to use for read and write requests.`
`19`	`19`
`20`	`20`	`> [!NOTE]`
`21`		`-> Data transfer between Azure regions is charged at standard [bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/).`
	`21`	`+> * Using active geo-replication produces data transfer between Azure regions. These bandwidth charges are currently absorbed by Azure Managed Redis and not passed on to customers.`
	`22`	`+> Billing can change in the future. For more information, see [bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/).`
`22`	`23`	`>`
`23`		`-> Data sync among replicas follows eventual consistency. The service does not provide SLA on sync time. Please design your system without relying on the timeliness of data sync.`
	`24`	`+> * Data sync among replicas follows eventual consistency. The service does not provide SLA on sync time. Please design your system without relying on the timeliness of data sync.`
`24`	`25`	`>`
`25`	`26`
`26`	`27`	`## How active geo-replication works`