AD Connect using .local on-premises domain

Azure AD Connect for hash password sync.  Have a client with a .local on prem Active Directory domain.  The Azure AD Connect wizard is showing their .com domain (for their website and email) is published and verified but the .local is not verified.  I have read tons of documentation, added the .com domain suffix to the on prem AD and changed the UPN of all users to use the @abcd.com verified domain.

Now as i go back to the wizard it still shows the .local as not verified (which i expect) but says the users will not be able to login to Azure services using SSO because not all the domains are verified.  I am stuck.  Will my users with the verified domain UPN still sync and work correctly but anything using the .local domain will not?  Or will they all flat out fail?  I am having difficulty finding specifics about this with Microsoft documentation.  Thanks!
aungelbachAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Users with a verified UPN that are synced will be able to log into cloud services and take advantage of SSO.  In the Azure AD portal is a download for the "IDFix" tool that can check all of your users and let you quickly fix errors as well.  There are plenty of old SBS (which defaulted to .local) installs out there that use Office 365 and AADConnect successfully, just as an example of the wide deployment of .local and successful syncing.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aungelbachAuthor Commented:
Ah I see, so as long as I change the UPN of the users that will be actually using the SSO I can ignore the other accounts such as service accounts and administrator etc.  We are only sync'ing users that have Exchange mailboxes at Azure currently so that is my focus.
0
timgreen7077Exchange EngineerCommented:
.local is not a routable internet domain so it will not sync, and if the user's UPN uses the .local, then they will not be able to sync via ADConnect. You will need to add additional UPN suffixes to you domain and then change the user's UPN to that new domain. see the below link for assistance.

https://support.office.com/en-us/article/how-to-prepare-a-non-routable-domain-such-as-local-domain-for-directory-synchronization-e7968303-c234-46c4-b8b0-b5c93c6d57a7
0
aungelbachAuthor Commented:
Thanks Tim that is what i did.  I used their verified .com domain, added it to AD then changed the UPN for those users to utilize the .com suffix for their UPN.
0
timgreen7077Exchange EngineerCommented:
The wizard will still see .local because that is your domain, but the user's will be logging in via the new UPN and it should be fine.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
sso

From novice to tech pro — start learning today.