Skip to content

Commit 2a3c1ff

Browse files
authored
Apply suggestions from code review
1 parent 1e41ca6 commit 2a3c1ff

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/reliability/reliability-data-factory.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,9 @@ To prepare for a failover, there might be some extra considerations, depending o
168168

169169
- You can configure the *Azure IR* to automatically resolve the region that it uses. If the region is set to *auto resolve* and there's an outage in the primary region, the Azure IR automatically fails over to the paired region. This failover is subject to [limitations](#microsoft-managed-failover-to-a-paired-region). To configure the Azure IR region for your activity implementation or dispatch in the IR setup, set the region to *auto resolve*.
170170

171-
- *Azure-SSIS IR* failover is managed separately from a Microsoft-managed failover of the data factory. For more information, see [Alternative multiple-region approaches](#alternative-multiple-region-approaches).
171+
- *Azure-SSIS IR* failover is managed separately from a Microsoft-managed failover of the data factory. For more information, see [Alternative multi-region approaches](#alternative-multi-region-approaches).
172172

173-
- *A SHIR* runs on infrastructure that you're responsible for, so a Microsoft-managed failover doesn't apply to SHIRs. For more information, see [Alternative multiple-region approaches](#alternative-multiple-region-approaches).
173+
- *A SHIR* runs on infrastructure that you're responsible for, so a Microsoft-managed failover doesn't apply to SHIRs. For more information, see [Alternative multi-region approaches](#alternative-multi-region-approaches).
174174

175175
#### Post-failover reconfiguration
176176

0 commit comments

Comments
 (0)