From December 2026, Dashlane will no longer support AD Sync. We're moving to a more secure and reliable directory-sync experience via SCIM provisioning. SCIM is an industry-standard protocol that offers improved security and stability.
To avoid any disruption to your directory sync, you'll need to switch to SCIM provisioning before December 2026.
Why are you discontinuing AD Sync?
Microsoft is ending support for older versions of Entra Connect Sync on September 30, 2026, requiring a mandatory upgrade. Rather than migrating to a new version of the same legacy architecture, we'd encourage you to use this moment to switch to a modern, cloud-native standard.
SCIM provisioning is built on a different security model. Unlike legacy AD Sync, which requires periodic polling of your directory every 30–60 minutes, SCIM pushes changes to your systems the moment they happen. That means when an employee leaves your organization, their access is revoked in seconds.
SCIM runs inside a secure enclave (AWS Nitro), meaning that neither Dashlane nor any cloud provider can access your encryption keys or directory data during the sync process. It's the only directory sync solution that extends Zero-Knowledge privacy to your user directory.
How can I switch to SCIM provisioning?
Please follow these steps, depending on your SSO configuration:
Confidential SSO
As Confidential SSO is already set up for your team, you can follow the steps below to complete the switch to SCIM:
- Stop the on-prem AD sync script from running in PowerShell.
-
Turn off AD sync in the Admin Console
-
Set up options:
- If you have Azure, Okta, or PingID as your Identity Provider, follow the specific steps under Set up SCIM Provisioning to complete the migration.
- If you have a different Identity Provider, check how to set up SCIM Provisioning to complete the migration.
- If your Identity Provider doesn't support SCIM Provisioning, like Google Workspace, we recommend turning on Just in Time Provisioning.
Self-hosted SSO
As self-hosted SSO is already set up for your team, you can follow the steps below to complete the switch to SCIM:
- Stop the on-prem AD sync script from running in PowerShell.
-
Turn off AD sync in the Admin Console
-
Set up options:
- If you have Azure, Okta, or JumpCloud as your Identity Provider, select which one and follow the specific steps under Set up SCIM Provisioning to complete the migration.
- If you have a different Identity Provider, check how to set up SCIM Provisioning to complete the migration.
- If your Identity Provider doesn't support SCIM Provisioning, like Google Workspace, we recommend turning on Just in Time Provisioning.
If you have self-hosted SSO set up and you wish to switch to Confidential SSO and SCIM, select Chat with bot in the bottom right of this page, to contact our Support team. We can help you with this.
What happens if I don't switch to SCIM provisioning before the deadline?
If you still have an active AD Sync setup when Dashlane stops supporting it in December 2026, your directory sync will stop working entirely. This means changes to your user directory, like new employees, role changes, and departures, will no longer sync to Dashlane automatically.
User provisioning and deprovisioning will have to be handled manually, which is also a security risk: former employees may retain access to company credentials longer than intended.
Why haven't I received an email about this?
Emails about the AD Sync switch to SCIM provisioning will be sent to all admins progressively, and according to the AD Sync provisioning setup your organization has. We will help you with the switch to SCIM provisioning before we stop supporting AD Sync.