Entra Connect not detecting AD LDS instance

Mithunkumar Chopda 41 Reputation points
2025-02-23T16:51:27.76+00:00

I have a non domain join Windows Server 2019 running an AD LDS instance. I am trying to sync a directory partition on this instance to cloud only Entra ID tenant. I have installed both Cloud Sync (Provisioning Agent) and Entra Connect agents. CloudSync agent detects my AD LDS instance. But seems like this agent will provision identity from Entra to AD LDS. I want to sync from Ad LDS to Entra. Running AzureADConnect.exe /EnableLDAP seems to have no effect. The Entra Connect wizard launched with /EnableLDAP flag was expected to allow adding LDAP directories. Has anything changed or is LDAP to Entra ID synchronization not supported?

Microsoft Security Microsoft Entra Microsoft Entra ID
0 comments No comments
{count} votes

Accepted answer
  1. Marcin Policht 49,640 Reputation points MVP Volunteer Moderator
    2025-02-23T17:25:57.1533333+00:00

    As per https://learn.microsoft.com/en-us/entra/architecture/sync-ldap

    Deploying the LDAP Connector requires an advanced configuration. Microsoft provides this connector with limited support. Configuring this connector requires familiarity with Microsoft Identity Manager and the specific LDAP directory.

    When you deploy this configuration in a production environment, collaborate with a partner such as Microsoft Consulting Services for help, guidance, and support.

    If you intend to do this on your own, refer to https://learn.microsoft.com/en-us/microsoft-identity-manager/reference/microsoft-identity-manager-2016-connector-genericldap


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.