Skip to main content
This guide provides a complete overview of the ContraForce onboarding process. Whether you’re onboarding your first customer or your fiftieth, use this as your roadmap to successful deployments.
Estimated Time: A typical onboarding takes 30-60 minutes depending on module selection and environment complexity.

Before You Begin

Prerequisites Checklist

Ensure you have the following before starting:

Microsoft Credentials

Global Administrator or Security Administrator access to the customer’s Microsoft 365 tenant

Licensing

Active Microsoft 365 license (Business Premium, E3, or E5) with Defender capabilities

ContraForce Access

Organization Admin or Admin role in ContraForce to create workspaces

Azure Access

For SIEM module: Subscription Owner access to deploy Azure resources

Information to Gather

Collect this information from your customer before the onboarding call:
InformationRequired ForExample
Microsoft 365 tenant domainAll deploymentsacmecorp.onmicrosoft.com
Global Admin credentialsConsent flow[email protected]
Microsoft 365 license tierCapability planningE5, E3, Business Premium
Azure subscription IDSIEM module onlyxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Sentinel workspace nameSIEM module onlyacme-sentinel-workspace
Notification emailAll deployments[email protected]

Choose Your Module

ContraForce offers two deployment modules. Select based on your customer’s environment and your service offering.

Microsoft Defender XDR Module

Best for: Customers with Microsoft 365 Business Premium, E3, or E5 who want centralized incident management without Sentinel.What’s Included:
  • Incident ingestion from Microsoft Defender XDR
  • Entity enrichment (users, devices, IPs, files, emails)
  • Gamebook response actions
  • Multi-tenant management
What’s NOT Included:
  • Microsoft Sentinel integration
  • Custom detection rules (CMS)
  • SIEM-based incident notifications
  • Log search capabilities
Deployment Time: ~15-20 minutesAzure Resources: None (no Azure deployment required)

Module Comparison

CapabilityXDRXDR + SIEM
Defender XDR incidents
Entity enrichment
Gamebook response actions
Multi-tenant management
Sentinel incidents
Detection rules (CMS)
Email notifications
Log search
Azure Lighthouse

Module Selection Guide

Detailed comparison to help you choose the right module

Onboarding Process

High-Level Steps

Step-by-Step Overview

1

Create Customer Workspace

Create a new workspace in ContraForce for the customer. This establishes their isolated environment.Where: Workspaces → Create Workspace
2

Launch Onboarding Wizard

Open the onboarding wizard from the workspace settings to begin the guided setup.Where: Workspace → Settings → Onboarding Wizard
3

Consent Core Enterprise Applications

Sign in with customer Global Admin credentials to consent the ContraForce API and Portal applications.Applications:
  • ContraForce API
  • ContraForce Portal
4

Select Module

Choose either XDR or XDR + SIEM based on customer requirements and environment.
5

Consent Module Applications

Consent additional enterprise applications required for the selected module.XDR Applications:
  • ContraForce for MDE
  • ContraForce Gamebooks for MDE
  • ContraForce Gamebooks for Identity
  • ContraForce Gamebooks for Email
SIEM Applications (additional):
  • ContraForce Sentinel Hunting
6

Configure Azure Resources (SIEM Only)

For XDR + SIEM module, deploy Azure resources including Lighthouse delegation and Apollo infrastructure.Resources Deployed:
  • Azure Lighthouse delegation
  • Apollo resource group
  • Logic Apps for incident streaming
7

Add Users and Groups

Assign your team members to the workspace with appropriate roles.Recommended:
  • Assign organization groups (SOC Tier 1, Tier 2, etc.)
  • Add customer users if they need portal access
8

Configure Notifications

Set up email notifications for incident alerts (SIEM module only).Options:
  • Configure severity filters
  • Set up distribution group notifications
9

Verify Deployment

Confirm everything is working correctly before going live.Verification:
  • Check incidents are syncing
  • Test Gamebook execution
  • Verify user access

Detailed Guides by Module

XDR Module Onboarding

XDR + SIEM Module Onboarding

Post-Onboarding Configuration


User and Access Setup

Adding Your Team

After onboarding the workspace, assign your team members:
StepActionDetails
1Navigate to workspaceSelect the newly onboarded workspace
2Open settingsClick the gear icon
3Go to Users & GroupsSelect the Users & Groups tab
4Add organization groupsAssign groups like “SOC Tier 1” with appropriate roles
5Verify accessConfirm team members can see the workspace
Team MemberWorkspace RoleCapabilities
SOC ManagerAdminFull control including user management
Tier 2 AnalystIncident ResponderInvestigate and respond to incidents
Tier 1 AnalystIncident AnalystView and triage incidents
Integration EngineerData Source AdminConfigure modules and connectors

