Skip to content

Commit dd2fef1

Browse files
Create on-premises-custom-connector.md
1 parent c601019 commit dd2fef1

File tree

1 file changed

+53
-0
lines changed

1 file changed

+53
-0
lines changed
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Azure AD provisioning to applications using custom connectors
3+
description: This document describes how to configure Azure AD to provision users with external systems that offer REST and SOAP APIs.
4+
services: active-directory
5+
author: billmath
6+
manager: amycolannino
7+
ms.service: active-directory
8+
ms.subservice: app-provisioning
9+
ms.topic: how-to
10+
ms.workload: identity
11+
ms.date: 05/19/2023
12+
ms.author: billmath
13+
ms.reviewer: arvinh
14+
---
15+
16+
17+
# Provisioning with the custom connectors
18+
19+
Azure AD supports pre-integrated connectors for applications that support the following protocols and standards:
20+
21+
> [!div class="checklist"]
22+
> - [SCIM 2.0](on-premises-scim-provisioning.md)
23+
> - [SQL](utorial-ecma-sql-connector.md)
24+
> - [LDAP](on-premises-ldap-connector-configure.md)
25+
> - [REST](on-premises-ldap-connector-configure.md)
26+
> - [SOAP](on-premises-ldap-connector-configure.md)
27+
28+
For connectivity to applications that don't support the aformetioned protocols and standards, customers and partners have built custom [ECMA 2.0](https://learn.microsoft.com/previous-versions/windows/desktop/forefront-2010/hh859557(v=vs.100)) connectors for Microsoft Identity Manager (MIM) 2016. You can now use those ECMA 2.0 connectors with the Azure AD provisioning provisioning agent, without needing MIM sync deployed. We also have a healthy ecosystem of custom connectors built by partners that you can use to connect to popular applications. For a full list, please see [here](https://social.technet.microsoft.com/wiki/contents/articles/1589.fim-2010-mim-2016-management-agents-from-partners.aspx).
29+
30+
## Limitations
31+
32+
Custom connectors built for MIM rely on the [ECMA framework](https://learn.microsoft.com/previous-versions/windows/desktop/forefront-2010/hh859557(v=vs.100)). The following table describes the parts of the ECMA to framework that the ECMA host supports. For a list of known limitations for the Azure AD provisioning service and on-premises application provisioning, see [here](https://learn.microsoft.com/azure/active-directory/app-provisioning/known-issues?pivots=app-provisioning#on-premises-application-provisioning).
33+
34+
35+
| **Scenario** | **Support** | **Comments** |
36+
| --- | --- | --- |
37+
| Object type | Partially supported | Supports one object type |
38+
| Partitions | Partially supported | Supports one partition |
39+
| Hierarchies | Not supported | |
40+
| Full export | Not supported | |
41+
| DeleteAddAsReplace | Not supported | |
42+
| ExportPasswordInFirstPass | Not supported | |
43+
| Normalizations | Not supported | |
44+
| Concurrent operations | Not supported | |
45+
46+
47+
## Next steps
48+
49+
- [App provisioning](user-provisioning.md)
50+
- [ECMA Connector Host generic SQL connector](tutorial-ecma-sql-connector.md)
51+
- [ECMA Connector Host LDAP connector](on-premises-ldap-connector-configure.md)
52+
53+

0 commit comments

Comments
 (0)