Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | MIP_LABEL_NOT_APPLIED | Office Info Bar / Purview Activity Explorer | Indicates failure to apply, inherit, or enforce label |
| Affected Build Range | Microsoft 365 Apps (Current/Semi-Annual) | Office Client Version Check | Older versions may lack schema support |
| Registry Key / OMA-URI | HKCU\Software\Policies\Microsoft\Office\16.0\Common\Security\Adm\Labeling | Local Registry / Group Policy | Controls labeling behavior and policy enforcement |
| Relevant Service Endpoint | RightsManagementUrl (from Get-AIPServiceConfiguration) | PowerShell AIP Module | Must be active for Azure RMS protection labels |
| Log Line Signature | LabelingFailed event in Activity Explorer | %localappdata%\Microsoft\MSIP\Logs\msip_uls_<user>.log | Detailed ULS logs show specific failure reason |
Log Files to Check
%localappdata%\Microsoft\MSIP\Logs\msip_uls_<user>.log%programdata%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
What This Error Actually Means
The error code MIP_LABEL_NOT_APPLIED is a critical indicator within the Microsoft Information Protection (MIP) engine that signifies a failure in the enforcement or application of a sensitivity label. Unlike transient network timeouts, this specific error denotes a logical mismatch between the policy definition in the cloud and the client-side execution context. It is raised by the Unified Labeling Client (ULC), which is embedded within Microsoft 365 Apps for enterprise, as well as standalone AIP clients. When the ULC attempts to apply a label—whether triggered by user action, auto-labeling rules, or mandatory policy enforcement—it validates the label schema against the local cache and the Azure Rights Management (Azure RMS) service status. If this validation fails due to scope exclusion, schema incompatibility, or service unavailability, the engine aborts the operation and returns MIP_LABEL_NOT_APPLIED. This is not merely a UI glitch; it represents a breakdown in the compliance chain where the document remains unprotected despite administrative intent.
Affected Versions and Scope
This error primarily impacts tenants utilizing Microsoft 365 Apps (Current Channel or Semi-Annual Enterprise Channel) where the Unified Labeling feature is enabled. It is most prevalent in environments transitioning from legacy Azure Information Protection (AIP) scanners to native Office client integration. The issue is strictly scoped to clients running builds that support the current label schema version but are misconfigured regarding policy replication. Specifically, if an organization enforces mandatory labeling for specific file types (e.g., .docx, .xlsx) and the client has not successfully downloaded the latest policy blob from the Azure AD Graph or Microsoft Graph endpoint, this error manifests. It does not affect on-premises SharePoint servers directly unless they are configured with the AIP scanner service, nor does it impact users who are explicitly excluded from label policies via group membership. The scope is limited to Windows 10/11 endpoints and macOS clients where the MIP SDK is active.
Where To Look First: Logs and Event IDs
To diagnose MIP_LABEL_NOT_APPLIED, you must correlate client-side logs with server-side activity records. The primary source of truth on the endpoint is the Unified Labeling Client log located at %localappdata%\Microsoft\MSIP\Logs\msip_uls_. You should grep this file for the literal string LabelingFailed or MIP_LABEL_NOT_APPLIED to identify the exact timestamp of the failure. Additionally, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Office > Telemetry for Event ID 1000, which often logs generic application errors related to add-ins, and Event ID 4001 in the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log if the issue stems from Intune policy delivery failures. In the cloud, navigate to the Microsoft Purview compliance portal > Information Protection > Activity explorer and filter for LabelingFailed events. This will provide the correlation ID needed to trace the request back to the specific tenant policy violation.
Root Causes
Policy Scope Misalignment
The most common cause is that the user is not included in the scope of the label policy. Even if the label exists, the policy assigning it must explicitly include the user or a group they belong to. If the policy is assigned to "All Users" but the user is excluded via a nested group exclusion, the client receives no valid label definitions, resulting in MIP_LABEL_NOT_APPLIED when mandatory labeling is attempted.
Azure RMS Service Activation Failure
If the sensitivity label requires encryption (Azure Rights Management), the tenant must have Azure RMS activated. If the service endpoint is unreachable or not configured, the client cannot apply the protection component of the label. This is distinct from simple classification labels which do not require encryption.
Client Cache Corruption
The local MIP cache may become corrupted, preventing the client from validating the label schema. This often occurs after a major Office update or a change in the Azure AD tenant configuration. The client attempts to apply a label using an outdated or invalid schema version cached locally.
Fix Procedure
- Verify Policy Scope: Navigate to
Microsoft Purview compliance portal > Information Protection > Label policies. Select the relevant policy and check the "Scope" tab. Ensure the user is included in the assigned groups or users list. If using dynamic groups, verify the membership rules. - Check Azure RMS Status: Run the following PowerShell cmdlet to ensure the Rights Management service is active and reachable:
Get-AIPServiceConfiguration | Select-Object RightsManagementUrl. If this returns null or an error, activate Azure RMS in the Microsoft 365 admin center. - Force Policy Refresh: On the affected client, open PowerShell as Administrator and run:
Get-AIPFileStatus -Path "C:\Temp\test.docx" -JustificationMessage "Policy Refresh Test". This forces the client to re-evaluate the file against current policies. If this fails, proceed to cache clearing. - Clear MIP Cache: Delete the contents of
%localappdata%\Microsoft\MSIPand restart Office applications. This forces a fresh download of policy definitions from the cloud. - Verify Intune Policy Delivery: If using Intune for configuration, check the delivery status via:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'". Ensure the device is reporting healthy compliance status. For specific policy troubleshooting, use:Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices"to verify the device object exists and is synced. - Registry Verification: Ensure that Group Policy or Intune has not disabled labeling. Check
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\Security\Adm\Labeling. If the valueDisableLabelingis set to 1, change it to 0 or delete the key.
%localappdata%\Microsoft\MSIP) will temporarily remove all locally cached labels and may cause a brief period where existing protected documents cannot be opened until the new cache is rebuilt. Ensure users are aware of this potential disruption before proceeding.
Error Code Variants
| Error Code | Description | Distinguishing Feature |
|---|---|---|
MIP_LABEL_NOT_APPLIED |
Label application failed due to policy/scope/service issues. | Occurs when policy is present but enforcement fails logically. |
MIP_LABEL_NOT_FOUND |
The specific label ID requested does not exist in the tenant. | Indicates a deleted or renamed label, not a scope issue. |
MIP_NETWORK_ERROR |
Client could not reach Azure services. | Transient network issue; retry usually succeeds. |
MIP_SCHEMA_MISMATCH |
Local schema version differs from cloud schema. | Requires client update or cache clear, similar to NOT_APPLIED but specific to versioning. |
Verification
To verify the fix, create a test document and attempt to apply the previously failing label. Monitor the log file at %localappdata%\Microsoft\MSIP\Logs\msip_uls_ for the absence of LabelingFailed entries. Instead, you should see successful application events with status code 200 or similar success indicators. Additionally, check the Microsoft Purview compliance portal > Activity explorer to confirm that the LabelApplied event is recorded for the test file. You can also use PowerShell to verify the file status: Get-AIPFileStatus -Path "C:\Temp\test.docx". The output should show the label name and protection status correctly.
dsregcmd /status to quickly verify device registration and Azure AD join status. While not directly related to labeling, a broken AAD join can sometimes interfere with policy retrieval if conditional access or hybrid identity issues are present.
Prevention
To prevent recurrence, implement automated monitoring for label application failures. Configure alerts in Microsoft Purview for LabelingFailed events exceeding a threshold. Ensure that all Office clients are updated to the latest Semi-Annual or Current Channel builds to support the latest label schemas. Use Intune to enforce consistent configuration via OMA-URI settings, specifically ensuring that labeling is not disabled by local policies. For example, deploy the following OMA-URI to ensure labeling is enabled: ./Device/Vendor/MSFT/Policy/ConfigOperations/OfficeLabeling/EnableLabeling. Regularly audit label policy scopes to ensure group memberships are accurate and up-to-date. Finally, maintain a healthy Azure RMS service configuration by monitoring the RightsManagementUrl endpoint availability via scheduled PowerShell scripts.