Forum Discussion

David Kramkowski's avatar
David Kramkowski
Copper Contributor
Dec 07, 2017

Azure AD Sync functionality

I just tested out the Azure AD Sync functionality to sync between a local AD domain and Azure AD. What I gathered from reading through and setting it up is that in order to sync to Office365 or to ...
azure active directory
Paul Cunningham's avatar
Paul Cunningham
Steel Contributor
Dec 08, 2017
David Kramkowski wrote:

 

There really is no way we could change all of our users from .local to .com, due to the way our users are spread out along with the way our data security is set up, tied to the .local UPNs, to try and change it would be quite the nightmare.

What does that mean though? What have you designed and implemented on-prem that makes you incompatible with Office 365, and that can't be changed in any way?

 

Putting that another way, sometimes when customers say "we can't do this, so how can me make Microsoft/whoever work differently?" I get them to flip the question around. Imagine there's absolutely no way that Microsoft can make the .local domain work for you (you can't add a .local domain to your tenant because it can't be verified, and there's no workaround of "mapping" a .local to a verifiable domain), what is actually possible to change in your current environment to make things work?

 

If it's a "nightmare", so be it. It might be necessary.