CloudM Continuity requires two connections to operate: a source connection to Microsoft 365 and a destination connection to Google Workspace. This article explains how to create, edit, test, and manage your connections.
Viewing your connections
Go to Connections in the sidebar. The page displays two connection cards:
- Source Connection — Microsoft 365
- Destination Connection — Google Workspace
Each connection card shows:
| Field | Description |
|---|---|
| Type | Microsoft 365 (source) or Google Workspace (destination) |
| Status | Tested successfully, Error, or Not tested |
| Last tested | The date and time the connection was last tested |
Creating a connection
Microsoft 365 (source)
- Go to Connections in the sidebar
- On the Source Connection card, click Create source
- Enter the following fields:
- Tenant ID — your Microsoft 365 tenant identifier
- Client ID — the Application (client) ID from your Azure AD app registration
- PFX certificate — upload the .pfx certificate file registered with the app
- Certificate password — the password for the PFX file
- Click Save
Google Workspace (destination)
- Go to Connections in the sidebar
- On the Destination Connection card, click Create destination
- Enter the following fields:
-
Domain — your Google Workspace domain (e.g.
yourcompany.com) - Admin email — a Google Workspace super admin email address
- Service account email — the email address of the GCP service account configured for CloudM Continuity
-
Domain — your Google Workspace domain (e.g.
- Click Save
No JSON key files
The Google Workspace connection uses token-based authentication. The CloudM token provider (coop-tp-sa@coop-production-488013.iam.gserviceaccount.com) is granted the Service Account Token Creator role on your service account, allowing it to generate tokens on your behalf. You do not need to download or upload any JSON key files.
Testing a connection
- Go to Connections in the sidebar
- Click the three-dot menu on the connection you want to test
- Select Test connection
- A green toast notification — "Connection test successful" — confirms the connection is working
Always test after creating or editing
After creating a new connection or changing any credential, always use Test connection from the three-dot menu to confirm it works. Sync operations rely on valid credentials — an untested or invalid connection will cause sync failures.
Editing a connection
- Go to Connections in the sidebar
- Click the three-dot menu on the connection you want to edit
- Select Edit
- Update the credentials or settings as needed
- Click Save
- Use Test connection from the three-dot menu to confirm the updated connection works
Editable fields
| Connection type | Editable fields |
|---|---|
| Microsoft 365 | Tenant ID, Client ID, PFX certificate, Certificate password |
| Google Workspace | Domain, Admin email, Service account email |
Removing a connection
- Click the three-dot menu on the connection
- Select Remove
- Confirm the removal
When to update connections
You should update your connection credentials when:
- A certificate expires (Microsoft 365) — PFX certificates have an expiry date. Upload a new certificate before it expires.
- You rotate credentials as part of your security policy
- You need to change the service account (Google Workspace) — update the service account email after configuring the new account
- You see connection errors in the audit log
- You need to change the target tenant (e.g. switching from a test to a production environment)
Connection changes and active policies
Connections are referenced by sync policies. If you update a connection's credentials:
- Existing policies continue to reference the same connection and will use the updated credentials on their next sync cycle
- No policy reconfiguration is needed when you rotate credentials — the policy points to the connection, not to specific credentials
- If you change the underlying tenant (e.g. a different M365 Tenant ID), be aware that the policy will now target a different set of users
Who can manage connections?
Super Admins and Admins can create, edit, test, and remove connections. Viewers have read-only access and cannot make changes. See Roles and permissions for full details.
Audit trail
All connection changes are recorded in the audit log, including:
- Connection created
- Connection credentials updated
- Connection tested (with result)
- Connection removed