Getting started: connect your first customer workspace
Reviewed by ContraForce
ContraForce · Help article · Beginner · 5 min read
Pre-onboard a customer in the Workspace Center, send the invite, have their admin grant the core and module consents, then confirm the workspace is live with the onboarding checklist.
Connecting a customer to ContraForce happens in two halves. You create the customer's workspace and choose its modules. The customer's admin then signs in from an invite link and grants Microsoft consent. This walkthrough assumes your own organization is already set up on ContraForce.
Who does what?
- You: pre-onboard the workspace in the Workspace Center, pre-select the customer's detection and response modules, and send the invite.
- The customer admin: click the invite link, accept the two core consents (ContraForce API and ContraForce Portal), then consent each module on the Modules tab.
- You again: run the verification checklist, then assign your team.
What do you need before you start?
- The customer's Microsoft Entra tenant ID.
- The email address of the customer admin who will receive the invite.
- Pop-ups allowed for portal.contraforce.com on both sides. Microsoft consent prompts open in popup windows.
- On the customer side, an active Microsoft 365 license with Defender capabilities (Business Premium, E3 or E5) for Defender-based detection and response.
Which admin roles can grant consent?
The two core consents can be granted by a Global Administrator, Privileged Role Administrator, Application Administrator or Cloud Application Administrator in the customer's Microsoft Entra tenant.
Module consents are stricter. Security modules request application (app-only) Microsoft Graph permissions, which Entra grants only to a Global Administrator or Privileged Role Administrator. An Application Administrator who tries will reach "approval required". The role is needed only for the one-time consent and is not retained, so it can be activated just-in-time with Privileged Identity Management (PIM).
If you pre-select Microsoft Sentinel, the person consenting also needs Azure Subscription Owner. A Defender XDR-only customer does not.
Check roles before the call
If the customer splits these roles across people, such as an Entra admin and a separate Azure subscription owner, line up both before the onboarding call.
How do you pre-onboard the customer?
- 1. Open the Workspace Center from the Workspaces icon in the left navigation.
- 2. Select the Onboarding tab.
- 3. Click Add workspace. The form opens in the right-hand rail.
- 4. Enter the Workspace name, the customer's Tenant ID and the Customer admin email.
- 5. Pre-select the Detection modules the customer is bringing and the Response modules they will use.
- 6. Click Send Invite.
ContraForce emails the invite, and the workspace appears on the Onboarding tab with a Pending customer setup badge and a blue status light. Click the card to see which modules the customer has connected so far.
Choosing modules: Defender for Endpoint and Sentinel both bring Defender for Endpoint incidents, entity enrichment and Gamebook response actions. Only Sentinel adds Sentinel incidents, detection rules, email notifications, log search and Azure Lighthouse. Response modules, such as Gamebooks for Defender XDR or Identity, enable actions like isolating devices and disabling users.
What does the customer admin do?
Send the customer admin these steps, or walk through them together on a call.
- 1. Click the onboarding link in the invite email. It opens portal.contraforce.com.
- 2. Sign in with Microsoft using an account that holds one of the admin roles above.
- 3. On the ContraForce API consent prompt, check Consent on behalf of your organization and click Accept.
- 4. On the second prompt, for ContraForce Portal, check Consent on behalf of your organization again and click Accept.
- 5. Open the workspace from the Workspace Center and go to the Modules tab.
- 6. Click Consent on each pre-selected module, review the permissions and click Accept.
Consent is granted per module, in any order. The core consents are a one-time approval: once they're granted, the rest of the customer's team can sign in normally.
What changes for the Sentinel and Defender modules?
Consenting to the Sentinel module automatically deploys the supporting Azure infrastructure in the customer's subscription, including the Azure Lighthouse delegation, the Apollo resource group and the Sentinel-side automation. There is no separate Azure deployment step. Provisioning runs in the background, so allow extra time after consent before you check Sentinel.
Defender for Endpoint and the Microsoft response modules need only their module consent, from a Global Administrator or Privileged Role Administrator.
How do you know the workspace is live?
There is no completion screen. When the customer finishes, you get a Customer onboarding complete notification in the portal, and the card moves from the Onboarding tab to the Workspaces tab. Then read the status light:
- Blue: pre-onboarded, waiting for the customer.
- Amber: needs attention. A detection module is missing or no Agent Center is deployed.
- Green: onboarded and live.
Next, run the core checks from the verification checklist. Any failure here blocks go-live.
- The workspace shows Active, not Pending customer setup.
- Every pre-selected module shows Connected.
- Incidents appear on the Command Dashboard filtered to the workspace. The checklist allows 5 to 15 minutes for initial sync.
- On the Environments tab, endpoints are onboarded and licenses are in place.
- An incident opens in the Workbench with entity context and timeline.
- Gamebook response actions appear on incident entities.
Look, don't click
Don't test response actions on production entities. Gamebook actions such as Isolate Device or Disable User execute immediately. If you want to test one, use a test account or device.
For a Sentinel customer, also confirm that Sentinel incidents are syncing, the Azure Lighthouse delegation completed, the Content Management System (the flask icon on the Microsoft Sentinel module) loads its analytics rules, and log search works.
What usually goes wrong?
- No consent popup: a pop-up blocker. Allow pop-ups for portal.contraforce.com.
- Sign In Failed page: usually the person isn't a Global Administrator and the tenant hasn't approved ContraForce yet, or an earlier attempt left a stale session. They click Sign out, then Try Again if they are a Global Admin. Anyone else clicks Email Your Admin, then Try Again once that admin has accepted. Retrying without signing out can make it worse.
- Module shows Not Connected: consent was skipped or denied. The customer clicks Consent on that module.
- Card stays blue on the Onboarding tab: the customer hasn't finished consenting their modules. Resend the invite or contact their point of contact.
- Sentinel infrastructure didn't deploy: check that the customer admin has Subscription Owner.
- No incidents after 30 minutes: ContraForce syncs existing incidents, so check the Defender, Sentinel or CrowdStrike console for active ones.
What comes next?
Once the checks pass, assign your team to the workspace with organization-level groups rather than individual users. Tell the customer they are live, and book a check-in within 7 days to review initial incident volume and rule tuning.
For screenshots, the full permission list and every troubleshooting case, read the Onboarding Overview for MSPs and Customers in the ContraForce docs.
Keep learning
- Configuring Security Delivery Agents: On Queue, policies and shifts. Set which severities a Security Delivery Agent picks up On Queue, gate its Gamebooks with a confidence threshold, add investigation policies and shifts, link SOPs and check Run History.
- GDAP, Azure Lighthouse or an enterprise app? Least-privilege access to customer tenants. How GDAP, Azure Lighthouse and admin-consented Entra ID enterprise apps each give an MSSP access to customer tenants, where each stops, and how to keep that access small and time-bound.
- How ContraForce automates detection rule tuning for Microsoft Defender and Sentinel. A short explainer on keeping one set of baseline detection rules across every customer workspace, catching drift, and having a Security Delivery Agent review a noisy rule before a person approves the change.
Sources
- ContraForce Docs, Onboarding Overview for MSPs and Customers, verified 2026-11-20
- ContraForce Docs, MSP and MSSP Platform Onboarding, verified 2026-11-20
- ContraForce Docs, Customer Workspace Onboarding, verified 2026-11-20
- ContraForce Docs, Onboarding Admin Roles and App Permissions, verified 2026-11-20
- ContraForce Docs, Workspace Onboarding Verification Checklist, verified 2026-11-20
- ContraForce Docs, Workspace Center: Manage Customer Workspaces, verified 2026-11-20