Skip to content

Commit a3eab99

Browse files
authored
Fix markdown link formatting in failover group overview
Corrected bracket for link to customer-managed failover policy
1 parent 2d30747 commit a3eab99

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

azure-sql/includes/failover-group-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Each failover policy has a unique set of use cases and corresponding expectation
3232
| Failover policy | Failover scope | Use case | Potential data loss |
3333
| --- | --- | --- | --- |
3434
| Customer managed <br> **(Recommended)** | Failover groups | One or more databases in a failover group is impacted by an outage and becomes unavailable. You can choose to fail over. | Yes |
35-
| Microsoft managed | All failover groups in the region | A widespread outage in a region causes unavailability of databases and the Microsoft Azure SQL service team decides to trigger a forced failover. <br> Use this option only when you want to delegate the disaster recovery responsibility to Microsoft and the application is tolerant to RTO (downtime) of at least one hour or more. <br> Microsoft managed failover might only execute in extreme circumstances. A [customer-managed failover policy[(#customer-managed) is highly recommended. | Yes |
35+
| Microsoft managed | All failover groups in the region | A widespread outage in a region causes unavailability of databases and the Microsoft Azure SQL service team decides to trigger a forced failover. <br> Use this option only when you want to delegate the disaster recovery responsibility to Microsoft and the application is tolerant to RTO (downtime) of at least one hour or more. <br> Microsoft managed failover might only execute in extreme circumstances. A [customer-managed failover policy](#customer-managed) is highly recommended. | Yes |
3636

3737
### Customer managed
3838

0 commit comments

Comments
 (0)