Skip to content

Commit 59c9126

Browse files
Merge pull request #34890 from MicrosoftDocs/main
Auto Publish – main to live - 2025-08-05 17:30 UTC
2 parents b6231ad + 3ece2c8 commit 59c9126

File tree

4 files changed

+30
-6
lines changed

4 files changed

+30
-6
lines changed

azure-sql/database/failover-group-configure-sql-db.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ titleSuffix: Azure SQL Database
44
description: Learn how to configure a failover group for a single or pooled database in Azure SQL Database by using the Azure portal, PowerShell, and the Azure CLI.
55
author: rajeshsetlem
66
ms.author: rsetlem
7-
ms.reviewer: wiassaf, mathoma, randolphwest
8-
ms.date: 09/27/2024
7+
ms.reviewer: wiassaf, mathoma, randolphwest, mahyon
8+
ms.date: 08/05/2025
99
ms.service: azure-sql-database
1010
ms.subservice: high-availability
1111
ms.topic: how-to
@@ -509,8 +509,11 @@ Be aware of the following limitations:
509509
- Removing a failover group for a single or pooled database doesn't stop replication, and it doesn't delete the replicated database. You'll need to manually stop geo-replication and delete the database from the secondary server if you wanted to add a single or pooled database back to a failover group after it's been removed. Failing to do either might result in an error similar to `The operation cannot be performed due to multiple errors` when attempting to add the database to the failover group.
510510
- Failover group name is subject to [naming restrictions](/azure/azure-resource-manager/management/resource-name-rules).
511511
- When creating a new failover group, or when adding databases to an existing failover group, you can _only_ designate the databases as [standby replicas](standby-replica-how-to-configure.md) _when using the Azure portal_ - Azure PowerShell and the Azure CLI are not currently available.
512+
- The Azure portal doesn't support creating failover groups across different subscriptions. Instead, use [PowerShell cmdlets to programmatically manage failover groups](#programmatically-manage-failover-groups).
512513

513-
## <a name="programmatically-managing-failover-groups"></a> Programmatically manage failover groups
514+
<a name="programmatically-managing-failover-groups"></a>
515+
516+
## Programmatically manage failover groups
514517

515518
Failover groups can also be managed programmatically by using Azure PowerShell, Azure CLI, and REST API. The following tables describe the set of commands available. Failover groups include a set of Azure Resource Manager APIs for management, including the [Azure SQL Database REST API](/rest/api/sql/) and [Azure PowerShell cmdlets](/powershell/azure/). These APIs require the use of resource groups and support Azure role-based access control (Azure RBAC). For more information on how to implement access roles, see [Azure role-based access control (Azure RBAC)](/azure/role-based-access-control/overview).
516519

azure-sql/docfx.json

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,14 @@
220220
},
221221
"sensitive-language-bl": {
222222
"exclude": []
223-
}
223+
},
224+
"filename-incomplete": {
225+
"exclude": [
226+
"includes/*",
227+
"*/include"
228+
]
229+
}
230+
224231
}
225232
}
226233
}

data-migration/docfx.json

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,14 @@
4141
"fileMetadata": {},
4242
"template": [],
4343
"dest": "data-migration",
44-
"markdownEngineName": "markdig"
44+
"markdownEngineName": "markdig",
45+
"rules": {
46+
"filename-incomplete": {
47+
"exclude": [
48+
"includes/*",
49+
"*/include"
50+
]
51+
}
52+
}
4553
}
4654
}

docs/docfx.json

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -591,7 +591,13 @@
591591
},
592592
"sensitive-language-bl": {
593593
"exclude": []
594-
}
594+
},
595+
"filename-incomplete": {
596+
"exclude": [
597+
"includes/*",
598+
"*/include"
599+
]
600+
}
595601
}
596602
}
597603
}

0 commit comments

Comments
 (0)