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?

What do you need before you start?

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?

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.

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:

Next, run the core checks from the verification checklist. Any failure here blocks go-live.

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?

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

All of ContraU

Sources

  1. ContraForce Docs, Onboarding Overview for MSPs and Customers, verified 2026-11-20
  2. ContraForce Docs, MSP and MSSP Platform Onboarding, verified 2026-11-20
  3. ContraForce Docs, Customer Workspace Onboarding, verified 2026-11-20
  4. ContraForce Docs, Onboarding Admin Roles and App Permissions, verified 2026-11-20
  5. ContraForce Docs, Workspace Onboarding Verification Checklist, verified 2026-11-20
  6. ContraForce Docs, Workspace Center: Manage Customer Workspaces, verified 2026-11-20