Forum Discussion
Setup up autoDiscover In On-Perm DNS to integrate with O365
hntaurus Yes, you should do that as well to avoid your clients connecting to the old namespace after migration. In fact, you don't need this anymore and after your cutover, you can decommission Exchange as well.
What you would need to do when your mailboxes are in Exchange Online is to change the serviceBindingInformation parameter of the service connection point in either ADSI Edit or AD Sites and Services. The link below shows how to do that.
The SCP can be set to
https://autodiscover.outlook.com/autodiscover/autodiscover.xml and this should take care of autodiscover for any Outlook clients inside your network.
Thanks a lot for your prompt reply
Do I need to create SRV and CNAME for that auto discover on my Internal DNS as well?
hntaurus please use Exchange Management Shell to change it, not ADSIEDIT 😉
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://autodiscover.outlook.com
Disable-OutlookAnywhere –Server <ServerName>
You only have to change/add the CNAME record in your external DNS after migration.
- Hi Dominik,
I have fully hybrid env with exch2010, and I just run AutoDiscoverServiceInternalUri $Null
So how do I retrieve old value?
TAaussupport what do you want to achieve? The old value is often your Autodiscover URL e. g. https://autodiscover.domain.tld/Autodiscover/Autodiscover.xml
Thanks a lot for your time
I see you mentioned a command about Outlook Anyehre
DO I need to disable that one as well?
hntaurus Yes, you should do that as well to avoid your clients connecting to the old namespace after migration. In fact, you don't need this anymore and after your cutover, you can decommission Exchange as well.
Good call I agree, I would avoid using ADSIEdit unless you absolutely have no choice. The Exchange Shell method is absolutely the way to go.
Sure, I'll do it from exchange
and I guess by doing that I should not be worried about outloook clients finding the right path to connect to O365 ?
