.LOCAL domain question ..... Office 365 Directory Sync.

Greetings. We're using FIM with DirSync for Exchange Online Protection now, but will be moving to the full Office 365 shortly.

A recommended tool from Microsoft is IDFix.  This scans your active directory prior to a sync to identify objects that will not sync correctly to Azure AD.

IDFix notifies us that all objects with .LOCAL SMTPs will not sync correctly.

That's essentially every mail enabled object.

Question:  do we even need .LOCAL user addresses any more ?  All mail uses our fqdn, including internal.

Thanks much.
Stephen

Mail server currently is Exchange 2010 SP3.  All certs are trusted (not internally generated CA).
lapavoniAsked:
Who is Participating?
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:
Your AD domain can be .local, but there is no reason any of your users should have a .local proxyAddress.
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
jparedisCommented:
As Cliff said, there is no need to change the entire config of your domain. That part can continue on using .local as a suffix.

However, all the users you want to enable in Office 365 need an internet - routable UPN. (this is not entirely, through, workarounds exists, see http://vanhybrid.com/2014/04/10/windows-server-2012-r2-update-enables-adfs-to-use-alternative-login-id-possibly-removing-the-need-to-have-an-internet-routable-upn/ )

If you cannot use 2012 R2 ADFS, or you dont want to implement alternative login id, you have to follow the steps, properly described in http://technet.microsoft.com/library/jj151831.aspx#BKMK_UPN
0
lapavoniAuthor Commented:
Thanks for the information.  We're running 2008 (functional level), but the TechNet link was useful. We already have the correct alternative UPNs, so it's just a matter of removing those .local proxy addresses from each mail-enabled account.
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
Office 365

From novice to tech pro — start learning today.

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.