Skip to content

Commit d39f113

Browse files
committed
Acrolinx
1 parent 17174fc commit d39f113

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/business-continuity-disaster-recovery.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ For more information, see [Shared responsibility for reliability](/azure/reliabi
4545

4646
Microsoft Sentinel uses Microsoft's best practices for resiliency, safe deployment, and BCDR with Azure Availability Zones (AZs).
4747

48-
To support BCDR in case of a regional outage, Microsoft Sentinel uses a customer-enabled BCDR approach, which means customers are responsible for setting up disaster recovery. To ensure continuous business operations, customers must configure their Microsoft Sentinel environment in an active-active (mirrored) fashion across the two paired regions relevant to them, depending on the cloud environment.
48+
To support BCDR in a regional outage, Microsoft Sentinel uses a customer-enabled BCDR approach, which means customers are responsible for setting up disaster recovery. To ensure continuous business operations, customers must configure their Microsoft Sentinel environment in an active-active (mirrored) fashion across the two paired regions relevant to them, depending on the cloud environment.
4949

5050
Customer-enabled BCDR involves:
5151

@@ -67,7 +67,7 @@ The following table describes the recommended actions for setting up BCDR in dif
6767

6868
For more information, see [Geographical availability and data residency in Microsoft Sentinel](geographical-availability-data-residency.md).
6969

70-
The following geographical regions are not currently supported for the customer-enabled BCDR approach described in this article:
70+
The following geographical regions aren't currently supported for the customer-enabled BCDR approach described in this article:
7171

7272
- EU customers due to EUDB compliance limitations.
7373
- Israel.

0 commit comments

Comments
 (0)