Event details
What is the best practice to systematically and retrospectively apply sensitivity labels on vast volumes of SharePoint content that already exists in our repository so that Copilot cannot access it?
Reach out to eg Data architect , aware existing Data Obsification software "already purchased " , and "appropiate fit for your use case " .
My logic follows irrespective of copilot , sensitive info as categorized by "company " , would need to be protected not from a or 1 tool but All current and any future implementions of software tools,AI,People,... implemented explicitally.