Getting Started › Overview
System Requirements
Before setting up CloudM Continuity, make sure your Microsoft 365 and Google Workspace environments meet the following requirements. You will also need appropriate admin access to both platforms.
Microsoft 365 (Source)
| Requirement | Detail |
|---|---|
| Subscription | Any Microsoft 365 plan that includes Exchange Online (Business Basic, Business Standard, Business Premium, E3, E5, etc.) |
| Admin access | Global Administrator or Application Administrator role in Azure AD to register the required application |
| Azure AD app registration | An Azure AD application must be registered with the required Microsoft Graph API permissions and certificate-based authentication (PFX certificate). See Connecting Microsoft 365. |
| Graph API permissions | Application-level (not delegated) permissions for reading mail data. The specific permissions required are listed in the connection guide. |
Google Workspace (Destination)
| Requirement | Detail |
|---|---|
| Edition | Google Workspace Business Starter, Business Standard, Business Plus, Enterprise Standard, Enterprise Plus, or Education edition |
| Admin access | Super Admin role in the Google Admin console to configure domain-wide delegation |
| GCP project | A Google Cloud Platform project with a service account. You must grant the CloudM token provider the Service Account Token Creator role on your service account to enable token-based authentication. See Connecting Google Workspace. |
| Service account details | Your Google Workspace domain, admin email address, and service account email are required for the connection. No JSON key file is needed — authentication uses token-based auth via the CloudM token provider. |
| APIs enabled | Gmail API and Admin SDK API must be enabled in the GCP project |
| Domain-wide delegation | The GCP service account must have domain-wide delegation enabled and the correct OAuth scopes authorised in the Google Admin console |
CloudM Continuity platform
| Requirement | Detail |
|---|---|
| Licence | An active CloudM Continuity licence key (format: BCSYNC-XXXXX-XXXXX-XXXXX). Contact CloudM if you don't have one. |
| Browser | Latest versions of Chrome, Edge, Firefox, or Safari |
| Authentication | A Google or Microsoft 365 account for signing in to the CloudM Continuity dashboard (authenticated via Firebase) |
Network and access
| Requirement | Detail |
|---|---|
| Outbound access | No firewall or proxy rules should block outbound HTTPS traffic to Microsoft Graph API endpoints (graph.microsoft.com) or Google Workspace APIs (googleapis.com) |
| No on-premises infrastructure | CloudM Continuity is fully SaaS-hosted. No agents, connectors, or on-premises software is required. |
Nothing to install
CloudM Continuity runs entirely in the cloud. There is no software to download or infrastructure to provision. Setup is done through the CloudM Continuity web dashboard and the admin consoles for Microsoft 365 and Google Workspace.
Pre-setup checklist
Before you begin, confirm that you have:
- An active CloudM Continuity licence key (format:
BCSYNC-XXXXX-XXXXX-XXXXX) - Global Administrator or Application Administrator access to your Microsoft 365 / Azure AD tenant
- Super Admin access to your Google Workspace Admin console
- Access to create a GCP project and service account (or an existing one you can use)
- A Google or Microsoft 365 account to sign in to the CloudM Continuity dashboard
Permissions are customer-managed
You create and control all application registrations and service accounts. CloudM Continuity never stores your admin credentials — it uses the OAuth tokens generated by the applications you configure.