Skip to content

Commit 03ee6ad

Browse files
update link to how to
1 parent 8c56fd1 commit 03ee6ad

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-app-configuration/concept-geo-replication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Replicating your configuration store adds the following benefits:
2222
- **Redistribution of Request Limits:** You can customize in code which replica endpoint your application uses letting you distribute your request load to avoid exhausting request limits. For example, if your applications run in multiple regions and only send requests to one region, you may begin exhausting App Configuration request limits. You can help redistribute this load by creating replicas in the regions your applications are running in. Each replica has isolated request limits, equal in size to the request limits of the origin. Exhausting the request limits in one replica has no impact on the request limits in another replica.
2323
- **Regional Compartmentalization:** Accessing multiple regions can improve latency between your application and configuration store, leading to faster request responses and better performance if an application sends requests to its closest replica. Specifying replica access also allows you to limit data storage and flow between different regions based on your preferences.
2424

25-
Follow our [how-to to enable geo-replication](./howto-geo-replication.md) in your configuration store.
25+
To enable this feature in your store, reference the [how-to to enable geo-replication document](./howto-geo-replication.md).
2626

2727
## Sample use case
2828

0 commit comments

Comments
 (0)