Forum Discussion
Deleted
Sep 04, 2017Azure AD Sync to On-Prem AD
Hello, I have Azure AD with about 50 users. These users were made when we purchased Office365. Let's say domain on Azure AD is example.com. (username@example.com) Locally, we use on-prem AD to auth...
Deleted
Sep 04, 2017"You can use your public domain that is registered on Azure AD in your on-premises AD changing the UPN of the users to that domain and then match the email."
Is it okay to use public domain internally? My understanding is that you should not use resolvable domain names internally?
If that is okay, then I will have equal usernames on both on-prem AD and Azure AD.
When I use AD Connect, will it automatically softmatch ?And will it sync passwords FROM Azure AD to On-Prem AD or other way around?
Is it okay to use public domain internally? My understanding is that you should not use resolvable domain names internally?
If that is okay, then I will have equal usernames on both on-prem AD and Azure AD.
When I use AD Connect, will it automatically softmatch ?And will it sync passwords FROM Azure AD to On-Prem AD or other way around?
Sep 05, 2017
Hi Januka,
You only will change the UPN, not the public domain internaly, just the way the user login on Office 365.
When AD Connect will softmatch the password is from AD, you source of identity will be AD not Azure AD.
You have to setup the AD Connect, just do a scope to a few test users and after you see how it works, send communications to the end users that after date/hour x their passwords on Office 365 will be the same that are from AD.