Forum Discussion

pazzoide76's avatar
pazzoide76
Iron Contributor
Jul 30, 2020
Solved

Autodiscover configuration in full hybrid

Hello, I have a question regarding the configuration of the autodiscover service. My infrastructure is full hybrid with a 2016 exchange server on premise. I have already moved the mail flow to o36...
exchange
hybrid
On-Premises
  • DeepakRandhawa's avatar
    DeepakRandhawa
    Jul 30, 2020
    Yes, you can point it to O365 without causing any issues to your environment.
    Below cmdlet will change the SCP entry to null so that your outlook does not query AD for mailbox info
    Get-ClientAccessService | Set-ClientAccessService -AutoDiscoverServiceInternalUri $ Null
    And yes you need to point your dns to autodiscover.outlook.com for both internal and external.
DeepakRandhawa's avatar
DeepakRandhawa
Iron Contributor
Jul 30, 2020
if you still have mailboxes on-prem then keep it pointing to on-prem else you can point it to O365.
pazzoide76's avatar
pazzoide76
Iron Contributor
Jul 30, 2020

I don't have any mailboxes on premises.
The on premise server has a connector that allows the relay of the email in an unauthenticated way because an old application must send email to the internet.

 

 

  • DeepakRandhawa's avatar
    DeepakRandhawa
    Iron Contributor
    Jul 30, 2020
    you can point your autodiscover to O365 then
    • pazzoide76's avatar
      pazzoide76
      Iron Contributor
      Jul 30, 2020

      DeepakRandhawa 

       

      Thanks for the reply.
      Since the article https://docs.microsoft.com/en-us/exchange/decommission-on-premises-exchange scenario 3 says:
      We recommend against removing Exchange and the hybrid configuration at this point. If you were to even start the process by pointing the Autodiscover Records to Exchange Online, you would immediately break some features like hybrid public folder access. You could change the MX record to point to Exchange Online Protection if it is not already, you could even remove some of the on-premises Exchange servers. However, you would need to keep enough in place to handle the remaining hybrid functions. Usually, this would lead to a very small on-premises footprint.
      Are you sure it can make the autodiscover service point on O365?
      If the answer is yes on the server on premise I have to type the command Get-ClientAccessService | Set-ClientAccessService -AutoDiscoverServiceInternalUri $ Null?
      Also do I have to point the dns record, both for internal and public dns, to autodiscover.outlook.com?

       

      Thank you

       

      Regards

      • DeepakRandhawa's avatar
        DeepakRandhawa
        Iron Contributor
        Jul 30, 2020
        Yes, you can point it to O365 without causing any issues to your environment.
        Below cmdlet will change the SCP entry to null so that your outlook does not query AD for mailbox info
        Get-ClientAccessService | Set-ClientAccessService -AutoDiscoverServiceInternalUri $ Null
        And yes you need to point your dns to autodiscover.outlook.com for both internal and external.

Resources