An organization wants to apply mandatory sensitivity labels to all content generated by Microsoft 365 Copilot. The policy should inherit the highest sensitivity label of any documents referenced during a Copilot session. Which Purview feature enables label inheritance for Copilot-generated content?
Select an answer to reveal the explanation.
Short Explanation
Here's the deal — you need sensitivity label inheritance from referenced content in Copilot label policies. It pulls the highest label from the documents Copilot references into the generated output, so a response based on a Highly Confidential document inherits that label automatically.
Full Explanation
Sensitivity label inheritance from referenced content in Copilot label policies is correct because Microsoft Purview sensitivity label policies for Copilot include an option to inherit the highest sensitivity label from the documents that Copilot references when generating a response. This ensures that if a Copilot output is based on a 'Highly Confidential' document, the output inherits that label automatically. Auto-labeling policies in Purview Information Protection are wrong because they scan existing content, such as files and emails, for sensitive information and apply labels, rather than applying labels to Copilot outputs specifically through inheritance. A DLP policy with label-based conditions is wrong because DLP policies enforce data protection actions based on label conditions, but they do not assign or inherit labels themselves. Manual labeling enforcement through default label policies is wrong because default label policies assign a baseline label, but they do not dynamically inherit the highest label from referenced documents.