Configure Copilot settings with the owner role

Give administrators the ability to manage the data and custom plugin use in Security Copilot.

Prerequisites

You need the Security Copilot owner role to manage owner settings.

For more information, see Understand authentication in Microsoft Security Copilot.

Owner settings

Manage the usage and data privacy for Copilot in this menu section.

• Manage capacity - Manage security compute unit association and creation.
• Help improve Copilot - Help improve Copilot by allowing Microsoft to capture data.
• Logging audit data in Microsoft Purview - Manage logging audit data by configuring whether to allow Microsoft Purview to access, process, copy, and store Customer data.
• Manage who can upload files - Specify who can upload files. For more information, see File upload.

Capacity management

Manage capacity association, overage units, and geo location evaluation options. Keep in mind, purchasing new security capacity units (SCUs), changing capacity, or associating with a different capacity all require Azure Owner or Contributor access to the capacity resource in the Azure portal.

Figure shows owner setting for associating SCUs.

For more information on purchasing SCUs, see Provision capacity.

Help improve Copilot

The following data sharing options are available:

Setting	Description
Allow Microsoft to capture data from Security Copilot to validate product performance using human review	Such validations include but aren't limited to: - Ability of Security Copilot to successfully provide responses to user requests and understand capability gaps that need to be addressed based on user prompts. - Understand the types of tasks customers are using Security Copilot for. - Produce metrics surrounding the usability and quality of responses. - Validate Security Copilot capabilities involving other Microsoft products purchased and integrated by a customer. - Improve responses from plugins accessing other Microsoft products. For more information, see Set up location for prompt evaluation and opt-in (or out of) data sharing.
Allow Microsoft to capture and human review data from Security Copilot to build and validate Microsoft's security AI model	Such validations include but aren't limited to: - Captured data is used to develop security specific models built on top of Azure OpenAI foundational model, which would power more intelligent and personalized capabilities for Security Copilot and other Microsoft products that it integrates with. NOTE: Data isn't shared with OpenAI or used to train the Azure OpenAI foundational model.

For more information, see Data sharing and feedback options.

Manage logging audit data in Microsoft Purview

Manage logging audit data by configuring whether to allow Microsoft Purview to access, process, copy, and store Customer data.

Security Copilot uses Microsoft Purview to process and store data such as admin actions, user actions, and system responses.

In most scenarios, logs are available within 24 hours in Microsoft Purview after enabling the capability.

Important

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. The default retention period for audit logs is 180 days, but can be extended using audit log retention policies. For more information, see Manage audit log retention policies.

If you already use Microsoft Purview, no further set up is needed. Otherwise, you'll need to provision a free, limited experience. For more information, see Turn auditing on or off.

For more information, see Audit logging.

Manage who can upload files

As an owner, you can configure who can upload files into Security Copilot to allow Copilot to refer to contents of the file for responses. You can set it so that no one can upload files or contributors and owners can upload files.

Related content

• Manage plugins
• Assign roles

For more information on authentication in Security Copilot, see Understand authentication in Microsoft Security Copilot.