Azure Active Directory Password Synchronization issues

The DirSync Directory Sync tool helps organizations synchronize user information on on-premises ad to Office 365 so that IT administrators only need user management on the on-premises AD, synchronizing user information to Office365 with dirsync, reducing administrator maintenance effort For end-users, only 1 AD accounts are required to achieve local and Office365 authentication, which is extremely convenient.

DirSync has been replaced with a new product calledAzure Active Directory Connect, and Azure Active Directory synchronization is a new synchronization service that allows customers to do the following:

• You can synchronize a multi-forest Active Directory environment without the full feature set of Forefront Identity Manager R2.

• Advanced settings, mapping and filtering targets and attributes, including support for synchronizing a small set of user attributes (only 7!) ）

• Configure multiple on-premises Exchange organizations to map to a single Azure Active Directory tenant

We can refer to technet:https://msdn.microsoft.com/zh-cn/library/azure/dn790204.aspx

Azure Active Directory is currently available in several versions, with major versions: 1.0 and 1.1

650) this.width=650; "height=" 539 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/83/B2/ Wkiom1d7csvw4epmaagmakvnpjq000.png "border=" 0 "/>

650) this.width=650; "height=" 412 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/83/B1/ Wkiol1d7cszr32heaackrhw7dvy034.png "border=" 0 "/>

Before doing a hybrid deployment project that uses Azure Active Directory version 1.0, because the customer was using a server that was already down, the customer wanted to deploy Azure Active Directory with a new server, So I used the new Azure Active Directory version 1.1 when I was deploying Azure Active Directory, and after the deployment was completed, after a few days of observation, the problem came, and every day, users will be reflected, after the password has been modified, unable to sign in office with the new password 365 Exchange Online Mailbox.

I did a series of checks on these issues, including: Password synchronization option checking, re-synchronizing full synchronizations, re-executing the Synchronization wizard, and reinstalling Azure Active Directory 1.1 will not resolve password synchronization issues.

Is there a problem with the Azure Active Directory 1.1 version for the domestic version of Office 365 support? I swapped the customer's Azure Active Directory 1.1 version back into Azure Active Directory Version 1.0.

When the deployment is complete, the problem is resolved, and after the user modifies the password locally, the user can sign in to the Office 365 mailbox with the new password in 1-3 minutes.

I also discussed the above issues with the Microsoft engineers, but eventually changed back to the 1.0 version before the solution.

I do not know if you have encountered this problem, if it is the domestic version of Office 365, and the use of Azure Active Directory version is 1.1, and password synchronization is normal, I hope you share, is where I set the issue.

Of course, if you are experiencing this issue with Azure Active Directory 1.1, it is recommended that you use the 1.0 version of Azure Active Directory

This article is from "Jianbin Liu's Blog" blog, please be sure to keep this source http://liujb.blog.51cto.com/269257/1795809

Azure Active Directory Password Synchronization issues