Blog Post

Microsoft Entra Blog
3 MIN READ

AAD Password Sync, Encryption and FIPS compliance

Alex_Simons's avatar
Alex_Simons
Icon for Microsoft rankMicrosoft
Sep 07, 2018
First published on CloudBlogs on Jun, 28 2014 Howdy folks, A couple weeks back, Taylor Higley asked a question on Twitter about Azure AD Password Sync, MD5 and FIPS ...
Updated Jul 28, 2020
Version 2.0
Alex_Simons's avatar
Icon for Microsoft rankMicrosoft
Joined May 01, 2017
View Profile
Microsoft Entra Blog
Stay informed on how to secure access for employees, customers, and non-human identities, from anywhere, to multicloud and on-premises resources, with comprehensive identity and network access solutions powered by AI.
Jack_Chen1780's avatar
Jack_Chen1780
Brass Contributor
Sep 27, 2022

I met this issue in a customer environment today and "<enforceFIPSPolicy enabled="false" />" fixed it. But the original issue was reported on 2014, why Microsoft won't just replace MD5 with SHA hash here ?  It's not easy to explain to customer "you have to disable FIPSPolicy to make it work, because Azure AD Connect use MD5, but in a acceptable way..."