How to quickly verify if Autodiscover is working

How to quickly verify if Autodiscover is working

Autodiscover is an Exchange service that ensures seamless connectivity across various devices and applications, saving admins and users tons of time. That’s why diagnosing problems with the service as soon as they arise is essential.

Thanks to Autodiscover, Outlook clients are automatically configured after as little as entering a user’s email address and password upon the first login. But its job doesn’t end there – it’s also required to ensure Outlook-Exchange connectivity later on. In this guide, I’ll show you two quick and easy ways to verify if Autodiscover is working properly.

Using Powershell

Checking Autodiscover connection for a user is as simple as using a single cmdlet:Test-OutlookWebServices for the user you want to diagnose, i.e.

Test-OutlookWebServices -identity: [email protected] –MailboxCredential (Get-Credential)

The cmdlet first checks if it can connect to Autodiscover service and specifies its URL. Then it checks connectivity with all services defined by Autodiscover xml records, namely: Availability Service, Offline Address Book and Unified Messaging. The final result is a very short yet informative table:

Test-OutlookWebServices cmdlet

Using Outlook

Another way to verify Autodiscover service is by using an Outlook in-built tool. In order to do that, you have to follow those simple steps:

  1. Turn on MS Outlook, find its icon in the system tray and right-click it while holding ctrl key. From the context menu, choose “Test E-mail AutoConfiguration…”.

    Test Email AutoConfiguration

  2. Here, you can enter user’s credentials of the e-mail account you want to check. In order to verify Autodiscover service, check “Use Autodiscover” box and click “Test”. Autodiscover URL and information whether the connection succeeded can be found under Log tab.

    Test Email AutoConfiguration window

Both methods are quick easy to use and let you verify if Autodiscover Service works fine; however, it is clear that the latter has the advantage of requiring nothing more than Outlook. Furthermore, it provides more data, which comes in handy especially in case of an error. What is more, this tool can also be used to check EWS (Exchange Web Services) URL, OOF (Out of Office) URL on the Results tab, or to take a look at Autodiscover XML configuration file.

Autodiscover service is closely connected to the topic of migration – that is when it is especially prone to crashing and, at the same time, when its well being is crucial.

For those of you using Exchange 2007, check this article to see if maybe you should start planning your migration.

If you want to make migration much simpler and easier, check those CodeTwo products:

Tools for Exchange Server

Recommended articles

Exporting messages from mail queues on Exchange 2010/2013/2016/2019

Exporting messages from mail queues on Exchange 2010/2013/2016/2019

When a company migrates mailboxes between Exchange servers, they run the risk of losing emails that were in message queues. The gravity of this problem increases with the size of the organization and the amount of mail traffic - when hundreds of emails are sent every hour, the danger of overlooking them during the switch is quite high. Fortunately, a simple PowerShell script is all you need to avoid the setback. It is even useful as a final checkup measure before decommissioning the old server. Below you'll find steps required to perform this task.
Managing users’ Outlook rules from Exchange Management Shell (with PowerShell)

Managing users’ Outlook rules from Exchange Management Shell (with PowerShell)

Outlook rules (or inbox rules) can be controlled with PowerShell. Here's how.
How to quickly check installed software versions

How to quickly check installed software versions

Find out how to list and verify installed software on Windows by using PowerShell – both locally and remotely.

Comments

  1. Hey,

    the first check method results in failure of autodiscover.
    Outlook check method tells all is ok.

    Any idea?

    Regards Jay

    • avatar
      Adam the 32-bit Aardvark says:

      Hi Jay,
      This is a highly untypical behavior. I would start which checking if everything is ok with the PowerShell connection. And the important question is – does the user (or users) experience any problem connecting to the mailbox?

    • avatar
      Adam the 32-bit Aardvark says:

      Hi Jack,
      Yes, the cmdlet has been tested in Exchange 2016 and it worked without any problems.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.