Link to home
Start Free TrialLog in
Avatar of SupermanTB
SupermanTB

asked on

On-Prem Exchange to Office365 Autodiscover best practice

I'm about to migrate a company from SBS 2011 Exchange to Office365 for their email.  In doing this in the past, I've always run into issues related to reconfiguring the Outlook profile.  It always wants to configure the on-prem Exchange account.  I've always been able to either disable the user's mailbox in Exchange, make registry edits on the user's computer to get the autodiscover to pick up Office365 instead of Exchange.

This upcoming migration is for ~75 users.  I'd like to be more efficient with making sure reconfiguring the Outlook profiles pick up Office365 instead of Exchange for the autodiscover.  What's the best practice to ensure that happens?

Thanks very much.
Avatar of Saber
Saber

That depends if you are going to maintain an On-Premise environment. If so you are going to need a Hybrid Exchange server setup and the internal / external autodiscover should point to the hybrid server(s). The hybrid server will go through the discover logic and point the client to the connection endpoint for their mailbox.

Meaning if it is on-prem, the users Outlook client will connect to OnPrem. If it's in O365, autodiscover will issue a redirect to O365 for the Outlook client to get it's connection endpoint from there.

But if you are totally just going to migrate to O365, then just change the Autodiscover DNS records for your domain to the O365 autodiscover endpoint.

Due to Outlook clients caching the last known good autodiscover URL, you may want to read over this article and put in place a group policy to exclude the last known good autodiscover URL.

https://support.microsoft.com/en-us/help/3073002/after-migration-to-office-365,-outlook-doesn-t-connect-or-web-services-don-t-work
SOLUTION
Avatar of Vasil Michev (MVP)
Vasil Michev (MVP)
Flag of Bulgaria image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of SupermanTB

ASKER

I am not going to be needing the on-prem environment in the future.  

So basically, make sure the autodiscover in the DNS points to Office365 and deploy the registry changes to all computers?
@SupermanTB

Correct!!
Well you can also disable Autodiscover on the on-prem box, disable SCP, remove the A record, etc. In which case you will not need the reg keys. I simply prefer using the client-side solution.
Well you can also disable Autodiscover on the on-prem box, disable SCP, remove the A record, etc. In which case you will not need the reg keys. I simply prefer using the client-side solution.

Which creates more administrative overhead.
Saber....when you say disable Autodiscover on the on-prem box do you mean just change the DNS?  I'm not familiar with disabling SCP.  Would you mind elaborating a bit there or proving some quick instructions?  Thanks very much.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial