Blog Post

Exchange Team Blog
2 MIN READ

Announcing Public Preview: Exchange Online Admin API

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Nov 17, 2025

Today, we are announcing the Public Preview of the Exchange Online Admin API – a REST based, cmdlet style administrative surface specifically designed to help organizations migrate away from EWS for specific Exchange admin scenarios and modernize automation workflows over HTTP.

Context

Exchange Web Services (EWS) is scheduled for deprecation in October 2026, yet many organizations still depend on EWS for specific Exchange administrative tasks due to unavailability of the alternate API for these scenarios. The Admin API provides a REST based, cmdlet style alternative for these scenarios, enabling modern automation while preserving familiar semantics for Exchange administrators.

Note: The Admin API is not a full REST replacement for Exchange Online management. It is designed only to cover the subset of Exchange Online Administrative capabilities that provide alternative for administrative scenarios currently available through EWS. For complete Exchange management, we recommend using Exchange Online PowerShell.

Capabilities available in Public Preview

The Admin API Public Preview includes 6 endpoints. The list of endpoints and supported functionalities are as follows:

  • OrganizationConfig — Read tenant wide MailTips related configuration.
  • AcceptedDomain — List accepted domains and core domain settings for the tenant.
  • Mailbox — Read mailbox properties and manage Send on behalf delegates (view/update).
  • MailboxFolderPermission — List, grant, modify, and remove folder level permissions (Inbox, Calendar, subfolders).
  • DistributionGroupMember — Retrieve membership for distribution groups.
  • DynamicDistributionGroupMember — Retrieve membership for dynamic distribution groups.

For detailed documentation, including request patterns, and endpoint details, visit:

For the most up to date guidance on EWS migration see https://aka.ms/ews1Page.

Availability and roadmap

  • Public Preview (Worldwide): Available starting November 17, 2025. Use this phase to evaluate functionality, plan migrations, and share feedback on any gaps between EWS admin scenarios and the Admin API.
  • General Availability (Worldwide): Yet to be announced
  • Sovereign environments (GCC, GCC High, DoD): Yet to be announced

Currently, API responses include extra properties, but only those listed in each endpoint's documentation will be available at GA. Please refer the individual endpoint documentation for the list of properties that will be available in GA. Any updates to the list of output properties will be announced during the GA release.

Share feedback

Your input during Public Preview is essential. Please use our feedback form to report issues, gaps, or suggestions. Your feedback will help us refine the API and documentation ahead of GA.

Exchange Online Administration and EWS Deprecation teams

Published Nov 17, 2025
Version 1.0

10 Comments

  • MikeCrowley's avatar
    MikeCrowley
    Iron Contributor

    Cool! But some initial questions:

    1. Why isn't this behind Microsoft Graph? Is Graph no longer the goal for M365 API unification?
    2. Why would we use POST to GET object properties?
    • RalfJansen's avatar
      RalfJansen
      Copper Contributor

      I suppose because it isn't a clean REST API that fits in the more clean Graph approach. If you look at the bodies send via POST you see that you have to send the Cmdlet Name and parameters just like you could have done using the cmdlet in Powershell. So we can assume that they simply execute those Powershell cmdlets server side. Easy cheap shot to get something working without the burden of a clean new API design fitting into Graph. This API feels more like an abomination to me. Or phrased differently to replace an API with a different one and then feeling the need to create a third API to fill parts of the most abysmal holes it leaves open does not feel right.

  • ebuka's avatar
    ebuka
    Copper Contributor

    Does this API allow Creation of Distribution List or Shared Mailboxes functionality?

    • Vivek's avatar
      Vivek
      Icon for Microsoft rankMicrosoft

      Hi Ebuka, these API's do not support the creation of Distribution Lists or Shared Mailboxes. For these functionalities, you need to use the EXO PowerShell module or Exchange Admin Center.

  • woelki's avatar
    woelki
    Iron Contributor

    Is it possible due to these changes that there have been updates in the HCW as well?
    Since yesterday there are issues in downloading the Hybrid Updater Agent during the HCW process.

    • Nino_Bilic's avatar
      Nino_Bilic
      Icon for Microsoft rankMicrosoft

      We are aware of download issues (they are totally independent from this) and are working on it.

    • Vivek's avatar
      Vivek
      Icon for Microsoft rankMicrosoft

      This release of Exchange Online Admin API does not have any impact on the HCW.

  • joan123123's avatar
    joan123123
    Copper Contributor

    Why not put this functionality into Microsoft Graph? Great news but please reconsider where to put the functionality