Skip to content

Commit a380d95

Browse files
Merge pull request #250982 from ArvindHarinder1/patch-313
Update on-premises-migrate-microsoft-identity-manager.md
2 parents 0e4daf4 + e273a94 commit a380d95

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: amycolannino
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: how-to
10-
ms.date: 10/20/2022
10+
ms.date: 09/11/2023
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
@@ -18,8 +18,6 @@ ms.collection: M365-identity-device-management
1818

1919
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.
2020

21-
>[!IMPORTANT]
22-
>Currently, only the generic SQL and LDAP connectors are supported for use with the Azure AD ECMA Connector Host.
2321

2422
## Create a connector configuration in MIM Sync
2523
This section is included for illustrative purposes, if you wish to set up MIM Sync with a connector. If you already have MIM Sync with your ECMA connector configured, skip to the next section.

0 commit comments

Comments
 (0)