New Local Active Directory Server for an Existing Office 365 Environment.

Greetings,
I'm looking for a bit help with a small office using Office 365.  They have about 30 workstations but do not have a server onsite.  They are using Office 365 for Exchange, SharePoint, etc.  The problem is maintaining user accounts and network printers on all 30 workstations is getting very painful.  So, I'd like to deploy a small server and create a local AD Domain and sync all of the user accounts from Office 365 to the new DC.  I've read several articles and TechNet docs about syncing with Azure AD Sync but everything I've read deals with syncing current domains or migrating from local domains to O365 and not vice versa.  Has anyone tried doing this or know of a process for it?
LVL 5
DMJorgensenAsked:
Who is Participating?
 
Cliff GaliherConnect With a Mentor Commented:
You got it. As for the namespace, I am a proponent of using a subdomain of your primary public domain. So if you are company.com, going with hq.company.com or similar is not a bad way to go. That way, if you ever need to go child domain or make distinctions, yo can go seattle.company.com, sanfran.company.com, finance.company.com, etc, and keep it all internal. But you also avoid the issues of internal users needing to access a website at "company.com" and always hitting the DC as you would if you didn't use a subdomain.

Most AD experts I know now advocate this method. Existing .local domains don't need to be migrated in any short term way, but when starting fresh, this is the most sustainable method. Might as well start on the right foot.
0
 
Cliff GaliherCommented:
What you want, specifically, cannot be done. You can create a local domain.  And you can (eventually) have sync in place. But syncing is always from AD to AAD, not vice versa.

So you'll be creating the on-prem domain accounts, not just pulling them down from AAD. Once created, as long as you ensure the SMTP address property matches their primary address in Office 365, then when you do set up syncing, Office 365 will soft-match using that address and future on-prem changes will properly sync to the exiting O365 account. But you do have some initial setup to do if you go that route.
0
 
DMJorgensenAuthor Commented:
Awesome, that sounds like a really good time.  So, just to clarify:  I create a new empty domain, create users based on the O365 accounts / email address property, and then go through the sync process to match the local and cloud accounts?  Would it be wise to make the on-prem domain namespace a domain.local instead of the public namespace of domain.com?
0
 
DMJorgensenAuthor Commented:
Got it.  Good info Cliff, thanks for the help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.