This guide walks you through creating your first sync policy in CloudM Continuity. A policy defines which users to sync, which item types to include, and how often to sync them.
Prerequisites
- You have a valid Microsoft 365 connection (source) — see Connecting Microsoft 365
- You have a valid Google Workspace connection (destination) — see Connecting Google Workspace
- Both connections pass the connection test — see Validating connections
- You have Admin or Super Admin access to your tenant
Creating a policy
- Click Policies in the sidebar
- Click Create policy
The Create a policy page is divided into sections that match the order below. An Activate policy toggle and Learn more link are shown in the top right.
Policy name and description
| Field | Description |
|---|---|
| Policy name | A descriptive name for this policy (e.g. "All users - Daily sync") |
| Policy description | Optional notes about the policy's purpose |
Policy details
| Field | Description |
|---|---|
| Item types | Select which data types to include. Mail (mailbox data and attachments) is available at launch. Additional item types will appear here as they are released. Only item types included in your licence can be selected. |
| Username suffix | Optional. A suffix appended to usernames when Google Workspace accounts are created for matched users. Leave blank if you want usernames to match the source exactly. |
| User query | Define which Microsoft 365 users this policy applies to. Click Add user query to build rules based on group membership, department, or other attributes. Use Check query to preview how many users match. See Defining user selection rules for detailed guidance. |
| Domain | Select the Google Workspace destination domain for this policy. This is the domain where user accounts will be created and mail data will be synced to. |
Sync settings
| Field | Description |
|---|---|
| Sync frequency | Set how often delta syncs run for each item type. Enter a value and select a unit (Hours, Days, or Weeks). For example: 1 Hour, 6 Hours, 2 Days. The minimum interval you can set is determined by your licence tier — the UI will prevent you from entering a frequency faster than your tier allows. See Sync frequency tiers. |
| Deletion delay | Set how long (in days) CloudM Continuity waits before deleting a user's Google Workspace account after they are removed from Microsoft 365. This gives you a buffer to handle accidental deletions or phased offboarding. |
Creating the policy
At the top right of the page, the Activate policy toggle controls whether the policy is activated immediately on creation. By default it is off, meaning the policy is saved in a disabled state so you can review it before activating.
When you're ready, click Create policy at the bottom of the page. If the Activate policy toggle is on, sync operations will begin straight away.
Only one active policy at a time
Only one policy can be active at a time. If you already have an active policy, you will need to deactivate it before activating a new one.
After creating a policy
Once your policy is saved:
- Review the configuration — Check the policy details on the Policies page to confirm everything is correct
- Enable the policy — If you saved it as disabled, enable it when you're ready to start syncing. See Enabling and disabling a sync policy.
- Monitor progress — Use the Dashboard to watch users move through the sync pipeline, and the Sync Status page for per-user detail
Start small
For your first policy, consider targeting a small group of test users with the user query. Once you've confirmed sync is working correctly, you can update the user query to cover more users.
Policy creation is logged
Creating a policy generates an audit log event. If the policy is created and immediately activated, two events are logged: "policy created" and "policy enabled".