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
Without reliable backups, a hardware failure, accidental deletion, or ransomware event can permanently destroy your data. Automated backups with sensible retention give you a recovery path and are required by SOC 2, ISO 27001, and most frameworks.How to Fix
Before you begin- Ensure you have Contributor access to the Azure subscription.
- Sign in to the Azure Portal.
- For SQL / Cosmos DB, confirm backup retention is configured under the resource’s Backups settings.
- For disks / Databricks storage, open Backup center → + Backup, select the data source, choose a Backup vault and policy, and start the backup.
Frequently Asked Questions
How often does this check run?
How often does this check run?
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.
What happens if it keeps failing?
What happens if it keeps failing?
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.
Can I exclude this check?
Can I exclude this check?
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
Does DSALTA change my Microsoft Azure configuration?
Does DSALTA change my Microsoft Azure configuration?
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.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)