Forum Discussion
Stopping Copilot Access to SharePoint Online Sites and Document Libraries
We recently asked Copilot if it was possible to block access to sites using sensitivity labels. The response we got included DLP as part of the solution. It looks like the solutions you presented are at the SPO setting level or the content label level. Does this response provide a third option?
+++++
To configure Copilot to exclude a site based on a sensitivity label, you’ll need to use Microsoft Information Protection (MIP) and set up the appropriate policies. Here’s a step-by-step guide to help you through the process:
1. Create Sensitivity Labels:
- Go to the Microsoft 365 compliance center.
- Navigate to Information protection under Solutions.
- Click on Labels and then Create a label.
- Define the label name, description, and settings (e.g., encryption, content marking).
2. Publish Sensitivity Labels:
- After creating the labels, go to Label policies.
- Click on Publish labels and select the labels you want to publish.
- Choose the users or groups to whom the labels should be available.
3. Configure Policies to Exclude Sites:
- In the compliance center, go to Information protection.
- Under Data loss prevention, create a new policy.
- Define the policy settings, including the conditions and actions.
- In the conditions, specify the sensitivity label that should trigger the exclusion.
- In the actions, configure the policy to block access to specific sites or content.
4. Apply the Policy:
- Ensure the policy is applied to the relevant users or groups.
- Test the policy to confirm that it correctly excludes access to the specified sites based on the sensitivity label.
By following these steps, you can effectively configure Copilot to exclude sites based on sensitivity labels.
Copilot depends on enterprise search. If you exclude sites or document libraries from search results, Copilot can't access that information.
The only sensitivity label setting to block Copilot is for individual documents: https://practical365.com/block-access-to-content-services/ I don't understand the directions that you cite above. They seem like a lot of generated text: garbled
- DaveTheTeamsGuyAug 15, 2024Iron ContributorNo, I do not believe everything Copilot says, however the response got me thinking about the possibility. The response basically says to create a label, then create a DLP policy that blocks access to the site based on applied label.
I was not able to find any reference to using a combination of sensitivity labels and DLP policies to block Copilot from indexing SPO sites in my research, so before digging further I simply wanted to run the response by this thread in case my research wasn't turning up something obvious.