Skip to content

Commit afa7e5b

Browse files
v-albemiv-albemi
authored
Merge pull request #110510 from billmath/relnotes1
udpating tools
2 parents fd59e86 + 37f120b commit afa7e5b

File tree

1 file changed

+6
-75
lines changed

1 file changed

+6
-75
lines changed

‎articles/active-directory/hybrid/plan-hybrid-identity-design-considerations-tools-comparison.md

Lines changed: 6 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -11,89 +11,20 @@ ms.workload: identity
1111
ms.tgt_pltfrm: na
1212
ms.devlang: na
1313
ms.topic: conceptual
14-
ms.date: 08/28/2018
14+
ms.date: 04/07/2020
1515
ms.subservice: hybrid
1616
ms.author: billmath
17-
1817
ms.collection: M365-identity-device-management
1918
---
2019
# Hybrid Identity directory integration tools comparison
21-
Over the years the directory integration tools have grown and evolved. This document is to help provide a consolidated view of these tools and a comparison of the features that are available in each.
22-
23-
<!-- The hardcoded link is a workaround for campaign ids not working in acom links-->
24-
25-
> [!NOTE]
26-
> Azure AD Connect incorporates the components and functionality previously released as Dirsync and AAD Sync. These tools are no longer being released individually, and all future improvements will be included in updates to Azure AD Connect, so that you always know where to get the most current functionality.
27-
>
28-
> DirSync and Azure AD Sync are deprecated. More information can be found in [here](reference-connect-dirsync-deprecated.md).
29-
>
30-
>
31-
32-
Use the following key for each of the tables.
33-
34-
● = Available Now
35-
FR = Future Release
36-
PP = Public Preview
37-
38-
## On-Premises to Cloud Synchronization
39-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services (AAD Sync) - NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync) - NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
40-
|:--- |:---:|:---:|:---:|:---:|:---:|
41-
| Connect to single on-premises AD forest |● |● |● |● |● |
42-
| Connect to multiple on-premises AD forests |● |● | |● |● |
43-
| Connect to multiple on-premises Exchange Orgs |● | | | | |
44-
| Connect to single on-premises LDAP directory |●* | | |● |● |
45-
| Connect to multiple on-premises LDAP directories |●* | | |● |● |
46-
| Connect to on-premises AD and on-premises LDAP directories |●* | | |● |● |
47-
| Connect to custom systems (i.e. SQL, Oracle, MySQL, etc.) |FR | | |● |● |
48-
| Synchronize customer defined attributes (directory extensions) |● | | | | |
49-
| Connect to on-premises HR (i.e., SAP, Oracle eBusiness,PeopleSoft) |FR | | |● |● |
50-
| Supports FIM synchronization rules and connectors for provisioning to on-premises systems. | | | |● |● |
51-
52-
53-
&#42; Currently there are two supported options for this. They are:
54-
55-
1. You can use the generic LDAP connector and enable it outside of Azure AD Connect. This is complex and requires a partner for on-boarding and a premier support agreement to maintain. This option can handle both single and multiple LDAP directories.
56-
57-
2. You can develop your own solution for moving objects from LDAP to Active Directory. Then synchronize the objects with Azure AD Connect. MIM or FIM could be used as a possible solution for moving the objects.
58-
59-
## Cloud to On-Premises Synchronization
60-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
61-
|:--- |:---:|:---:|:---:|:---:|:---:|
62-
| Writeback of devices |● | |● | | |
63-
| Attribute writeback (for Exchange hybrid deployment ) |● |● |● |● |● |
64-
| Writeback of groups objects |● | | | | |
65-
| Writeback of passwords (from self-service password reset (SSPR) and password change) |● |● | | | |
20+
Over the years the directory integration tools have grown and evolved.
6621

67-
## Authentication Feature Support
68-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
69-
|:--- |:---:|:---:|:---:|:---:|:---:|
70-
| Password Hash Sync for single on-premises AD forest |●|●|● | | |
71-
| Password Hash Sync for multiple on-premises AD forests |●|● | | | |
72-
| Pass-Through Authentication for single on-premises AD forests |●| | | | |
73-
| Single Sign-on with Federation |● |● |● |● |● |
74-
| Seamless Single Sign-on|● |||||
75-
| Writeback of passwords (from SSPR and password change) |● |● | | | |
7622

77-
## Set-up and Installation
78-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Microsoft Identity Manager 2016 (MIM) |
79-
|:--- |:---:|:---:|:---:|:---:|
80-
| Supports installation on a Domain Controller |● |● |● | |
81-
| Supports installation using SQL Express |● |● |● | |
82-
| Easy upgrade from DirSync |● | | | |
83-
| Localization of Admin UX to Windows Server languages |● |● |● | |
84-
| Localization of end user UX to Windows Server languages | | | |● |
85-
| Support for Windows Server 2008 and Windows Server 2008 R2 |● for Sync, No for federation |● |● |● |
86-
| Support for Windows Server 2012 and Windows Server 2012 R2 |● |● |● |● |
23+
- [FIM](https://docs.microsoft.com/previous-versions/windows/desktop/forefront-2010/ff182370%28v%3dvs.100%29) and [MIM](https://docs.microsoft.com/microsoft-identity-manager/microsoft-identity-manager-2016) are still supported and primarily enable synchronization between on-premises systems. The [FIM Windows Azure AD Connector](https://docs.microsoft.com/previous-versions/mim/dn511001(v=ws.10)?redirectedfrom=MSDN) is supported in both FIM and MIM, but not recommended for new deployments - customers with on-premises sources such as Notes or SAP HCM should use MIM to populate Active Directory Domain Services (AD DS) and then also use either Azure AD Connect sync or Azure AD Connect cloud provisioning to synchronize from AD DS to Azure AD.
24+
- [Azure AD Connect sync](how-to-connect-sync-whatis.md) incorporates the components and functionality previously released in DirSync and Azure AD Sync, for synchronizing between AD DS forests and Azure AD.
25+
- [Azure AD Connect cloud provisioning](../cloud-provisioning/what-is-cloud-provisioning.md) is a new Microsoft agent for synching from AD DS to Azure AD, useful for scenarios such as merger and acquisition where the acquired company's AD forests are isolated from the parent company's AD forests.
8726

88-
## Filtering and Configuration
89-
| Feature | Azure Active Directory Connect | Azure Active Directory Synchronization Services- NO LONGER SUPPORTED | Azure Active Directory Synchronization Tool (DirSync)- NO LONGER SUPPORTED | Forefront Identity Manager 2010 R2 (FIM) | Microsoft Identity Manager 2016 (MIM) |
90-
|:--- |:---:|:---:|:---:|:---:|:---:|
91-
| Filter on Domains and Organizational Units |● |● |● |● |● |
92-
| Filter on objects’ attribute values |● |● |● |● |● |
93-
| Allow minimal set of attributes to be synchronized (MinSync) |● |● | | | |
94-
| Allow different service templates to be applied for attribute flows |● |● | | | |
95-
| Allow removing attributes from flowing from AD to Azure AD |● |● | | | |
96-
| Allow advanced customization for attribute flows |● |● | |● |● |
27+
To learn more about the differences between Azure AD Connect sync and Azure AD Connect cloud provisioning, see the article [What is Azure AD Connect cloud provisioning?](../cloud-provisioning/what-is-cloud-provisioning.md)
9728

9829
## Next steps
9930
Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).

0 commit comments

Comments
 (0)