Planning of Microsoft 365 Copilot Rollout Strategy

In this webinar, you'll learn how to:
- Get your organization ready for Microsoft Copilot: get your information ready for search
- Implement the right information access controls and policies established in your organization so that your users will have access to the information that they need and nothing else
- Enable automatic data classification controls across your M365 workloads (Teams, SharePoint, OneDrive) to manage information access across your organization
- Key considerations, best practices, and actionable insights to ensure a smooth and effective Microsoft 365 Copilot implementation
Download Copilot for Microsoft 365 ebook here netwoven.com/services/cloud-i...

[@georgewashington3012]

Are sensitivity labels truly required for Copilot for M365? Labels have their own issues (compatibility, performance, end user training, etc.). I’m hoping I can simply get by with double checking permissions everywhere prior to rollout as label deployment would be a cultural shift and an even bigger headache than deploying Copilot.
Besides, what would be the benefit in deploying labels as it relates to Copilot? We’d want people to feel free to use ALL sensitivities of data with Copilot for M365. After all, one reason it’s so expensive is the robust privacy and security controls built into Copilot for M365. Restricting the types of data users can use with Copilot would only serve to frustrate users and create angry calls to the Service Desk.
Same thing for DLP. I realize DLP is useful in its own right, but what relevance does it have for Copilot? It isn’t as though users will exfiltrate data to external storage services/devices/recipients to a higher degree simply because they have Copilot for M365. Employees are expected to exercise good judgement when sending data and Copilot for M365 doesn’t change that.

[@netwoven]

Sensitivity labels are not required to use Copilot for M365. We are recommending, however, that you take steps to secure sensitive or confidential information from being accessed and incorporated into CoPilot results. Sensitivity labels are one way to do this, but there are other approaches you can take as well. Double-checking access permissions is a good idea. We would also suggest monitoring access logs for selected content, to confirm that CoPilot is not inadvertently accessing content it should not see.