Skip to main content
Checks that Azure storage accounts enforce a minimum TLS version of 1.2.

​
About

When you connect Microsoft Azure to DSALTA, the platform evaluates this control on every sync using read-only API access. If the requirement is not met, DSALTA activates this check.

​
Why This Matters

Traffic sent over plain HTTP can be intercepted or tampered with in transit. Enforcing HTTPS with a current TLS version protects data confidentiality and integrity and is a baseline requirement for PCI DSS, SOC 2, and GDPR.

​
How to Fix

Before you begin
  • Ensure you have Contributor access to the Azure subscription.
Enforce the latest TLS version
  1. Sign in to the Azure Portal and open the resource (Storage account or App Service).
  2. For storage, open Configuration and set Minimum TLS version to 1.2.
  3. For App Service, open Configuration → General settings and set Minimum Inbound TLS Version to 1.2.
  4. Save the change.
Once the minimum TLS version is enforced, 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.