Exchange publishes service connection point (SCP) objects in AD DS, which allows Autodiscover requests to be routed to servers based on Active Directory sites. Table 1: Autodiscover endpoint candidate sources Place to lookįor domain-joined clients, this is the first place to look. In the case where multiple candidates are found, Autodiscover also defines a way to generate and prioritize the list. Luckily, Autodiscover defines a limited number of places for you to look. Three phases of the Autodiscover processīefore you can use Autodiscover, you have to locate the right Autodiscover server for your user.

The following figure shows the three phases of the Autodiscover process.įigure 1. The ExchangeService.AutodiscoverUrl method in the EWS Managed API implements all three phases of this process for you, so if you are using the EWS Managed API, you don't need to worry about implementing Autodiscover yourself. If none of your candidates worked out, you move on to phase three, which represents a 'last ditch' attempt to find an Autodiscover endpoint. In phase one, you generate a list of potential Autodiscover servers, and in phase two, you try each server in your list until you (hopefully) get a successful response. The Autodiscover process essentially has three phases. Autodiscover works for client applications that are inside or outside firewalls and will work in resource forest and multiple forest scenarios. For Exchange Web Services (EWS) clients, Autodiscover is typically used to find the EWS endpoint URL, but Autodiscover can also provide information to configure clients that use other protocols.

Most users know their email address and password, and with those two pieces of information, you can retrieve all the other details you need to get up and running. The Exchange Autodiscover service provides an easy way for your client application to configure itself with minimal user input. Learn about the Autodiscover service in Exchange.

Exchange 2010 autodiscover url