![]() ![]() ![]() Endpoint located using SCP queryĪutodiscover unable to answer query as mailbox in O365. Start from beginning using new SMTP address: starts over. Since the dialog cannot be resized the bottom portion was overlaid so all results were in a single image for readability purposesĪutodiscover endpoint located using SCP queryĪuthentication successful to Autodiscover web service using logged on credentialsĪutodiscover unable to answer query as mailbox in O365.Each response line has been manually numbered.This has been edited to show the following: The below screen shot shows the steps Outlook has gone through to locate the correct Autodiscover endpoint for this Office 365 mailbox. Guesssmart and Secure Guesssmart are for POP and IMAP clients so they are cleared to remove unwanted fluff from the results. We are using the Test E-Mail AutoConfiguration tool to review the Autodiscover process. This is the Outlook 2013 ProPlus client, version. Testing Outlook Autodiscover Lookup Process Now that we know the infrastructure, let’s see what Outlook does. Leave a comment and let me know your thoughts please. The newer portal has addressed this, maybe I’ll add a post with details. Ignore the GUI, and check the status of the custom domain using Get-MSOLDomain using PowerShell. This is a common configuration issue as the Office 365 portal complains about missing DNS records. Note that in a hybrid configuration the external Autodiscover namespace must point back to the on-premises Exchange infrastructure and not to Office 365. This is for points to the external firewall interface which is configured to pass the traffic to the Exchange 2010 CAS server. That is great for internal domain joined machines, what about external or workgroup machines?įor external clients, Autodiscover is configured as a standard A record in the external DNS zone. Setting the AutodiscoverServiceInternalURI is the value which will be returned to Outlook when it does a SCP query. Please review the myth busting post for the background on this urban legend. ![]() Note that we are NOT setting URLs on the Autodiscover VirtualDirectory. Get-ClientAccessServer | Select Name, *URI | Format-Table -AutoSize In short the Exchange 2010 CAS server has the AutoDiscoverServiceInternalURI set to the namespace. This is the URL that users will leverage to get the XML response from Exchange. The Autodiscover namespace in this lab is. They are logging onto a domain joined machine which is located on the corporate network, using their credentials. Our test mailbox was moved successfully to Office 365. This Exchange 2010 SP3 lab has a hybrid configuration with Office 365. ![]() The intent is to look at how Outlook will locate the correct Autodiscover endpoint in a hybrid environment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |