Overview
Microsoft has announced the retirement of Exchange Web Services (EWS) in favor of the Microsoft Graph API, with blocking of EWS requests from third-party apps scheduled to begin on October 1, 2026.
In alignment with Microsoft’s direction, Cloudally will be migrating its Microsoft Exchange Online and Groups/Teams backup services from EWS to Microsoft Graph API.
This update ensures improved security, long-term platform support, and alignment with Microsoft’s modern API strategy.
Migration Timeline
- Starting May 2026 (Release 26.2)
Cloudally will update its application to use the necessary Microsoft Graph API permissions. Customers will be prompted to reauthorize their Microsoft Exchange and Groups/Teams backup tasks and grant consent to the new required permissions.
While these permissions are not immediately required for backup functionality, completing the setup now will ensure customers are fully prepared for the migration before Microsoft’s deadline. Customers who complete this step will gradually be transitioned to Graph API–based backups in the background, with no additional action required.
Reauthorization notifications will be shown within the Cloudally customer portal:
Note:
The orange indicator reflects a reauthorization requirement and is independent of the backup health status (Succeeded / Partially Succeeded / Failed).
This notification will be displayed regardless of the current backup status, and backups will continue running as usual while it is shown.
- June 30, 2026 – Early Microsoft EWS Deprecation
Microsoft will disable EWS access earlier than the general deadline for the following license types:
- Exchange Online Kiosk
- Microsoft 365 / Office 365 F1
- Microsoft 365 / Office 365 F3
As of June 30, 2026, EWS-based access for these licenses will no longer be supported by Microsoft.
- October 1, 2026 – General EWS Retirement Deadline
October 1, 2026 marks Microsoft’s general retirement of EWS. From this date forward, EWS-based backups will no longer be supported. All customers must be transitioned to Microsoft Graph API by this point.
What Action Is Required from Customers
- Reauthorize Microsoft Exchange and Groups/Teams backup tasks when prompted to avoid service interruption.
- Complete reauthorization as early as possible, preferably before the end of June 2026
Customers who do not immediately reauthorize will continue to be protected using EWS-based backups until Microsoft’s October 1, 2026 deadline. Early reauthorization is strongly recommended to ensure a smooth and controlled transition.
Known Microsoft Graph API Limitations
Microsoft Graph API does not yet support all Exchange data types. Once Graph-based backups are enabled, the following content will no longer be backed up:
- Exchange Online Archive
- Exchange Public Folders
All historical backup snapshots created using EWS will be retained and remain accessible. However, these data types will no longer be included in new backups once Graph API is in use.
Frequently Asked Questions
1. When will this change take place?
The transition will occur in phases:
- May 2026 (Release 26.2): Customers will be prompted to reauthorize their Exchange and Groups/Teams backup tasks with new Microsoft Graph permissions.
- June 30, 2026: Microsoft will disable EWS earlier for certain license types (Kiosk, F1, F3).
- October 1, 2026: Full retirement of EWS; all customers must be on Microsoft Graph API by this date.
2. What action is required from customers?
From May 2026, customers are required to reauthorize their Microsoft Exchange and Groups/Teams backup tasks and grant consent to the new Microsoft Graph API permissions when prompted. Early reauthorization (before the end of June 2026) is strongly recommended.
3. What happens if a customer does not reauthorize immediately?
If a customer does not reauthorize right away, backups will continue to run using EWS‑based access until Microsoft blocks access to EWS. However, delaying reauthorization increases the risk of a rushed or disrupted transition closer to the cutoff date.
4. Will backups stop during the transition?
No. Backups will continue to run as usual while reauthorization notifications are shown. Customers who complete reauthorization will be gradually transitioned to Graph API–based backups in the background, with no additional action required.
5. Is the backup task’s status dependent on Graph API reauthorization?
No. The reauthorization prompt is independent of the current backup status (Succeeded, Partially Succeeded, or Failed). All applicable customers will see the notification regardless of task status.
6. Are there any limitations when using Microsoft Graph API?
Microsoft Graph API does not yet support all Exchange data types. Once a tenant is fully transitioned to Graph‑based backups Exchange Online Archive and Exchange Public Folders will no longer be supported.
7. What happens to historical backups created using EWS?
All historical backup snapshots created using EWS will be retained and remain accessible. Only new backups after the transition will be affected by Graph API limitations.
Cloudally Commitment
Cloudally will continue to monitor Microsoft Graph API enhancements and expand backup coverage as Microsoft adds new capabilities. We are committed to transparent communication and a smooth customer experience throughout this transition.
Need Help?
If you have questions or need assistance with reauthorization, please contact Cloudally Support or refer to upcoming documentation and in-product guidance.