Copilot Generated Document Loses Sensitivity Label: Fix

When you use Copilot in Microsoft 365 apps to draft a document, the final output may arrive without the expected sensitivity label. This label, applied by Microsoft Purview Information Protection, controls access and encryption for confidential content. The root cause is that Copilot generates content in a new temporary file that does not inherit the label from a parent template or from the Copilot session itself. This article explains why the label is lost and provides a reliable fix to reapply it.

Why Copilot Output Loses the Sensitivity Label

Copilot in Microsoft 365 apps generates content in a new, temporary document container. This container does not automatically copy the sensitivity label from the original document or from the Copilot conversation context. Microsoft Purview Information Protection labels are applied to files based on content inspection, template inheritance, or manual user action. Since Copilot creates a file from scratch without a parent template, the label is missing. The issue occurs most often when you use Copilot to generate a new document from a prompt rather than from an existing labeled file.

How Sensitivity Labels Work in Microsoft 365

Sensitivity labels are metadata tags that enforce protection rules such as encryption, watermarks, and access restrictions. Labels are stored in the file header and must be explicitly assigned or inherited. In Word, Excel, and PowerPoint, the label appears on the status bar and the Home tab. If a file is created without a label, it is treated as unclassified and may not be shared securely.

Why Copilot Does Not Apply the Label Automatically

Copilot generates content through the Microsoft Graph and the Large Language Model. The output is streamed into a new document object that has no pre-existing label metadata. The Copilot session itself does not carry a label that can be transferred to the output file. Unless an auto-labeling policy scans the file after creation, the label remains absent.

Steps to Fix a Missing Sensitivity Label on Copilot-Generated Documents

Method 1: Apply the Label Manually After Generation

1. Open the generated document in the desktop app
   Double-click the file to open it in Word, Excel, or PowerPoint. Ensure you are signed in with your work or school account that has the sensitivity label assigned.
2. Locate the Sensitivity button on the Home tab
   On the ribbon, go to Home and find the Sensitivity button in the Protection group. The button shows a shield icon with the current label name or No Label.
3. Select the correct sensitivity label
   Click the Sensitivity button and choose the label that matches the document content. Labels are grouped by classification: Internal, Confidential, Highly Confidential. Pick the appropriate one.
4. Confirm the label appears on the status bar
   After selection, verify that the label name displays on the status bar at the bottom of the window. If encryption is required, the file will prompt you to save with encryption.
5. Save the file
   Press Ctrl+S or click File > Save. The label is now embedded in the file metadata and will travel with the document.

Method 2: Configure Auto-Labeling Rules in Microsoft Purview

1. Sign in to the Microsoft Purview compliance portal
   Go to compliance.microsoft.com and sign in with an account that has the Compliance Administrator role.
2. Navigate to Information Protection > Auto-labeling
   In the left navigation, expand Information Protection and select Auto-labeling. This shows a list of existing auto-labeling policies.
3. Create a new auto-labeling policy
   Click Create auto-labeling policy. Give it a name such as Copilot Generated Documents. Choose the policy type that scans content in SharePoint and OneDrive.
4. Define the conditions for label application
   Under Conditions, select Content contains and specify keywords or sensitive info types that match your Copilot content. For example, add Confidential or Internal as keywords to trigger the label.
5. Choose the label to apply automatically
   Under Label, select the sensitivity label that should be applied when the conditions are met. Click Next and review the policy settings.
6. Test and publish the policy
   Run the policy in simulation mode first to check which files would be labeled. After confirming the results, turn on the policy to apply labels automatically to new files including Copilot-generated documents.

Method 3: Enable Label Inheritance in Copilot Settings

1. Open the Copilot pane in Word or PowerPoint
   Click the Copilot icon on the Home tab or use the Alt+I shortcut to open the Copilot pane.
2. Click the Settings gear icon
   In the Copilot pane, locate the gear icon next to your profile picture. Click it to open the Copilot settings menu.
3. Toggle on Sensitivity label inheritance
   In the settings menu, find the option called Inherit sensitivity label from conversation. Turn the toggle to On. This tells Copilot to copy the label from the source conversation or template to the generated document.
4. Generate a new document to test
   Close and reopen the Copilot pane. Generate a new document from a prompt. After generation, check the status bar to confirm the label is present.

If the Sensitivity Label Is Still Missing After the Fix

Copilot Output Shows No Label Despite Manual Application

If you manually apply a label but the document still shows No Label after saving, the file may be saved in a format that does not support sensitivity labels. Only the Office Open XML formats .docx, .xlsx, and .pptx store label metadata. Save the file in the correct format by using File > Save As and choosing the .docx extension.

Auto-Labeling Policy Does Not Scan Copilot Files

Auto-labeling policies scan files only after they are saved to SharePoint or OneDrive. If you save the Copilot-generated document to a local drive, the policy will not apply. Save the file to a SharePoint document library or OneDrive for Business folder to trigger the auto-labeling scan.

Label Inheritance Toggle Does Not Appear in Copilot Settings

The Inherit sensitivity label from conversation option is available only in Copilot for Microsoft 365 with a license that includes Microsoft Purview Information Protection. If you use Copilot Pro or a free Copilot, this setting is not present. Upgrade to Copilot for Microsoft 365 and ensure the sensitivity label policies are published to your tenant.

Manual Label Application vs Auto-Labeling Policy: Comparison

Item	Manual Label Application	Auto-Labeling Policy
Setup effort	Zero configuration required	Requires Purview compliance portal setup
Speed	Immediate after generation	Delayed until file is saved and scanned
Reliability	Depends on user action	Automatic and consistent
Scope	Single document	All documents in SharePoint or OneDrive
Required license	Any Microsoft 365 plan with sensitivity labels	Microsoft 365 E5 or E5 Compliance add-on

After applying the fix, you can now generate documents with Copilot and retain the correct sensitivity label. The manual method works for immediate needs, while an auto-labeling policy provides a long-term automated solution. For consistent protection, combine the label inheritance toggle in Copilot settings with an auto-labeling policy that scans your document libraries.