So you want to roll out Copilot, or maybe you’ve already started in your organization. Copilot will consume anything users have access to, regardless of whether it’s been overshared with them or it’s sensitivity. We saw this happen with Delve, where organizations panicked when they thought Delve was sharing things people shouldn’t have access to. It wasn’t, the underlying governance wasn’t in place and Delve was making it more obvious. The same happens with Copilot, not to mention Microsoft Search.
Sure you can turn on search index exclusions to exclude most of your tenant while you clean it up, and that can be a valid phase one. Make sure you exclude any sensitive content if you haven’t put an information protection plan like Microsoft Purview in place. But if you really want benefit from Copilot, not to mention a safe and secure Microsoft Search, you need to do more.
In this session we’ll go over a planning and roadmap process that covers the following:
-
Consolidating your data into Microsoft 365
-
Inventorying what is already in Microsoft 365
-
Clean out redundant and stale content, and consider Purview retention policies
-
Look for oversharing and clean up security
-
Apply Purview sensitivity labels
-
Change management and training
-
Governance