Skip to content

Commit 79e717b

Browse files
authored
Update geo-replication.md
1 parent e66ca20 commit 79e717b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/event-hubs/geo-replication.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ These features shouldn't be confused with Availability Zones. Both geographic re
2121
> - This feature is currently in public preview, and as such shouldn't be used in production scenarios.
2222
> - The following regions are currently supported in the public preview.
2323
>
24-
> | US | Europe |
25-
> |------------------|---------------|
26-
> | Central US EUAP | Italy North |
27-
> | | Spain Central |
28-
> | | Norway East |
24+
> | US | Europe | APAC |
25+
> |------------------|---------------|---------------|
26+
> | Central US EUAP | Italy North | Australia Central |
27+
> | Canada Central | Spain Central | Australia East |
28+
> | Canada East | Norway East ||
2929
3030

3131
## Metadata disaster recovery vs. Geo-replication of metadata and data
@@ -152,4 +152,4 @@ Clients that use the Event Hubs SDK need to upgrade to the April 2024 version of
152152
Event Hubs dedicated clusters are priced independently of geo-replication. Use of geo-replication with Event Hubs dedicated requires you to have at least two dedicated clusters in separate regions. The dedicated clusters used as secondary instances for geo-replication can be used for other workloads. There's a charge for geo-replication based on the published bandwidth * the number of secondary regions. The geo-replication charge is waived in early public preview.
153153

154154
## Related content
155-
To learn how to use the Geo-replication feature, see [Use Geo-replication](use-geo-replication.md).
155+
To learn how to use the Geo-replication feature, see [Use Geo-replication](use-geo-replication.md).

0 commit comments

Comments
 (0)