Skip to content

Commit fb1fecd

Browse files
Processed review feedback
1 parent 01363e7 commit fb1fecd

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/service-bus-messaging/service-bus-geo-replication.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,8 @@ This feature allows promoting any secondary region to primary, at any time. Prom
3333
> - Large message support.
3434
> - When you have Event Grid integration enabled on a namespace that is using Geo-Replication, note the following.
3535
> - Event Grid replicates to the [geo-paired location](/azure/reliability/reliability-event-grid#set-up-disaster-recovery), not the secondary region set up for geo-replication.
36-
> - [Promotion](#promotion-flow) of a secondary region for Service Bus doesn't initiate a failover of Event Grid.
37-
> - Consequently, after promotion, Service Bus is now running in the new primary region, however Event Grid is still running in the initial primary region.
38-
> - If the initial primary region is [removed](#delete-secondary-region) from the Geo-Replication configuration, this breaks the EG integration.
36+
> - [Promotion](#promotion-flow) of a secondary region for Service Bus doesn't initiate a failover of Event Grid. Consequently, after promotion, Service Bus is now running in the new primary region, however Event Grid is still running in the initial primary region.
37+
> - If the initial primary region is [removed](#delete-secondary-region) from the Geo-Replication configuration, this breaks the Event Grid integration.
3938
4039
## Scenarios
4140
The Geo-replication feature can be used to implement different scenarios, as described here.
@@ -184,9 +183,9 @@ A promotion is triggered manually by the customer (either explicitly through a c
184183
After the promotion is initiated:
185184

186185
1. The hostname is updated to point to the secondary region, which can take up to a few minutes.
187-
> [!NOTE]
188-
> You can check the current primary region by initiating a ping command:
189-
> ping *your-namespace-fully-qualified-name*
186+
> [!NOTE]
187+
> You can check the current primary region by initiating a ping command:
188+
> ping *your-namespace-fully-qualified-name*
190189
191190
1. Clients automatically reconnect to the secondary region.
192191

0 commit comments

Comments
 (0)