Continuity Release Notes

This page lists what shipped in each release of CloudM Continuity, most recent first.

Version 1.1.0.0 — July 2026

This release introduces two major capabilities: Recovery Sync, which returns data to Microsoft 365 once an outage is over, and Multi-Policy Management, which lets you run several sync policies side by side.

Recovery Sync

Until now, Continuity has kept a synchronised copy of your users' mail in Google Workspace, ready for an outage. Recovery Sync completes the loop. When a Microsoft 365 outage ends, you can now sync everything your users did in Google Workspace during the outage back into Microsoft 365, so nothing is lost.

• A new Recovery page in the sidebar is your home for starting, monitoring and reviewing recoveries
• Starting a recovery is simple: pick a recovery start date and all mail synced from that day onward is recovered. Users are included automatically — everyone with an active policy and a completed initial sync — and the dialog shows how many users that is before you confirm
• While a recovery runs you see items synced counts for each user, updated every few minutes
• When it finishes, a summary shows the outcome for every user: recovered successfully, completed with warnings, or failed
• If a recovery fails or completes with warnings, you can retry it. A retry re-runs the recovery for all users in it, which makes sure anything that arrived in Google Workspace after the original run is also picked up. Items that already exist in Microsoft 365 are never duplicated
• Once you have reviewed a completed recovery, finish it to move it into the historic recoveries list and clear the way for the next one. Retries are kept as separate runs, so the full history is preserved

Recovery covers mail in this release. Recovered messages are placed into the right folders in Microsoft 365, and any folders that don't exist yet are created automatically. Recovery events also appear in the audit logs. To learn more, see Understanding Recovery Sync.

Multi-Policy Management

Tenants are no longer limited to a single active sync policy. You can now create as many policies as you need and run them all at the same time, each with its own configuration, sync frequency and user selection.

• The Policies page is now an ordered list. A policy's position sets its priority, with the top policy taking precedence. Drag and drop to reorder
• If a user is matched by more than one active policy, the highest-priority active policy applies. Paused policies are skipped, so if you pause a policy, the next one down takes over for any overlapping users on the next sync cycle
• The Sync Status page and user details now show which policy is actually applied to each user, and flag when a user is also matched by other policies
• New policies are added at the lowest priority, and priority changes take effect on the next sync cycle without interrupting syncs already in progress
• Licensing counts unique users: a user who appears in three policies counts once against your licence

Once a user has been set up in Google Workspace by a policy, they keep that same Google Workspace account even if a different policy later takes priority for them. The newly applied policy's settings, such as sync frequency, apply from that point on, but the user's destination account and its address never change. This keeps their synced history in one place. To learn more, see Using multiple sync policies.

Version 1.0.0.0 — May 2026

The first release of CloudM Continuity: continuous synchronisation of Microsoft 365 mail into Google Workspace, keeping a ready-to-use standby environment for your users in the event of a Microsoft 365 outage.

• Mail sync — Initial bulk sync followed by scheduled delta syncs from Microsoft 365 to Google Workspace, preserving subject, body, attachments, sender, recipients and dates. Folder structure is mapped to Gmail labels, and read/unread state, message moves and deletes are kept in sync
• Sync policies — Define which users to sync using selection rules (department, employee type, job title), preview the matching user count before activating, and configure destination domain, username suffix, sync frequency and deletion delay
• Automatic user provisioning — Google Workspace accounts are created automatically for matched Microsoft 365 users, each with a unique password available for retrieval
• Connections — Microsoft 365 source connection (Azure AD app with certificate-based authentication) and Google Workspace destination connection (service account with domain-wide delegation), with built-in connection testing
• Dashboard — Data synced, users synced and success/failure metrics, sync pipeline visualisation, sync freshness, and service health indicators
• Sync Status page — Filterable, sortable user table with per-user sync history, item counts and error details
• Audit logs — All system events logged with severity levels and full filtering by actor, context, event type, severity and date range
• Roles and access control — Super Admin, Admin and Viewer roles, with user invitations and role management per tenant
• Licensing — Licence tiers (Basic, Standard, Premium) governing sync frequency and user limits, with expiry warnings and a grace period