#Azure ad sync tool download password#
However, if we compare the two tools at the moment, it becomes clear that the only reason to use DirSync is because of the lack of the password hash synchronization in AADSync. Both tools are currently supported and MS will not drop support for DirSync anytime soon. With both tools currently available, it might be a bit confusing which tool is the preferred tool to use.
MS is working on this and says this will be part of the next release.Īdditionally MS is also working on integrating the following features into the AADSync tool: Exchange / SharePoint…) … and if that doesn’t suffice, you can filter per attribute!Īs you might have noticed, there is currently no option to synchronize password hashes to Azure AD with the AADSync tool.
This tool is intended to provide a single synchronization engine to support both Azure Active Directory and Office 365 and includes the following feature additions: The new “sync service to rule them all” is called Microsoft Azure AD Sync Services (AADSync) tool. Last month (16 th of September), Microsoft released a new identity synchronization tool. Furthermore, MS included support for Exchange 2013 Hybrid scenarios, enabled the synchronisation of passwords via the Password Hash sync feature (May 2013), enabled WAAD Sync to be installed on Domain Controllers (Nov 2013) and most recently, enabled password write back in Azure AD premium scenarios (May 2014). The tool was now able to synchronized users and groups into an Azure AD tenant that wasn’t linked to an Office 365 subscription.
#Azure ad sync tool download windows#
In 2012, Microsoft made some bigger changes around DirSync to support synchronisation with Azure AD and it was rebranded to the Windows Azure Active Directory Synchronisation tool (WAAD Sync). The underlying synchronization engine was updated to FIM, providing a 64-bit version of the tool. The next major release of DirSync came to us around the end of 2011. Support for filtering objects such OUs, accounts and groups was also introduced. When BPOS was rebranded to Office 365 in 2010, not only did MS change the underlying versions of Exchange Online, SharePoint Online and Lync Online, but DirSync became an essential requirement for the new Exchange Hybrid as well as Single Sign-On with Office 365. DirSync v1 was only available as a 32-bit version and it didn’t offer much more than the synchronisation of all user, group and contact objects from a single Active Directory to the Microsoft Online Identity Directory for BPOS. Back in those days, DirSync was based on FIM’s predecessor, Microsoft Identity Lifecycle Manager (ILM). DirSync HistoryĭirSync was first introduced in 2009 to synchronize AD accounts between on-premises AD and the predecessor to Office 365, Microsoft BPOS (Business Productivity Online Suite). Finally, as we now have 3 Directory Synchronization options for Office 365 and Azure AD (DirSync, AADSync, FIM), we will help you decide which Directory Synchronization option is right for you. With the latest release, I found this to be a perfect time to reflect on how DirSync has developed over the last few years, to look at what’s possible with the new tool and what we can expect in AADSync vNext. Microsoft calls it the new “one sync service to rule them all”, enabling support for Multi-Forest synchronizations and AD attribute filtering, amongst other features that were previously only possible with a licensed version of Forefront Identity Manager (FIM). Microsoft’s new Azure Active Directory Synchronization Services tool (AADSync) was released to General Availability last month on the 16th of September.
0 kommentar(er)
