Deletion of Resource Group on Azure and Impact on Databricks Workspace

[oeztuerk82]

Hello together,

I would like to confirm the data retention and deletion behavior associated with an Azure Databricks workspace, particularly in the context of deleting an Azure resource group where a Databricks Workspace lays in.

Recently, I deleted an Azure resource group that included an Azure Databricks workspace. I understand that the workspace and its associated compute resources are deleted in this process. However, I would like to confirm the following point with full certainty:

Does deleting the resource group (and thereby the Databricks workspace) also permanently delete all data stored in the Databricks File System (DBFS), including uploaded files, /dbfs/, /FileStore/, notebooks, and any other workspace-managed data?

Additionally:

• Is any part of this data stored in a Databricks-managed Azure Storage account or service outside of my Azure subscription?

• Is there any possibility of recovery after the workspace and resource group have been fully deleted?

This confirmation is needed for my documentation and future data management strategy.

Thank you in advance for your support and clarification.

[SP_6721]

Hi @oeztuerk82 ,

Deleting the Azure resource group containing a Databricks workspace permanently deletes all data in the DBFS, including uploaded files, /FileStore/, notebooks, and other workspace-managed data. This data is tied to a storage account within the resource group, and once deleted, it cannot be recovered.
There is no documentation I found that mentions data being stored in Databricks-managed Azure systems outside the subscription.
And once the resource group and workspace are deleted, the associated data is unrecoverable, as per my knowledge.

[SAKBAR]

Resource group once deleted cannot be recovered as like ADLS, so not possible to restore workspace or any resource under the resource group. May be Microsoft support can recover if under premium plan with them. For future perspective it is always better to put delete lock on resource group level.