Guidelines for Active Directory before sync

Highlighted
Super Contributor

Hello 

 

There's a lot of guidelines for various O365 workloads and Tenant settings - but havn't found any for "Designing an AD structure" guidelines  regarding AD Connect and the use of filtering  - 

 

Is your (complete) AD synced to AAD (service accounts etc etc. ? -

or did you create a specific OU where you have 'categorized' your users in security groups and used the filtering before sync?

 

- what are the 'recommendations' from MS ?   

 

5 Replies
Highlighted

Filtering is an optional feature, which you should only use when needed. There's negligible security impact of syncing your objects to Azure AD, and adjusting the OUs/objects to sync will hardly remedy any bad decisions implemented back when the AD was designed.

 

You can think of the default configuration as Microsoft's recommendation, as mentioned here: https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnectsync-conf...

 

Spoiler
The default configuration takes all objects in all domains in the configured forests. In general, this is the recommended configuration. Users using Office 365 workloads, such as Exchange Online and Skype for Business, benefit from a complete Global Address List so they can send email and call everyone. With the default configuration, they would have the same experience that they would have with an on-premises implementation of Exchange or Lync.
Highlighted

Hi Vasil 

Thanks for your reply :) 

So when MS guidelines says "Categorize your users" and "Use groups and group-based licensing" - and we have the AD administration "on prem" only - what to do then?  .... the complete AD synced out - are 'just' to have the global address List available or am I missing something?.

Highlighted

It's up to you really, I've seen organizations going either way. We certainly have more than enough settings to configure filtering now, so you can use it if you thinks it's best for your particular org. The closest think I could find to a "recommendation" is in the article I linked above :)

Highlighted

Some reasons to not sync service accounts include:

1. they provide an additional risk to the organization if they get compromised in the cloud.

2. they show up in Delve and other places, which can be confusing/ugly

 

Highlighted
Hi Dean

My point exactly ;) could’t agree more ;)