Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that MFA is enabled for all Azure Active Directory users.

​
Why This Matters

Without MFA, a compromised password is the only barrier between an attacker and your systems. Credential stuffing attacks, phishing, and password reuse make single-factor authentication a significant vulnerability. Enabling MFA adds a second verification layer that blocks over 99% of automated account takeover attempts.

​
What DSALTA Checks

DSALTA connects to your Azure Active Directory environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Azure Active Directory.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Log in to your Azure Active Directory admin console.
  2. Navigate to the Security or Authentication settings.
  3. Enable Multi-Factor Authentication for all users.
  4. Set enforcement to require MFA — not just optional.
  5. Choose allowed MFA methods (authenticator app, hardware key, SMS).
  6. Communicate the change to your team and set an enrollment deadline.
  7. Once all users have enrolled, DSALTA will detect the change on the next sync cycle and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Azure Active Directory integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Azure Active Directory.