On Premises Ldap Connector Linux
In brief
The documentation now refers to the **Advanced Options** dropdown and **Edit target User attributes** instead of the former UI labels.
What Entra admins need to know
Administrators configuring on-premises LDAP provisioning should use the updated labels when verifying that directory schema attributes are available in Microsoft Entra ID.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
No content changes were available in this diff.
@@ -319,7 +319,7 @@ In this section, you'll configure the mapping between the Microsoft Entra user's 1. In the Microsoft Entra admin center, under **Enterprise applications**, select the **On-premises ECMA app** application, and then select the **Provisioning** page. 2. Select **Edit provisioning**. 3. Expand **Mappings** and select **Provision Microsoft Entra users**. If this is the first time you've configured the attribute mappings for this application, there's only one mapping present as a placeholder.- 1. To confirm that the schema of the directory server is available in Microsoft Entra ID, select the **Show advanced options** checkbox and select **Edit attribute list for ScimOnPremises**. Ensure that all the attributes selected in the configuration wizard are listed. If not, then wait several minutes for the schema to refresh, then select **Attribute Mapping** in the navigation line, and then select **Edit attribute list for ScimOnPremises** again to reload the page. Once you see the attributes listed, then cancel from this page to return to the mappings list.+ 1. To confirm that the schema of the directory server is available in Microsoft Entra ID, select the **Advanced Options** dropdown and select **Edit target User attributes**. Ensure that all the attributes selected in the configuration wizard are listed. If not, then wait several minutes for the schema to refresh, then select **Attribute Mapping** in the navigation line, and then select **Edit target User attributes** again to reload the page. Once you see the attributes listed, then cancel from this page to return to the mappings list. 1. Every user in a directory must have a unique distinguished name. You can specify how the connector should construct a distinguished name by using an attribute mapping. Select **Add New Mapping**. Use the following values to create the mapping, changing the distinguished names in the expression to match that of the organizational unit or other container in your target directory. - Mapping type: expression - Expression: `Join("", "CN=", Word([userPrincipalName], 1, "@"), ",DC=Contoso,DC=lab")` 