Manual Onboarding and Workspace Setup

Atlanta, USA

Cloud2BR OSS - Learning Hub

Last updated: 2026-08-04

---

References

• Manual onboarding for non-Microsoft 365 E5 (Enterprise 5) and E7 (Enterprise 7) customers
• Security compute units and capacity

Objective

Provision Security Copilot for organizations that are not in the included Microsoft 365 E5 (Enterprise 5) and E7 (Enterprise 7) onboarding model.

Prerequisites

• Azure subscription for SCU (Security Compute Unit) capacity.
• Required tenant and subscription roles for provisioning.
• Defined owner and contributor assignment model.

Recommended setup path

1. Sign in to Security Copilot and select Get started.
2. Create workspace using naming and governance conventions.
3. Provision SCU (Security Compute Unit) capacity and overage settings.
4. Configure data sharing and logging settings.
5. Confirm role assignments and complete onboarding.

Alternative setup path

You can provision capacity in Azure first, then finish setup in the Security Copilot portal.

Validation checklist

• Workspace was created and is accessible.
• Capacity reflects expected baseline and overage values.
• Owners and contributors are assigned correctly.
• Initial prompt and agent operations succeed.