Enabling and Disabling a Sync Policy

Sync policies are saved in a disabled state by default. You must explicitly enable a policy to start syncing. This article explains how to enable and disable policies, and what happens in each case.

Enabling a policy

1. Go to Policies in the sidebar
2. Find the policy you want to enable
3. Click the Enable toggle or button
4. Confirm the action when prompted

What happens when you enable a policy

Step	What happens
1. User matching	The backend queries Microsoft 365 using the policy's user selection rules to identify matching users
2. User provisioning	For matched users without a Google Workspace account, accounts are created automatically. Failures are logged in the audit trail.
3. Initial sync queued	Matched users enter the sync pipeline in the "With policy" (waiting) state
4. Initial sync runs	The last 30 days of mail data is migrated from M365 to Google Workspace
5. Delta sync begins	After initial sync completes, incremental syncs run on the configured schedule

Disabling a policy

1. Go to Policies in the sidebar
2. Find the policy you want to disable
3. Click the Disable toggle or button
4. Confirm the action when prompted

What happens when you disable a policy

Area	Impact
Scheduled syncs	All future sync jobs for this policy are stopped. No new delta syncs will run.
In-progress syncs	Any sync job currently running will complete, but no new jobs are scheduled after it finishes.
Synced data	All data previously synced to Google Workspace is retained. Nothing is deleted.
User accounts	Google Workspace accounts created by Continuity remain active. They are not removed or disabled.
Dashboard	The policy's users will no longer appear in the active sync pipeline. Historical data remains viewable in status and logs.

Re-enabling a disabled policy

When you re-enable a previously disabled policy:

• User selection rules are re-evaluated — new users may be added, removed users may be dropped
• Users who already completed initial sync go straight to delta sync
• Users who were mid-initial-sync resume from where they stopped
• A new "policy enabled" audit log event is recorded

Common scenarios

Scenario	Action
Troubleshooting sync errors	Disable the policy, investigate the issue, fix the cause (e.g. connection credentials), then re-enable
Changing sync frequency	You can edit the frequency without disabling — the change takes effect on the next sync cycle
Temporarily pausing all sync	Disable all policies. Re-enable when ready. Data is preserved throughout.
Decommissioning a policy	Disable first, verify no impact, then delete if no longer needed. See Editing and deleting policies.