Apr 2026 - 4.15.0 Release Notes

Written By Nikki Klukowski (Administrator)

Updated at May 4th, 2026

x360­­­Cloud 4.14.0 Release Notes

     Version

      4.15.0

 

     When

     Europe – April 29, 2026

     United States, Canada – April 30, 2026

 

     Goals

  • To improve backup status reporting for Microsoft Teams.
  • To fix issues related to backup and restore functions.

 

 

 

 

 

 

 

 

 

 

 


Improvements 

Microsoft Teams backup status reporting 

Previously, the backup status for Microsoft Teams was only visible under the Accounts menu, where Teams protection is managed. Starting with this version — and continuing in future releases — we are increasing the visibility of Microsoft Teams protection status across other areas of x360Cloud.

An organization-level summary of all backed-up Teams is now available on the organization-level Dashboard and Reports pages. This summary provides a breakdown of Teams by backup status, including how many Teams are successfully protected, currently being backed up (backup in progress), onboarding, and other relevant states.

 

The same breakdown is also available on the Reports page. In the next release, we are adding a detailed listing of all Teams along with their corresponding backup status information.

 

Fixes 

  • Fixed the issue when Google Workspace Calendar backups were partial when email address in in "mailto:" field is not in a proper format for iCalendar items.
  • Added an advanced retry mechanics for intermittent errors coming from Google API during Drive data backups.
  • Fixed the issue when Microsoft Exchange emails were restored to a point in time without a proper folder hierarchy.
  • Optimized the SharePoint and OneDrive data restoration for large files and in conditions of throttling from Microsoft 365. By increasing timeouts and the maximum allowed upload chunk size, the system can now complete restores, that previously took up to 30 hours, in 5 minutes.
     

Known issues  

  • It was confirmed on March 27, 2026, that Microsoft applied a patch to correct how Exchange Online enforces Exchange Web Services (EWS) access. Previously, some environments were able to access mailboxes via EWS even when it was not explicitly enabled (i.e., $Null status). After Microsoft corrected this behavior, EWS must now be explicitly enabled at both the organization and mailbox levels for Archive Mailbox backups to succeed. Review this Microsoft blog post for reference: The way to control EWS usage in Exchange Online is changing.
  • The solution to this problem is described in the following article: How EWS Access Impacts Backup of Archive Mailboxes in x360Cloud
     

 SUPPORT | 800-352-0248