AAD Connect Advanced Deployments and Troubleshooting

A few weeks ago, I wrote a blog post here covering how to deploy Azure Active Directory Connect 1.1. Due to popular demand, today I'm going to circle back and review some of the advanced configurations of AAD Connect as well as some troubleshooting tips to cover you in case you run into a hitch with your AAD Connect deployment.

Since there is a lot to cover, and I have limited space in which to do it, I’m not going to go super deep into each of these topics. Instead I’m going to give you a high-level overview. I’ll try to link to resources where you can get more information on each topic as appropriate, and you can reach out to me via the comments below or on Twitter if you’d like me to answer any specific questions.

Office 365Nathan OBryanApril 19, 2016AAD COnnect, Azure ADComment

Azure AD Connect 1.1 Filtering – Part 1

As DirSync evolved to AAD Sync, and AAD Sync evolved to AAD Connect, there have been significant changes to the way we accomplish tasks with these tools.

With the recent release of Azure Active Directory Connect v 1.1, Microsoft has made several updates to how various aspects of the process of syncing your on-premises Active Directory accounts into Azure Active Directory. There have been some pretty significant changes in a couple of areas, with one of those being sync filtering. In this series of blogs posts, I’m going to walk you through the options and processes for filtering your sync jobs.

Office 365Nathan OBryanMarch 4, 2016AAD COnnect, DirSync, Azure ADComment

Updated PowerShell script: Activate-SyncedPasswords

A couple of weeks ago I published a script that assists with switching your Office 365 authentication method from federated to managed and back again. After playing with the script for a while, I have realized that I had made a couple of incorrect assumptions about the rep-requisites for this script.

PowerShellNathan OBryanDecember 22, 2014Azure AD, DirSync, ADFS, Office 365Comment

Changing user logon domain in Office 365

When syncing your users to your Office 365 tenant via DirSync there are a number of reason that their login ID and primary SMTP address can end up being set to @tenant.onmicrosoft.com. Maybe you started DirSync before the domain was accepted in Office 365, or maybe your users UPNs are set to something other than the domain name you want to use as their primary SMTP address. Whatever the reason, once users are synced and end up with the wrong login ID, it can be a pain to change them especially for a large number of users. One way to fix that problem is with the following PowerShell command run after you connect to Azure AD via the Azure AD module.

Office 365Nathan OBryanOctober 20, 2014Azure AD, Office 365, PowerShellComment

Home Blog

Contact Subscribe