Task 02: Cluster Quorum Configuration
DOCUMENT CATEGORY: Implementation Runbook
SCOPE: Azure Local, WSFC (S2D / SAN), and standalone Hyper-V clusters
PURPOSE: Validate the witness storage account exists (create if absent), then configure cluster quorum MASTER REFERENCE: Cluster Quorum Configuration
Status: Active
Configure cluster quorum for high availability and split-brain prevention. Cloud Witness is the recommended type for all cluster scenarios. The deployment creates the witness from cluster.witness of infrastructure.yml; use this task to check it, or to change it after the deployment.
Quorum Options
| Quorum Type | Best For | Requirements |
|---|---|---|
| Cloud Witness | Azure Local, WSFC (S2D/SAN), Hyper-V — recommended | Azure Storage Account, internet access |
| File Share Witness | Air-gapped or on-premises environments | Domain-joined file server — not a cluster node |
| Disk Witness | Legacy WSFC/SAN only | Shared disk visible to all nodes; incompatible with S2D and Azure Local |
Cloud Witness is the recommended quorum type for all cluster scenarios. It requires an Azure Storage Account (cluster.witness.storage_account). The deployment creates the witness; the steps below check it or change it.
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
Execution Options
- Failover Cluster Manager
- Orchestrated Script
- Azure CLI
Failover Cluster Manager
When to use: Single cluster, prefer GUI-based configuration, or verifying an existing quorum setting
Step 1 — Verify or Create the Cloud Witness Storage Account
Before configuring quorum, ensure the storage account exists in Azure.
-
Open Azure Portal → search for Storage accounts
-
Verify
cluster.witness.storage_accountexists in the correct resource group -
If absent, create it: | Field | Value | Source | |-------|-------|--------| | Subscription | (deployment subscription) |
azure.subscription_id| | Resource group | (cluster resource group) |azure.resource_group| | Name | (witness SA name) |cluster.witness.storage_account| | Region | (cluster region) |azure.location| | Redundancy | Standard ZRS or LRS | no key (the script or Azure decides it) | -
After creation, navigate to the storage account → Security + networking → Access keys
-
Copy key1 — you will need it for the quorum configuration below
Step 2 — Configure Quorum via Failover Cluster Manager
Cloud Witness (recommended):
- Open Failover Cluster Manager on a management server or cluster node
- Connect to the cluster
- Right-click the cluster name → More Actions → Configure Cluster Quorum Settings...
- Click Next on the wizard welcome screen
- Select Select the quorum witness → Next
- Select Configure a cloud witness → Next
- Enter:
- Azure storage account name:
<cluster_witness.name from infrastructure.yml> - Azure storage account key: (key1 from Azure Portal)
- Azure service endpoint: leave default (
core.windows.net)
- Click Next → Next → Finish
File Share Witness (air-gapped / alternative):
- On a domain-joined file server (not a cluster node), create a shared folder
- Grant the cluster computer account Full Control on the share
- In Failover Cluster Manager: More Actions → Configure Cluster Quorum Settings...
- Select Configure a file share witness
- Enter the UNC path:
\\<file-server>\<share-name> - Click Next → Finish
Validation
- Quorum witness shown in Failover Cluster Manager under the cluster summary
- Cluster Events show no quorum-related warnings or errors
-
Get-ClusterQuorumreturns expectedQuorumTypeandQuorumResource
PowerShell
No PowerShell script that configures the quorum.
Invoke-ConfigureClusterQuorum-Orchestrated.ps1is a placeholder. A placeholder printsNOT IMPLEMENTED, changes nothing and exits with code 3. The deployment creates the witness fromcluster.witnessofinfrastructure.yml. Use the steps in the other tab when you change the witness after the deployment. The Azure CLI tab has a script for the storage account of a cloud witness.
Check
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-06-post-deployment/task-09-post-deployment-verification/powershell/Invoke-VerifyPostDeployment.ps1 | Read only. Its quorum check: a quorum type is set and the quorum state is Normal. See Task 09. |
Run
./Invoke-VerifyPostDeployment.ps1 -InfrastructureFile ./infrastructure.yml
Azure CLI
When to use: Run the task from a host that has the Azure CLI and not the Az PowerShell modules. The script is PowerShell 7 that calls
az; it readsinfrastructure.ymland carries no values of its own.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-06-post-deployment/task-02-cluster-quorum-configuration/azurecli/New-CloudWitnessStorageAccount.azcli.ps1 | Creates, or checks, the Azure storage account of the cloud witness that cluster.witness of infrastructure.yml names, with the Azure CLI. Supports -WhatIf. |
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>.
Azure side only. An existing account is checked and never changed: a cloud witness supports only a Standard general-purpose v2 account with locally redundant storage, so an account of another kind or SKU is reported as Failed. A missing account is created (StorageV2, Standard_LRS) after the script checks that the name is free. It never reads, prints or stores an access key. Pointing the cluster at the account (Set-ClusterQuorum -CloudWitness) runs on a node and is not an Azure CLI task. For cluster.witness.type none or file_share it does nothing and exits 0. You need Storage Account Contributor (or Contributor) on the resource group.
Run
./New-CloudWitnessStorageAccount.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./New-CloudWitnessStorageAccount.azcli.ps1 -InfrastructureFile ./infrastructure.yml
Validation Summary
| Check | Command | Expected Result |
|---|---|---|
| Quorum type | Get-ClusterQuorum | Select QuorumType | NodeAndCloudWitness or NodeAndFileShareMajority |
| Quorum state | (Get-Cluster).QuorumState | Normal |
| Witness resource | Get-ClusterResource | Where-Object ResourceType -match "Witness" | State: Online |
| Storage account | Get-AzStorageAccount -Name <name> -ResourceGroupName <rg> | ProvisioningState: Succeeded |
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
Set-ClusterQuorum fails with access denied | Insufficient permissions on cluster or storage account | Run as cluster administrator; verify SPN has Storage Account Key Operator Service Role on the witness storage account |
Quorum state shows NotConfigured | Cloud witness storage account key is incorrect or rotated | Re-configure with fresh key: Set-ClusterQuorum -CloudWitness -AccountName <name> -AccessKey <newkey> |
Witness resource shows Failed | Storage account firewall blocking cluster node IPs | Add cluster node public IPs to the storage account firewall allow list or enable Allow trusted Microsoft services |
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| Previous | Up | Next |
|---|---|---|
| Task 01: Deploy SDN | Phase 06 Index | Task 03: Security Groups |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |