A cloud-based service included in Microsoft 365, delivering scalable messaging and collaboration features with simplified management and automatic updates.
Microsoft Graph and EWS Parity - Roadmap clarifications and updated ETAs
Hi Microsoft team,
I'm currently investigating the migration of an integration from Exchange Web Services (EWS) to Microsoft Graph and looking for clarification on the remaining parity gaps to help inform our technical design.
According to the EWS deprecation and parity roadmap, several capabilities, including Contact Lists, Additional Contact Properties and Notes, had target availability dates of Q3 2026.
As those dates have now passed, could the team provide an update on their current status and revised ETAs?
Our primary interest is Contact Lists, which we're investigating as a key dependency for our proposed design, and potentially Additional Contact Properties, depending on the functionality available.
With EWS disablement already underway and the final shutdown scheduled for 1 April 2027, we're trying to establish what functionality we can reliably plan around and whether there will be sufficient time for implementation, testing and migration.
I'd appreciate clarification on the following:
1. Contact Lists and Additional Contact Properties
- What is the current release status of each capability?
- When are they expected to reach general availability and be supported for production use?
- Are there any known limitations or outstanding functionality that could affect migration from EWS?
2. Roadmap commitments and EWS retirement
The published roadmap states:
If an EWS capability isn't listed in this roadmap table, don't plan on a corresponding Microsoft Graph or Exchange Admin API capability being available before EWS is fully disabled.
Can we conversely expect that capabilities included in the roadmap will be available before the April 2027 shutdown?
If not, how should developers plan for dependencies on those capabilities?
3. Migration timelines and alternatives
If these capabilities become generally available close to the retirement deadline, there may be limited time to implement, test and deploy a replacement.
- Is there an expected migration window between general availability and EWS retirement?
- If either capability isn't production-ready in sufficient time, is there a recommended alternative or supported migration approach?
4. Updated parity roadmap
Are revised ETAs available for the remaining capabilities whose Q3 2026 targets have passed?
If there are existing updates, documentation, release notes or other official resources that address these questions, links to those would also be greatly appreciated.
We're looking to make an informed technical design decision based on the expected availability of these capabilities, rather than make assumptions about the published target dates.
If someone from the Microsoft Graph or Exchange product team responsible for these capabilities could provide clarification, or direct us to the appropriate contact or channel, that would be very helpful.
We're looking to progress our technical design as soon as possible, so any initial guidance or direction within the next two business days would be greatly appreciated.
For reference, Microsoft's Exchange Online EWS retirement announcement confirms the phased disablement process and final April 2027 shutdown.
Thanks in advance,
Tim