azure

tl;dr – Close your Synchronization Rules Editor and just populate the mailNickname attribute in AD. There is a growing number of business networks that have never had Exchange installed on-premises. That’s awesome. You absolutely do not want to waste your time protecting your Exchange environment against whatever scripted threats can be thrown at you 24/7, especially when you can just pay Microsoft to do it for you. However, what that means is you end up missing information in a few places that Azure AD Connect is looking....

While following Elan Shudnow’s excellent guide on Connecting Azure Runbooks to Exchange Online and Microsoft Graph, I ran into the following error while uploading a self-signed certificate: And that’s weird, because I was just pasting the exact password I had generated with HSXKPasswd. I recreated the certificate and tried again – no dice. This “The specified network password is not correct” error can come from multiple areas in Azure, and searching for an answer didn’t really help....