Microsoft made a quiet but important update to how DLP works with Copilot, and it fixes a gap a lot of us have been working around for a while.
Previously, if you labeled and blocked a file with a sensitivity label + DLP policy, Copilot would still let you bypass it in certain experiences — like opening the file in Word. The common workaround was disabling the connected experience entirely, which meant giving up Copilot access across the board just to close that gap.
That’s no longer necessary. Copilot now respects the label and DLP policy across all experiences, blocking access the way we expected it to work in the first place.
In this video I test it live on a labeled file to show the before/after, and talk through what this means if you’re currently managing DLP for Copilot in your environment.
If you’re doing Purview DLP planning and want to see how this fits into a broader rollout, follow along – hopefully more of this coming.
#MicrosoftPurview #Copilot #DLP #DataLossPrevention #InformationProtection