- Internal security teams deploying ContraForce for your own organization
- MSP/MSSP partners setting up your parent tenant before onboarding customers
What You’ll Accomplish
By the end of this guide, you’ll have:Connected Microsoft Environment
Active Workspace
Team Access
Response Capabilities
Prerequisites
Required Access
| Requirement | Details |
|---|---|
| Microsoft 365 License | Business Premium, E3, or E5 with Defender capabilities |
| Global Administrator | Or Security Administrator role in Microsoft Entra ID |
| Azure Subscription Owner | Required only for XDR + SIEM module |
| ContraForce Account | Provided by ContraForce during contract setup |
For XDR + SIEM Module (Optional)
| Requirement | Details |
|---|---|
| Microsoft Sentinel | Active Sentinel workspace in your Azure subscription |
| Subscription Owner | To deploy Azure Lighthouse and Apollo resources |
| Resource Group Access | Ability to create resource groups in the subscription |
Step 1: Sign In to ContraForce
Navigate to ContraForce's Onboarding Workflow
Sign In with Microsoft
Complete MFA
Accept Initial Permissions
Step 2: Create Your Organization Workspace
Your organization workspace is where your own security data lives—separate from any customer workspaces you may create later.Navigate to Workspaces
Create New Workspace
Enter Workspace Details
- Name: Your organization name (e.g., “Acme Security Operations”)
- Description: Optional description
- Type: Select “Internal” for your own organization
Save Workspace
Step 3: Launch Onboarding Wizard
Open Workspace Settings
Go to Modules
Start Onboarding
Step 4: Consent Core Enterprise Applications
The first consent step authorizes ContraForce to access your Microsoft environment.Click Consent for ContraForce API
Sign In as Global Admin
Review Permissions
- Read security events
- Read user profiles
- Read directory data
Accept on Behalf of Organization
Repeat for ContraForce Portal
Core Applications
| Application | Purpose |
|---|---|
| ContraForce API | Platform backend access to your security data |
| ContraForce Portal | User authentication and portal access |
Step 5: Select Your Module
Choose the module that matches your environment:- XDR Module
- XDR + SIEM Module
Choose XDR If:
- You have Microsoft 365 with Defender but no Sentinel
- You want the fastest deployment (~15 minutes)
- You don’t need custom detection rules or log search
What You Get:
- Defender XDR incident ingestion
- Entity enrichment (users, devices, IPs, files, emails)
- Gamebook response actions
- Endpoint visibility
Click “XDR” to continue
Step 6: Consent Module Applications
Based on your module selection, consent the required enterprise applications.Microsoft Defender Applications
| Application | Purpose | Required For |
|---|---|---|
| ContraForce for MDE | Read endpoint and incident data | All deployments |
| ContraForce Gamebooks for MDE | Execute endpoint response actions | Gamebook actions |
| ContraForce Gamebooks for Identity | Disable users, reset passwords | Identity response |
| ContraForce Gamebooks for Email | Quarantine/release emails | Email response |
Microsoft Sentinel Applications (SIEM Module Only)
| Application | Purpose |
|---|---|
| ContraForce Sentinel Hunting | Query Log Analytics for threat hunting |
Consent Each Application
Authenticate as Admin
Accept Permissions
Verify Green Checkmarks
Step 7: Deploy Azure Resources (Microsoft Sentinel Module Only)
Select Azure Subscription
Select Sentinel Workspace
Deploy Apollo Infrastructure
Wait for Deployment
What Gets Deployed
| Resource | Purpose |
|---|---|
| Azure Lighthouse | Cross-tenant management delegation |
| Apollo Resource Group | Incident notification infrastructure |
| Logic App | Streams incidents to ContraForce |
| Role Assignments | Grants ContraForce access to Sentinel |
Azure Resources Reference
Step 8: Authorize Gamebook Service Principals
Gamebooks require additional authorization to execute response actions in your environment.Navigate to Gamebook Authorization
Click Authorize
Consent as Admin
Gamebook Capabilities by Authorization
| Service Principal | Enables |
|---|---|
| MDE Gamebooks | Isolate device, run AV scan, collect investigation package |
| Identity Gamebooks | Disable user, reset password, revoke sessions |
| Email Gamebooks | Soft delete email, release from quarantine |
Step 9: Add Your Team
Now add your team members so they can access the platform.For Internal Security Teams
Go to Settings → User Management
Add Users
Assign Organization Role
- Organization Admin for platform administrators
- Organization Member for analysts and engineers
Assign to Workspace
For Partners (Setting Up Parent Tenant)
Create Organization Groups
- SOC Tier 1
- SOC Tier 2
- SOC Managers
Add Team to Groups
Assign Groups to Workspace
Recommended Roles
| Team Member | Workspace Role |
|---|---|
| Security Director / Manager | Admin |
| Senior Analyst | Incident Responder |
| Analyst | Incident Analyst |
| Security Engineer | Data Source Admin |
Roles & Permissions Reference
Step 10: Verify Your Deployment
Confirm everything is working correctly.Verification Checklist
- Workspace shows “Active” status
- All enterprise applications show green checkmarks
- Module shows “Configured” status
- Team members can sign in and see the workspace
- Incidents are appearing on the Command Page (may take 5-15 minutes)
Test Gamebook Actions
Open an Incident
Select an Entity
View Available Actions
Configure Notifications (SIEM Module)
If you deployed the SIEM module, configure email notifications:Go to Workspace Settings
Configure Severity Filters
Save Settings
Distribution Group Setup
To send notifications to a team inbox:- Contact [email protected]
- Provide the distribution group email address
- ContraForce Engineering will configure the routing
Notifications Configuration
Next Steps
- Internal Teams
- Partners
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| Consent popup blocked | Browser popup blocker | Allow popups for portal.contraforce.com |
| Consent fails | Not Global Admin | Use Global Admin credentials |
| Azure deployment fails | Insufficient permissions | Verify Subscription Owner access |
| No incidents appearing | No active incidents in source | Check Defender/Sentinel for existing incidents |
| Team member can’t see workspace | No workspace role | Assign user to workspace with a role |
| Gamebook actions unavailable | Service principal not authorized | Complete Gamebook authorization step |