Skip to content

Commit 8efd945

Browse files
authored
Merge pull request #179574 from billmath/ldap1
updating
2 parents 4474988 + f5e0b66 commit 8efd945

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/app-provisioning/on-premises-migrate-microsoft-identity-manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: karenh444
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: how-to
10-
ms.date: 06/01/2021
10+
ms.date: 11/11/2021
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
@@ -22,7 +22,7 @@ ms.collection: M365-identity-device-management
2222
You can import into the Azure Active Directory (Azure AD) ECMA Connector Host a configuration for a specific connector from a Forefront Identity Manager Synchronization Service or Microsoft Identity Manager Synchronization Service (MIM Sync) installation. The MIM Sync installation is only used for configuration, not for the ongoing synchronization from Azure AD.
2323

2424
>[!IMPORTANT]
25-
>Currently, only the generic SQL connector is supported for use with the Azure AD ECMA Connector Host.
25+
>Currently, only the generic SQL and LDAP connectors are supported for use with the Azure AD ECMA Connector Host.
2626
2727
## Create and export a connector configuration in MIM Sync
2828
If you already have MIM Sync with your ECMA connector configured, skip to step 10.

0 commit comments

Comments
 (0)