Skip to content

Commit 7e08273

Browse files
authored
Update articles/reliability/concept-business-continuity-high-availability-disaster-recovery.md
1 parent 640c50a commit 7e08273

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/reliability/concept-business-continuity-high-availability-disaster-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ The following table lists some common criticality tiers:
168168
| Tier 2 - Business Operational | Business-operational systems support internal teams and processes. While not directly customer-facing, they're essential for productivity and operational continuity. | Reporting platforms, internal dashboards, and administrative tools. |
169169
| Tier 3 - Administrative | Administrative systems are non-critical workloads that support background operations or serve low-urgency use cases. | Archival platforms, sandbox environments, training portals, or batch-processing tools where availability isn't time-sensitive. |
170170

171-
For detailed guidance on the WAF criticality tiers, how classify your workload and optimize recovery costs, see [Well-Architected Framework - Select your criticality tier](/azure/well-architected/design-guides/disaster-recovery#select-your-criticality-tier).
171+
For detailed guidance on the WAF criticality tiers, how to classify your workload and optimize recovery costs, see [Well-Architected Framework - Select your criticality tier](/azure/well-architected/design-guides/disaster-recovery#select-your-criticality-tier).
172172

173173

174174

0 commit comments

Comments
 (0)