Skip to main content
Checks that Azure Databricks workspaces are encrypted at rest.

​
About

When you connect Microsoft Azure to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

​
Why This Matters

Data stored without encryption can be read by anyone who gains access to the underlying storage — through a misconfiguration, a stolen disk, or improper decommissioning. Encryption at rest renders that data useless without the key and is required by SOC 2, ISO 27001, HIPAA, and PCI DSS.

​
How to Fix

Before you begin
  • Ensure you have Contributor access to the Azure subscription.
Enable encryption at rest
  1. Sign in to the Azure Portal and open the relevant resource.
  2. For Azure SQL, confirm Transparent Data Encryption (TDE) is On under the database settings.
  3. For Storage accounts / Managed disks / Cosmos DB / Databricks, confirm encryption is enabled and, if required, configure a customer-managed key in Key Vault.
  4. Save the change.
Once encryption is configured, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Microsoft Azure integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Azure.