Greetings!
I'm realizing more and more the inefficiency involved with keeping my AD separate from Office 365. I want to start syncing the two, but have some specific questions related to our environment that I need answered before feeling comfortable taking the plunge.
1. Our internal FQDN is presently "xyz.local". Although I now know thanks to this article that I never should have set it up this way, it's a little too late now. Any downside to having a .local domain name before embarking upon a DirSync (and subsequent SSO) deployment? Or do I need to take the time now to perform a Domain Rename? NOTE: We are *not* running Exchange on-prem.
2. Do I simply need to add our "domain.com" as an alternative UPN suffix via AD Domains & Trusts?
3. I already have about 75 users in the cloud. What happens when our xyz.local users get pushed up to the cloud where some user@domain.com already exists? How does DirSync know to "link" the two and/or how does it handle conflicts?
There are several variations to Question #3 that come to mind, but rather than ask them explicitly, I'll leave it at that. In general, I need to know what to expect seeing as how some users are only in the cloud (will it create them in AD?), some are only in AD, and others exist in both. I don't want to have any major negative effect, especially seeing as how my domain is xyz.local, so any advice (especially from personal experience) would be greatly appreciated.
Thanks!
Matt