User & Group Management Guide

Complete guide to setting up users and groups

Post-Onboarding Checklist

Use this checklist to verify a successful deployment:

Immediate Verification

  • Workspace appears in your workspace list
  • Enterprise applications show “Consented” status
  • Module shows “Active” in workspace settings
  • Your team can access the workspace
  • Incidents are appearing (may take 5-15 minutes)

XDR Module Verification

  • Defender XDR incidents syncing to Command Page
  • Entity enrichment working (click an incident to verify)
  • Gamebook actions available on entities
  • Endpoints visible in Endpoints page (if applicable)

SIEM Module Verification (Additional)

  • Sentinel incidents syncing to Command Page
  • Azure Lighthouse delegation active
  • Apollo Logic App is enabled and running
  • CMS shows available detection rules
  • Notifications being received (test with severity filter)

User Access Verification

  • Organization groups assigned to workspace
  • Team members can view incidents
  • Roles are appropriate for each user
  • Customer users added (if applicable)

Timeline Expectations

Typical Onboarding Timeline

PhaseDurationActivities
Pre-call preparation15-30 minGather credentials, verify prerequisites
XDR onboarding15-20 minConsent apps, configure module
SIEM onboarding30-45 minAbove + Azure deployment, Lighthouse setup
User setup10-15 minAssign groups, configure roles
CMS deployment15-30 minDeploy initial detection rules
Verification10-15 minConfirm incidents flowing, test actions

First Incidents

ModuleExpected Time to First Incident
XDR5-15 minutes (depends on Defender activity)
SIEM5-15 minutes (depends on Sentinel activity)
If no incidents appear within 30 minutes, verify the customer has active incidents in their Defender/Sentinel console. ContraForce syncs existing incidents, so if there are none in the source system, none will appear in ContraForce.

Common Onboarding Issues

Troubleshooting Quick Reference

IssueLikely CauseSolution
Consent popup doesn’t appearPop-up blockerDisable pop-up blocker for ContraForce
Consent fails with permissions errorNot Global AdminUse Global Admin or Security Admin credentials
Azure deployment failsInsufficient permissionsVerify Subscription Owner access
No incidents appearingNo incidents in source systemCheck Defender/Sentinel for active incidents
Module shows “Not Configured”Consent incompleteRe-run consent flow from workspace settings
User can’t see workspaceNo workspace role assignedAdd user/group to workspace with a role
Lighthouse delegation failedSubscription restrictionsCheck for Azure Policy restrictions

Getting Help

If you encounter issues during onboarding:
  1. Check the troubleshooting guide for your specific module
  2. Review Azure deployment logs (SIEM module) in the Azure Portal
  3. Contact ContraForce support at [email protected]
For your first few customer onboardings, consider scheduling a joint call with ContraForce support for real-time assistance.

Onboarding Multiple Customers

Scaling Best Practices

Set up your standard groups (SOC Tier 1, Tier 2, Managers) at the organization level first. Then you can quickly assign them to each new workspace with consistent roles.
Create a template documenting your standard module selection, notification settings, and user assignments. This ensures consistency across all customer deployments.
If you’re onboarding multiple customers with the same module, batch them together. You’ll get faster as you repeat the same steps.
Send customers a pre-onboarding checklist to gather credentials and verify prerequisites before the call. This reduces onboarding time significantly.
For SIEM customers, decide upfront which detection rules to deploy. A standard “starter pack” of rules saves decision time during onboarding.

Onboarding Checklist Template

Use this checklist for each customer onboarding: Pre-Onboarding:
  • Customer domain confirmed
  • Global Admin credentials available
  • License tier verified
  • Azure subscription ID (SIEM only)
  • Sentinel workspace name (SIEM only)
  • Notification email confirmed
Onboarding:
  • Workspace created
  • Core apps consented
  • Module selected and configured
  • Azure resources deployed (SIEM only)
  • Users/groups assigned
Post-Onboarding:
  • Incidents syncing verified
  • Gamebooks tested
  • Notifications configured (SIEM only)
  • CMS rules deployed (SIEM only)
  • Customer notified of go-live

Next Steps After Onboarding



Questions about onboarding? Contact us at [email protected] or request hands-on support for your first deployments.