You apply a sensitivity label to a SharePoint file to restrict access or prevent Copilot from reading it. But Copilot still summarizes, rewrites, or references the file in its responses. This happens because Copilot reads files based on SharePoint permissions and Microsoft Graph indexing, not solely on the label’s encryption or marking settings. The label … Read more
You ask Copilot a question in Microsoft Teams chat, and the response includes a file that your organization has labeled as Confidential. This exposes sensitive data to users who should not see it. The root cause is a gap between how Microsoft Purview Information Protection sensitivity labels are applied and how Copilot interprets its data … Read more
You open a document protected by a Microsoft Purview Information Protection sensitivity label, such as Confidential or Highly Confidential, and ask Copilot to summarize the content or draft a reply based on it. Instead of returning the expected output, Copilot either refuses to act on the document, returns a generic error message, or skips the … Read more
When you create documents, emails, or presentations using Copilot in Microsoft 365, the output may contain sensitive business information. Without proper protection, that content could be shared outside your organization or accessed by unauthorized users. Sensitivity labels in Microsoft Purview let you apply classification and protection rules automatically to Copilot-generated content. This article explains how … Read more
Official documentation checked October 14, 2026. A missing sensitivity label on a Copilot-generated document should be checked before you share the file. It is not evidence that Copilot always creates an unprotected temporary container, and there is no documented Copilot setting called “Inherit sensitivity label from conversation” to switch on. Microsoft supports label inheritance in … Read more