PIVTR-D
RAzure playbook · Provider and accidental

Regional outage or service disruption

An Azure region or service fails, and your workloads there slow down or stop. Confirm the scope from Microsoft's health sources, fail over what you can, and record every emergency change so you can revert it. On October 20, 2025, a DNS automation fault in AWS us-east-1 left the regional DynamoDB endpoint with an empty DNS record, and dependent services failed for more than 14 hours.

Look here

LogSearch for
Azure statusWidespread incidents across regions, at https://azure.status.microsoft. Microsoft recommends Service Health for events that affect your own subscriptions
Service HealthActive service issues for your subscriptions: az graph query -q "ServiceHealthResources | where type =~ 'Microsoft.ResourceHealth/events' | where properties.EventType == 'ServiceIssue' and properties.Status == 'Active' | project name, properties.Title, properties.TrackingId, properties.ImpactStartTime"
AzureActivity, category ServiceHealthSubscription-scoped Service Health events: AzureActivity | where CategoryValue == "ServiceHealth" | project TimeGenerated, OperationNameValue, Properties_d
Resource HealthAvailability of each affected VM, database or gateway in the portal, which separates a platform event from a fault in your own resource
Log ingestionLate or missing security logs: Heartbeat | where TimeGenerated > ago(8h) | extend E2EIngestionLatency = ingestion_time() - TimeGenerated | summarize percentiles(E2EIngestionLatency, 50, 95) by Computer
AzureActivity, emergency changesRole assignments, network security group rules and firewall rules written during the outage: AzureActivity | where TimeGenerated between (datetime(<start>) .. now()) and OperationNameValue has_any ("roleAssignments/write", "securityRules/write", "firewallRules/write") | project TimeGenerated, Caller, OperationNameValue, _ResourceId

Contain

#Item
1Record the Service Health tracking ID, the impact start time and your first failed check in T3, and open an emergency change record for everything that follows
2Take the failed region out of Traffic Manager: az network traffic-manager endpoint update --name <endpoint> --profile-name <profile> --resource-group <rg> --type azureEndpoints --endpoint-status Disabled
3Take the failed origin out of Front Door. Since Azure CLI 2.88.0 the az afd commands come from the cdn extension: az afd origin update --resource-group <rg> --profile-name <profile> --origin-group-name <group> --origin-name <origin> --enabled-state Disabled
4Fail over a Cosmos DB account whose write region is down by taking that region offline (forced failover). Avoid changing the write region or failover priority during the outage: az cosmosdb offline-region --name <account> --resource-group <rg> --region <failed-region>
5Fail over an Azure SQL failover group, running the command against the secondary server. Add --allow-data-loss destructive only when the primary is unreachable: az sql failover-group set-primary --name <group> --resource-group <rg> --server <secondary-server>
6Check the storage account's last sync time before a failover: (Get-AzStorageAccount -ResourceGroupName <rg> -Name <account> -IncludeGeoReplicationStats).GeoReplicationStats.LastSyncTime
7Fail over the storage account to its secondary region destructive: az storage account failover --name <account> --resource-group <rg> --failover-type Unplanned --yes
8Give temporary access through time-bound role assignments only, and log each grant with its expiry in T3

Eradicate and recover

#Item
1Revert every emergency role assignment, network security group rule and firewall exception from the change record, and confirm each with the emergency-changes query
2Fail back after Service Health shows the issue mitigated, using a planned failover where the service offers one
3Write the log gaps, with source and time range, into the case record so later investigations know what data is missing
4Warn staff that phishing uses outage news, fake status pages and credit offers, and give them the official status address
5Alert on Service Health events: az monitor activity-log alert create --name <name> --resource-group <rg> --condition category=ServiceHealth --action-group <action-group-id>
6Keep the tracking ID and impact times for any service level agreement (SLA) credit claim, and follow the recover stage
7Exercise the failover with the regional outage tabletop
Watch out
  • When a resource group's region fails, Resource Manager reroutes that group's control plane requests to a backup region. The reroute does not cover data plane access to resources in the failed region.
  • An unplanned storage failover loses writes made after the last sync time. A SQL failover with --allow-data-loss can lose recent transactions.
  • Resource logs usually reach Log Analytics 3 to 10 minutes after the event and activity logs 3 to 20 minutes after, and an outage can add more delay. Queries by TimeGenerated can miss records that arrive late.

AWS summary of the Amazon DynamoDB service disruption in us-east-1. Microsoft Learn: Azure status overview, Service Health overview and notifications, Resource Graph samples for Service Health, Resource Manager overview, log data ingestion time, AzureActivity table, Azure CLI reference for az network traffic-manager endpoint, az afd origin (cdn extension), az cosmosdb, az sql failover-group, az storage account and az monitor activity-log alert, Azure Storage last sync time. Azure CLI 2.88.0 package contents and the cdn extension history in the azure-cli-extensions repository. Checked October 2026. Cosmos DB disaster recovery guidance: checked September 2026.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.