Skip to main content

Starting a Recovery

Once a Microsoft 365 outage is over, you start a recovery from the Recovery page in CloudM Continuity. This article covers what to check first and how to start.

Before you start

Check Why
Microsoft 365 is stable Recovery writes data into Microsoft 365. Starting while the service is still recovering can cause user failures. Wait until Microsoft confirms the service is restored.
Both connections are healthy Recovery reads from Google Workspace and writes to Microsoft 365, so both connections need to be valid. Check them on the dashboard.
Recovery permission is granted Your Microsoft 365 app registration needs the Office 365 Exchange Online full_access_as_app application permission so recovery can write mail back into mailboxes. See Connecting Microsoft 365.
No unfinished recovery A completed recovery must be finished (moved to the historic recoveries list) before a new one can start. If a previous recovery is still awaiting review, deal with it first.

There is no strict deadline, but starting promptly once Microsoft 365 is stable shortens the period where mail from the outage exists only in Google Workspace.

Starting the recovery

  1. Open the Recovery page from the sidebar. If you have never run a recovery, the page shows an empty state with a button to start your first one.
  2. Click Start recovery.
  3. The dialog shows what will be recovered: the item types (mail) and the number of users included. Users are included automatically — everyone with an active policy and a completed initial sync.
  4. Choose the recovery start date. All data synced from this day onward will be recovered, so pick the day the outage began (or earlier if you want a wider window).
  5. Confirm. The recovery starts and the page moves to the processing view.

While it runs

  • The processing view shows each user's progress and an items synced count, updated every few minutes
  • Recoveries are not instant — how long one takes depends on how much mail accumulated during the outage
  • You can leave the page and come back; the recovery continues in the background

Next steps

Was this article helpful?
0 out of 0 found this helpful