POX Autodiscover request for Exchange

Exchange Server 2013

The Autodiscover request contains a query for a user's client access configuration.

Last modified: August 18, 2014

Applies to: Exchange Online | Exchange Server 2007 | Exchange Server 2010 | Exchange Server 2013 | Office 365

Description

The following XML example shows an Autodiscover request body.

Code

XML
Copy 
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
   <Request>
     <EMailAddress>user@contoso.com</EMailAddress>
     <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>
   </Request>
 </Autodiscover>

Request Headers

The following HTTP headers are optional when sending Autodiscover requests.

Table 1.  HTTP request headers

Header

Description

X-MapiHttpCapability

If present and set to "1", indicates that the client is requesting information that can be used to connect to the server by using the MAPI/HTTP protocol. This header is applicable to clients that implement the MAPI/HTTP protocol.

X-ClientCanHandle

This header contains a comma-delimited list of capabilities that the client supports. The possible values are specified in Table 2.
Table 2.  X-ClientCanHandle header values

X-ClientCanHandle value (case-insensitive)

Minimum server version

Description

Negotiate

15.00.0995.014

If this value is present, the server will return a value of "Negotiate" in the AuthPackage (POX) element if the server is configured to accept Negotiate authentication. If this value is not present, the server will not return a value of "Negotiate" in the AuthPackage element.

ExHttpInfo

15.00.0995.014

If this value is present, the server will return a Protocol (POX) element with a Type (POX) element set to "EXHTTP" if the server is configured to accept RPC/HTTP connections. If this value is not present, the server will not return a Protocol element with a Type element set to "EXHTTP".

Request Elements

The following elements are used in the request body:

Note Note

The LegacyDN (POX) element can be used in place of the EMailAddress (POX) element.

Version differences

The X-MapiHttpCapability header is available in Office 365, Exchange Online, and on-premises versions of Exchange starting with build 15.00.0847.032 (Exchange Server 2013 SP1).

The X-ClientCanHandle header is available in Office 365, Exchange Online, and on-premises versions of Exchange starting with build 15.00.0995.014.

Show: