Del via

Onboarding to Security Copilot for non-Microsoft 365 E5 customers

Note

The following steps are only applicable for customers who are NOT Microsoft 365 E5 customers.
If you're a Microsoft 365 E5 included customer and have been notified that you're eligible to use Security Copilot these steps don't apply to you.
Microsoft will automatically provision and onboard you, so that you can immediately get started with Security Copilot. For more information, see Understand how Security Copilot is auto provisioned for Microsoft 365 E5 customers.

If Security Copilot isn't included in your license, you need to provision SCUs.

You can choose from the following options to provision capacity:

Note

Regardless of the method you choose, you'll need to purchase a minimum of 1 provisioned SCU. You can purchase up to a maximum of 100 SCUs. The recommended number of units to conduct an introductory exploration of Security Copilot is 3 units with overage set to unlimited overage. You can use the usage monitoring dashboard to keep track of usage and adjust capacity based on workload. For more information, see Manage usage.

Minimum requirements

Note

Whoever sets up the default environment (including any other owner roles that that person holds) will be designated as the default owner. For example, if the person setting up Security Copilot has an Microsoft Entra Compliance Administrator role and Purview Organization Management role, then both of those roles are added as owners by default.

When you first open Security Copilot (https://securitycopilot.microsoft.com), you're guided through the steps in setting up capacity for your organization.

  1. Sign in to Security Copilot (https://securitycopilot.microsoft.com).

  2. Select Get started.

    Screenshot of get started.

  3. Set up a workspace. A workspace is a scoped, tenant-bound environment where users, automations, and agents operate. Enter a workspace name following the workspace naming convention, then select Continue. For more information, see Naming rules and restrictions for Azure resources.

    Screenshot of Workspace info.

  4. Set up your security capacity:
    Select the Azure subscription, associate capacity to a resource group, add a name to the capacity, select the prompt evaluation location, and specify the number of Security Compute Units (SCUs). You can also specify the number of overage units. These units offer the flexibility to have additional security compute units available when the initially provisioned SCUs are depleted during usage spikes.

    Screenshot of set-up your security capacity.

    Note

    The number of SCUs is provisioned on an hourly basis, and the estimated monthly cost is displayed.

    If your selected geo location is too busy, you can also evaluate the prompts anywhere in the world. This can be done by selecting the appropriate option in the capacity creation screen.

  5. Select among the data sharing options. Select Continue. For more information on data sharing, see Privacy and data security.

  6. Confirm that you acknowledge and agree to the terms and conditions, then select Continue.

    After you've created the capacity, it will take a few minutes to deploy the Azure resource on the backend.

    Screenshot of setting up your security capacity.

  7. Select if you want Security Copilot to capture and store administrator actions, user actions, and system responses. Select Continue. For more information, see Accessing data from Microsoft 365 services.

    Note

    Microsoft Purview will store your Customer Data in the region where your Microsoft 365 data is stored. For more information, see Privacy and data security.

  8. Review the roles that can access Security Copilot. You can choose to select other recommended owner roles or add contributors. Select Continue.

    Screenshot of Copilot access roles.

  9. A confirmation page is displayed. Select Finish.

    Screenshot of Copilot all set.

Option 2: Provision capacity in Azure

The initial setup in this method starts in the Azure portal. Then, you need to complete the setup in the Security Copilot portal.

Note

Billing begins as soon as capacity is created, regardless of whether the SCU is attached to an environment.

  1. Sign in to the Azure portal.

  2. Search for Security compute in the list of services, then select Microsoft Security compute capacities.

  3. Select Resource groups.

  4. Under Plan, select Microsoft Security Copilot. Then select Create.

  5. Select a subscription and resource group, add a name to the capacity, select the prompt evaluation location and select the number of Security Compute Units (SCUs). You can also specify the number of overage units. These units offer the flexibility to have additional security compute units available when the initially provisioned SCUs are depleted during usage spikes. Data is always stored in your home tenant geo.

    Note

    The number of SCUs is provisioned on an hourly basis, and the estimated monthly cost is displayed.

    If your selected geo location is too busy, you can also evaluate the prompts anywhere in the world. This can be done by selecting the appropriate option in the capacity creation screen.

  6. Confirm that you acknowledge and have read the terms and conditions, then select Review + create.

  7. Verify that all the information is correct, then select Create. A confirmation page is displayed.

  8. Select Finish setup in the Security Copilot portal.

See also

  • Last updated on