Azure deleted our critical Azure Batch infrastructure without consent
Our production Azure Batch pools, jobs, and resources are missing and were deleted by Azure. We had a lapse in payment and the account was deactivated on May 19 2026 at 12:00am PST for about two hours before payment was quickly made and the account was reactivated.
The email said data would be deleted on 8/27/2026 if payment was not received. That's over 3 months away, but deletion of Batch data and infrastructure occurred within about 2 hours.
We need this escalated to the internal Azure Batch engineering team who builds and develops Batch or to an internal Azure backend data recovery team since your standard support staff was not able to address this from a support ticket. How can we get our data back? Are there forensic or data recovery specialists?
It is not acceptable to delete your customer's infrastructure and data without warning and extremely prematurely within a 2 hour period when we were told any possible deletion would occur after about 100 days from the given notice. Is this expected behavior for batch resources to be completely deleted when an azure account gets temporarily disabled for even just two hours? This needs to be fixed on your end to honor the disabled state and preserve batch resources, configurations, and history.
The Batch infrastructure took a lot of time to build and configure and has historical data for thousands of completed tasks we wanted to keep. We do backup task runtime logs and have scripts to recreate infrastructure, but we want this batch data loss to be recovered by azure as soon as possible.
-
Himanshu Shekhar 6,710 Reputation points • Microsoft External Staff • Moderator
Based on Microsoft’s documented subscription lifecycle, a temporary “Disabled” state due to non‑payment should not automatically delete resources. In the Disabled state, operations to create/update are blocked, but resources are still available to retrieve or delete (GET/DELETE), and permanent deletion is associated with the subscription reaching a Deleted state after a longer lifecycle window. Reference: Azure subscription states [learn.microsoft.com]
Also, Microsoft notes there can be a delay in managing resources after reactivation and advises contacting support if the delay persists. Reference: Reactivate a disabled Azure subscription
If the Azure Batch account/pools/jobs were actually deleted, there is no general self‑service “restore” for deleted ARM resources; recovery would depend on what was deleted and whether the underlying data still exists in dependent services (for example, Storage).
If any related Storage account was deleted, Microsoft documents that Storage accounts may be recoverable in some cases within 14 days, but recovery is best effort and not guaranteed.
Reference: https://learn.microsoft.com/en-us/azure/storage/common/storage-account-recover
-
Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator
I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail.
Sign in to comment
1 answer
-
AI answer
Azure Batch itself is a free control-plane service; charges and most persistent state come from underlying Azure resources such as virtual machines, disks, storage, virtual networks, and load balancers. When an Azure subscription or tenant is disabled for billing reasons and then reactivated, behavior for resource retention and deletion is governed by platform-level lifecycle policies, not by Azure Batch specifically.
From the available information, there is no supported mechanism in Azure Batch to self-service restore deleted Batch accounts, pools, jobs, or tasks once the underlying resources have been permanently deleted. The Batch troubleshooting and cost-management guidance only covers:
- How to resolve pool deletion failures when resource locks or dependencies prevent deletion.
- How to understand and clean up underlying resources (VMs, disks, VNets, load balancers, storage) that may continue to incur cost after Batch resources are deleted.
It does not describe any recovery or rollback path for deleted Batch control-plane entities (accounts, pools, jobs, tasks) after they have been removed by the platform.
For comparison, Azure Cosmos DB explicitly documents a backup-based restore process that requires opening a support ticket or calling Azure Support, and it notes that recovery is only possible within defined time windows and support plans. There is no equivalent documented restore workflow for Azure Batch resources in the provided material.
Given this, the only documented escalation and recovery pattern for critical data loss in Azure services is:
- Open an Azure Support request at the highest available severity for the affected subscription, clearly indicating production impact and unintentional deletion.
- Work with Azure Support, who can engage the appropriate product group or data recovery teams internally if any backend recovery options exist for that service.
If standard support has already been engaged and confirmed that the Batch resources are deleted with no recovery path, the documentation provided does not describe any further supported escalation channel or forensic/data-recovery specialist path that can be invoked directly by customers beyond Azure Support.
For future mitigation, the Batch cost and lifecycle guidance emphasizes:
- Batch accounts, jobs, and tasks are free, but compute nodes and related infrastructure incur charges even when idle.
- After deleting Batch resources, underlying resources such as VMs, disks, virtual networks, and load balancers may continue to exist and accrue costs until explicitly deleted.
- Backups and external logging (for example, storing task output and logs in Azure Storage) are necessary if long-term retention of historical execution data is required, because Batch does not provide a documented restore mechanism for deleted jobs/tasks.
References:
AI-generated content may be incorrect. Read our transparency notes for more information.