Skip to content

Commit d93515d

Browse files
committed
PR review updates
1 parent 7a068b6 commit d93515d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/cognitive-services/disaster-recovery.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,12 @@ ms.author: pafarley
1313

1414
# Cross–region disaster recovery
1515

16-
## Feature overview
17-
18-
One of the first decisions every Cognitive Service customer makes is which region to create their resource in. The choice of region provides customers with the benefits of regional compliance by enforcing data residency requirements. Cognitive Services are available in [multiple geographies](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=cognitive-services) to ensure customers across the world are supported.
16+
One of the first decisions every Cognitive Service customer makes is which region to create their resource in. The choice of region provides customers with the benefits of regional compliance by enforcing data residency requirements. Cognitive Services is available in [multiple geographies](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=cognitive-services) to ensure customers across the world are supported.
1917

2018
It's rare, but possible, to encounter a network issue that affects an entire region. If your solution needs to always be available, then you should design it to either fail-over into another region or split the workload between two or more regions. Both approaches require at least two resources in different regions and the ability to sync data between them.
2119

20+
## Feature overview
21+
2222
The cross-region disaster recovery feature, also known as Single Resource Multiple Region (SRMR), enables this scenario by allowing you to distribute traffic or copy custom models to multiple resources which can exist in any supported geography.
2323

2424
## SRMR business scenarios
@@ -44,10 +44,10 @@ If you use Priority or Weighted traffic manager profiles, your configuration wil
4444
1. Sign in to the [Azure portal](https://portal.azure.com).
4545
1. Navigate to your resource's page.
4646
1. Under the **Resource Management** section on the left pane, select the Regions tab and choose a routing method.
47-
:::image type="content" source="media/disaster-recovery/routing-method.png" alt-text="Screenshot of the routing method select menu in the Azure portal.":::
47+
:::image type="content" source="media/disaster-recovery/routing-method.png" alt-text="Screenshot of the routing method select menu in the Azure portal." lightbox="media/disaster-recovery/routing-method.png":::
4848
1. Select the **Add Region** link.
4949
1. On the **Add Region** pop-up screen, set up additional regions for your resources.
50-
:::image type="content" source="media/disaster-recovery/add-regions.png" alt-text="Screenshot of the Add Region popup in the Azure portal.":::
50+
:::image type="content" source="media/disaster-recovery/add-regions.png" alt-text="Screenshot of the Add Region popup in the Azure portal." lightbox="media/disaster-recovery/add-regions.png":::
5151
1. Save your changes.
5252

5353
## See also

0 commit comments

Comments
 (0)