Home › Microsoft Purview › MIP_LABEL_NOT_APPLIED

Microsoft Purview · MIP_LABEL_NOT_APPLIED · Windows 11 23H2

MIP_LABEL_NOT_APPLIED: Label policy not found in Windows 11 23H2

Missing AIP unified labeling client or label policy replication lag causing 'Label policy not found'. Verify Get-LabelPolicy and Set-LabelPolicy.

Error Details

FactValueSourceNote
Exact error stringMIP_LABEL_NOT_APPLIEDOffice application log->
Affected build rangeWindows 11 23H2OS Build Information
Registry keyHKLM\SOFTWARE\Microsoft\InformationProtection\PolicyRegistry Editor->
Relevant service/endpoint URLhttps://compliance.microsoft.com/Purview Compliance Portal
Log line signatureLabel policy not found in Get-LabelPolicy outputSecurity & Compliance PowerShell->

Log Files to Check

What This Error Actually Means

The error code MIP_LABEL_NOT_APPLIED is raised by Microsoft Purview Information Protection (MIP) when an Office application attempts to apply a sensitivity label but fails due to the absence of the corresponding policy on the client machine or in the compliance portal. The component responsible for this issue is primarily the AIP unified labeling client, which interacts with the MIP service and enforces policies defined through Microsoft Purview Compliance Portal. This error typically occurs when there's a mismatch between the sensitivity label policies configured in the Microsoft 365 admin center and those available on the local machine. The AIP unified labeling client checks for these labels before applying them to documents or emails, ensuring that only authorized users can access sensitive information according to organizational compliance requirements.

Affected Versions and Scope

This error is specific to Windows 11 build 23H2 running Microsoft Purview Information Protection. It impacts devices where sensitivity label policies are not correctly replicated from the cloud or where the AIP unified labeling client has failed to install properly. Devices outside this OS range, such as those running older versions of Windows 10 or other operating systems, may experience different error codes and behaviors. The scope of affected configurations includes: - Organizations using Microsoft Purview Information Protection for data classification and protection. - Environments where users are assigned sensitivity labels through AAD groups. - Scenarios involving Office applications like Word, Excel, and Outlook that rely on MIP for enforcing label policies.

Where To Look First: Logs and Event IDs

To diagnose the issue of missing sensitivity labels, start by examining two key log files: C:\Windows\Logs\Office16\OfficeClickToRun.log and C:\Program Files\Microsoft Information Protection\MIPClient\Logs\mipclient.log. These logs contain detailed information about the interaction between Office applications and the MIP service, including any errors encountered during label application attempts. In particular, look for log entries that indicate a failure to find the required sensitivity labels. The exact line you're looking for is: Label policy not found in Get-LabelPolicy output. Additionally, check Event Viewer logs under Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin. Two specific event IDs are particularly relevant here: 4016 and 5023. These events will provide additional context about the state of the AIP unified labeling client on affected devices.

Root Causes

Lag in Policy Replication

One common cause is a delay between when sensitivity labels are configured in Microsoft Purview Compliance Portal and when they become available for use on end-user machines. This can take up to 24 hours due to replication delays across the network. To distinguish this from other issues, check if newly created or updated policies appear correctly in the Security & Compliance PowerShell output but still fail to apply within Office applications.

Missing AIP Unified Labeling Client

Another frequent cause is a failure of the AIP unified labeling client installation on end-user devices. This can occur due to missing prerequisites, network issues preventing download and installation, or conflicts with other software. Identify this issue by confirming that the registry key HKLM\SOFTWARE\Microsoft\InformationProtection\Policy does not contain expected entries related to sensitivity labels.

Incorrect Policy Scoping

Sometimes, policies are correctly replicated but only apply to certain AAD groups. If a user is part of an AAD group that doesn't have the appropriate label policy assigned, they will encounter this error. To determine if this is the case, run Get-LabelPolicy -Identity "[email protected]" and verify that it returns expected results for your organization's policies.

Office Application Configuration Issues

Configuration settings within Office applications themselves can also lead to MIP_LABEL_NOT_APPLIED errors. For instance, if the application is not configured to use Microsoft Purview Information Protection services properly. Check C:\Program Files\Microsoft Office\root\office16\ClickToRun\reg.dat for relevant entries and ensure they match your organization's requirements.

Fix Procedure

  1. Verify Policy Replication: Use the Security & Compliance PowerShell to run Get-LabelPolicy -Identity "[email protected]". Ensure that policies are correctly replicated and available for your AAD group.
  2. Install or Reinstall AIP Unified Labeling Client: If the client is missing, download it from Microsoft's official site or through Intune. Use Intune admin center > Devices > Configuration Profiles to deploy the installer.
  3. Check Registry Settings: Open the registry editor and navigate to HKLM\SOFTWARE\Microsoft\InformationProtection\Policy. Confirm that all necessary keys are present, especially those related to sensitivity labels.
  4. Update Office Application Configuration: Modify the configuration settings in C:\Program Files\Microsoft Office\root\office16\ClickToRun\reg.dat using an OMA-URI such as ./Device/Vendor/MSFT/Office/ClientSettings/LabelingServiceUrl. Ensure it points to the correct service endpoint: https://compliance.microsoft.com/.
  5. Restart Services: Restart the AIP unified labeling client and Office applications after making changes. This can be done via Task Manager or by running commands like net stop mipsvc; net start mipsvc.
Be cautious when modifying registry settings, as incorrect changes can lead to system instability.

Error Code Variants

Error CodeDescription
MIP_LABEL_NOT_FOUNDIndicates that the label itself is not found on the client machine, even if policies are correctly replicated.
MIP_POLICY_NOT_APPLIEDSuggests a failure in applying any policy from Microsoft Purview Information Protection, not just sensitivity labels.
ERROR_LABEL_CLIENT_UNAVAILABLESignals that the AIP unified labeling client is unavailable or malfunctioning on the device.

Verification

After implementing fixes, verify success by checking if the sensitivity labels are now visible in Office applications and accessible via Get-LabelPolicy -Identity "[email protected]". Additionally, review logs for confirmation that no errors related to label application are present.

Prevention

To prevent recurrence of this issue:
A quick diagnostic shortcut is to use the Security & Compliance PowerShell cmdlet Get-LabelPolicy -Identity "[email protected]". This can quickly confirm whether policies are correctly replicated without diving into detailed logs or configurations.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.