Session

Restrict or not to Restrict, That is the question?

So the world has gone Copilot crazy, and what powers this awesomeness, it's all about your Data, and it being gobbled up into the vast semantic index within M365, but what about Data Security, won't someone please think of the Data Security!

The good news is Copilot makes sure you only see the data you can already access, it respects all existing permissions, purview controls and data sensitivity classifications and of course the data is never used to do any model training, so whats the problem?

Well this of course assumes a perfect world where the current user access controls and security groups/permissions granted to the user base are reflective of the data that they should be seeing….. and all of these changes done to provide these permissions will absolutely be managed through a bulletproof Joiners, Movers, Leavers process, won’t it…. No seriously it will won’t it…

But what if its not a perfect world, well in comes Restricted SharePoint Search to save the day, but the question I have is does it really, how does it work and does it severely hobble Copilot to the point of not getting the full capability.

So for me and you, Restrict or not to Restrict, That is the question?

Gary Raife

Modern Workplace Solutions Architect - Power Platform⚡️Microsoft365 🖥 Azure 🚀 Copilot 🤖

London, United Kingdom

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top