Forum Discussion
Solved
Hiding SharePoint Files and Pages from Copilot
How do we stop legacy items from returning as search results in Copilot? I only know how to exclude specific sites, but we'd like to exclude just particular pages without unpublishing them or revoki...
Hello RichardBegg,
I had the same error and searching in Microsoft documentation I found this and based on it, I sent the request in the following way:
{ "template@odata.bind":"https://graph.microsoft.com/v1.0/teamsTemplates('standard')", "displayName":"My Sample Team", "description":"My Sample Team’s Description", "members":[ { "@odata.type":"#microsoft.graph.aadUserConversationMember", "roles":[ "owner" ], "user@odata.bind":"https://graph.microsoft.com/v1.0/users('0040b377-61d8-43db-94f5-81374122dc7e')" } ] }The request was success.
This is a great question that I've talked to multiple people at Microsoft about. The way to ensure that legacy content is not used for Copilot is to ensure that legacy files are not accessible to search or deleted if they are not required for retention. If you can find a file with search, Copilot can consume it - for you, since you have access (so it's based on permissiosn). So, the bottom line is that you need to exclude content from search to ensure that Copilot does not consume the content. This is easier with files because you can ensure that they are in a library where search is disabled. It's harder with pages - so you need to make sure you shore up your governance plan! If the content isn't accurate, update it! If the content isn't needed, delete it! You can't currently use the term store to do this. You can, however, exclude entire sites from search. That will ensure that Copilot can't use the content. At the end of the day, it comes down to governance.
