Forum Discussion
Autodiscover configuration in full hybrid
- 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.
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.
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
- 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.Hello dear,
I have a question related to similar case, I have migrated all users from Exchange 2010 to Exchange 2016, we still have both Exchange servers but users mailboxes are on the 2016, we have two issues I think both are related to the autodiscover, whenever a user create a new meeting and add attendees from the same company (domain) they cannot see the free/busy time and the same if they add a Calendar of meeting room (resource) it shows no connection at the top of the Calendar of that meeting in their Outlook!
I have read many articles and most of them they say that "After the mailbox move is complete, Exchange Server 2013 or Exchange Server 2016 continues to proxy the EWS request to Exchange Server 2010. Exchange Server 2010 responds with a 302 redirect back to Exchange Server 2013 or Exchange Server 2016"
What settings/tuning do I need to fix on 2016 so we overcome this issue?
Thanks.
Muawya Ali
