Skip to main content
All CollectionsSign In Solutions PlannerPlanner & Exchange / O365
(v2) Why - migrate from EWS to Microsoft Graph
(v2) Why - migrate from EWS to Microsoft Graph
Reg Gray avatar
Written by Reg Gray
Updated over a week ago

Your organization is currently leveraging the Planner Cloud service and has a Planner solution that integrates with the Exchange Web Services (EWS) API.

This guide is tailored to help you understand the reason why it is needed to migrate you to Microsoft Graph API.

Why is it relevant to migrate from EWS to Microsoft Graph API?

  • We will sunset support of EWS API for our Planner Cloud customers by the end of March 2025

  • Microsoft has announced the EWS will no longer receive feature updates for Office 365/Exchange Online

  • Microsoft has announced that EWS be sunset too

Enhanced Security and Compliance

Microsoft Graph adheres to modern security standards, such as OAuth 2.0. By using access tokens, developers can ensure secure interactions with Exchange Online. Additionally, Microsoft Graph allows for fine-grained permissions, which in relation to Planner will enable customers to grant access only to the necessary scopes used by Planner.

This enhances security and aligns with compliance requirements.

Future-Proofing Your Solution

You’ll benefit from ongoing updates, security enhancements, and expanded features without worrying about legacy APIs

What are the prerequisites?

  • New Planner Office add-in for Microsoft Outlook (The new add-in can be deployed server side as an Exchange Manifest)

  • Consent of permissions on Azure - which requires an Azure admin to perform the consent

How will the upgrade impact the users?

  • The end users will not experience any changes

Did this answer your question?