PIVTR-D
RAzure playbook · Provider and accidental

Data lost through provider or operator error

Resources or data disappear through a mistake: an infrastructure-as-code apply, a cleanup script, a resource group delete, or an error on Microsoft's side. In May 2024 a Google Cloud provisioning misconfiguration deleted UniSuper's private cloud subscription in both of its regions, and UniSuper restored from backups it kept with another provider. Stop the automation that deleted the data and protect what remains first; if a caller is unknown or the deletes follow a suspicious sign-in, go to destruction and backup deletion.

Look here

LogSearch for
AzureActivityWho deleted what, in order. The Activity Log keeps 90 days without a diagnostic setting: AzureActivity | where OperationNameValue endswith "/delete" | project TimeGenerated, Caller, CallerIpAddress, OperationNameValue, ActivityStatusValue, _ResourceId | order by TimeGenerated asc
AzureActivity, resource groupsResource group deletes, which remove every resource in the group: Microsoft.Resources/subscriptions/resourceGroups/delete
Deployment and pipeline recordsThe deployment behind the change, then its pipeline run, plan output and commit: az deployment group list --resource-group <rg>
Deleted key vaultsVaults still in soft delete: az keyvault list-deleted --resource-type vault
Deleted AI accountsAzure OpenAI and other Foundry Tools accounts still recoverable: az cognitiveservices account list-deleted
Deleted SQL databasesDropped databases on a surviving server and their deletion times: az sql db list-deleted --resource-group <rg> --server <server>
Deleted App Service appsApps still restorable, from Azure PowerShell: Get-AzDeletedWebApp
Deleted backup itemsSoft-deleted backup items in each Recovery Services vault
Service Health and Customer LockboxA Microsoft-side error, shown as a Service Health event or a support case finding. Microsoft engineer access to your data appears as Create Lockbox Request and Approve Lockbox Request only when Customer Lockbox is on
Subscription stateA canceled subscription, which deallocates VMs and makes storage read-only: az account show --subscription <sub-id> --query state

Contain

#Item
1Stop the automation before any restore. Pause the pipeline or scheduled job, and remove its identity's role: az role assignment delete --ids <assignment-id>
2Lock surviving resource groups. A delete lock on any resource blocks deletion of its whole group: az lock create --name ir-nodelete --lock-type CanNotDelete --resource-group <rg>
3Save the Activity Log for the window, as in the first 15 minutes, and export the deployment records
4Check soft delete on each Recovery Services vault. Secure by default now enforces it on Recovery Services vaults: az backup vault backup-properties show --name <vault> --resource-group <rg>
5Where a vault still shows soft delete off, set it to AlwaysOn, which cannot be turned off later: az backup vault backup-properties set --name <vault> --resource-group <rg> --soft-delete-feature-state AlwaysOn
6Open a support case at the highest severity your plan allows, and ask whether Microsoft can still restore the resources. Add the contact, title, description, ticket name and --problem-classification flags, and use highestcriticalimpact only on a Premium plan: az support in-subscription tickets create --severity critical --advanced-diagnostic-consent Yes

Eradicate and recover

#Item
1Recreate a deleted resource group first, because recovery of storage accounts and other resources needs it. Resource group deletion itself cannot be undone
2Restore within each window: storage accounts 14 days (best effort), blobs and containers the soft delete period you set (1 to 365 days), Key Vault 7 to 90 days. The windows for Azure AI services are 48 hours, App Service apps 30 days, and Recovery Services backup items 14 days by default (up to 180)
3Restore a dropped SQL database within its point-in-time retention, using the deletion time from the list above. A deleted server takes its databases and point-in-time backups with it, and only long-term retention backups survive: az sql db restore --dest-name <new-db> --deleted-time "<deletion-time>" --name <db> --resource-group <rg> --server <server>
4Restore VMs and disks from Azure Backup recovery points, using Cross Region Restore where the vault is geo-redundant and the flag was set
5Reactivate a canceled subscription at once. Microsoft deletes the data 30 to 90 days after cancellation. Pay-as-you-go subscriptions reactivate in the portal, and other types through support within 90 days
6Keep one backup copy outside the subscription and tenant that production uses, and lock the vault's immutability once retention is right
7Require a reviewed plan for deletes in the pipeline, and follow the recover stage for service validation
Watch out
  • Permission to delete a resource group is enough to delete every resource in it, and it overrides delete actions in a role's notActions.
  • Blob soft delete does not survive deletion of the storage account. Only a lock on the account prevents that.
  • Customer Lockbox excludes emergency access by Microsoft to restore service or prevent data loss, so work done by Microsoft staff during recovery may not appear in your logs.

UniSuper and Google Cloud joint statement. Microsoft Learn: activity log, delete a resource group, lock resources, recover a deleted storage account, blob soft delete, recover or purge deleted Microsoft Foundry resources, Azure Backup secure by default, Customer Lockbox for Microsoft Azure, cancel an Azure subscription, Azure CLI reference for az backup vault backup-properties, az keyvault, az sql db and az support in-subscription tickets. Checked October 2026. Restore a deleted App Service app (30 days, paid plans only): checked October 2026. Key Vault soft delete, SQL Database recovery using backups, and create an Azure support request: 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.