Key Takeaways

• Autodiscover JSON is Microsoft's new REST-based endpoint format for mail profile configuration, replacing the XML-only Autodiscover v1 protocol used since Exchange 2007.
• The JSON endpoint is served at https://outlook.office365.com/autodiscover/autodiscover.json and uses HTTP POST with OAuth 2.0 bearer token authentication instead of basic or NTLM credentials.
• Backward compatibility is maintained: the legacy XML Autodiscover endpoint remains active, but Microsoft has announced it will be deprecated in future Exchange versions.
• Schema changes are significant: JSON responses return a flattened, more structured payload with dedicated sections for service binding, SSL preferences, and account validation that XML could not represent efficiently.
• Migration is mandatory for organizations relying on custom Autodiscover scripts, third-party email clients, and any tool that parses raw XML from the legacy endpoint.

What Is Autodiscover JSON?

From XML to REST: A Protocol Overhaul

The original Exchange Autodiscover protocol, introduced with Exchange Server 2007, operated almost entirely through HTTPS POST requests returning XML envelopes. Clients sent an email address; the service responded with server URLs, credential requirements, and configuration metadata. While functional, the XML format had inherent limitations: verbose payloads, limited support for modern authentication schemes, and no native JSON serialization path.

Autodiscover JSON was introduced as part of Microsoft's broader migration toward cloud-native identity and configuration models. It serves the same fundamental purpose — automated mail client configuration — but through a RESTful HTTP interface that returns JSON-formatted responses. This aligns Autodiscover with the architectural patterns used by Microsoft Graph, Conditional Access, and modern identity platforms.

Core Technical Differences

At the protocol level, Autodiscover JSON introduces several critical shifts:

How Autodiscover JSON Works: Under the Hood

The Request Lifecycle

When a mail client or device attempts to configure a mailbox using Autodiscover JSON, the following sequence occurs:

1. Discovery Initiation: The client resolves the domain's DNS _autodiscover._tcp SRV record or uses the standard URL guess pattern (autodiscover.).
2. OAuth Token Request: The client obtains an OAuth 2.0 access token scoped to the target Microsoft 365 tenant using the appropriate authorization flow (interactive, device code, or client credentials).
3. HTTP POST to JSON Endpoint: The client sends a POST request to the .json endpoint with the JSON body containing the target email address and a valid bearer token.
4. Server-Side Resolution: The Autodiscover JSON service validates the token, resolves the tenant context, queries the Exchange Online configuration store, and constructs the response payload.
5. JSON Response Delivery: The server returns a structured JSON object containing service endpoints, protocol preferences, SSL settings, and account validation tokens.

Sample JSON Response Structure

{
  "protocol": "autodiscoverv1",
  "response": {
    "accountType": "email",
    "accountName": "user@contoso.com",
    "username": "user@contoso.com",
    "outboundServer": {
      "server": "smtp.office365.com",
      "port": 587,
      "encryption": "TLS",
      "authType": "OAuth2"
    },
    "inboundServer": {
      "server": "outlook.office365.com",
      "port": 993,
      "encryption": "SSL",
      "authType": "OAuth2"
    },
    "serviceBinding": {
      "endpoint": "https://outlook.office365.com/EWS/Exchange.asmx",
      "protocol": "EWS"
    },
    "accountValidation": {
      "token": "eyJ0eXAi...",
      "expiresOn": "2025-09-15T18:30:00Z"
    },
    "additionalUrls": [
      {
        "type": "ollb",
        "url": "https://outlook.office365.com/autodiscover/autodiscover.json"
      }
    ]
  }
}

Why the JSON Format Matters

The structural advantages of JSON over XML are not merely cosmetic. In enterprise environments where thousands of devices and mail clients query Autodiscover simultaneously, the reduction in parsing overhead and bandwidth consumption is measurable. Internal benchmarks from Microsoft indicate an average payload size reduction of approximately 40% when comparing equivalent configurations served as JSON versus XML. Furthermore, JSON