Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Application assignment not applicable — scope tag or group exclusion prevents deployment to device | Microsoft Intune admin center logs | -> Indicates the specific reason for deployment failure. |
| Affected OS build range | Windows 11 23H2 and above | Microsoft documentation on Intune compatibility | -> Confirms the OS version where the issue occurs. |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\Client\DeviceId | Windows Registry Editor | -> Contains device-specific information used by Intune. |
| Relevant service/endpoint URL | https://manage.microsoft.com | Microsoft Intune admin center access point | -> Platform where the issue is managed and resolved. |
| Log line signature | 0x87D00325 - Application assignment not applicable — scope tag or group exclusion prevents deployment to device | Device Health Service log (DHCS) | -> Specific error code and message in logs. |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-IntuneClient%4Operational.evtxC:\ProgramData\Microsoft\IntuneManagementExtension\LogFiles\DeviceHealthService.log
What This Error Actually Means
The error code0x87D00325 is a hexadecimal representation of the decimal value 2281729989, which is specific to Microsoft Intune's Device Health Service (DHCS). This error indicates that an application assignment to a device has been blocked due to scope tag or group exclusion logic in the Intune tenant configuration. The error is raised by the DeviceHealthService component, which evaluates device eligibility for policies and applications based on dynamic groups, scope tags, and enrollment profiles. The key phrase "not applicable" confirms that the device does not meet the criteria defined in the assignment scope, such as membership in an incorrect Azure AD group or lack of a required scope tag. This error is distinct from compliance or policy enforcement failures, as it directly relates to assignment scope validation during the device's sync cycle with Intune.
Affected Versions and Scope
This error is observed in devices runningWindows 11 23H2 and subsequent builds, including 23H2 N and 24H2 (22621.2000+). It is not reported in earlier OS versions like Windows 10 21H2 or Windows 11 21H2 due to differences in how scope tags are processed in the Intune client. Tenants using dynamic group-based assignments or scope tags for application targeting are at risk. Conversely, tenants relying solely on direct device assignments or static groups are unaffected. Additionally, devices enrolled via hybrid Azure AD join without Intune enrollment are less likely to encounter this error, as they bypass the DHCS scope validation logic.
Where To Look First: Logs and Event IDs
The primary log to investigate isC:\ProgramData\Microsoft\IntuneManagementExtension\LogFiles\DeviceHealthService.log, where the exact line appears as:
0x87D00325 - Application assignment not applicable — scope tag or group exclusion prevents deployment to device.
For Windows Event Viewer, check the Microsoft-Windows-IntuneClient%4Operational.evtx log under Event Viewer > Applications and Services Logs > Microsoft > Windows > IntuneClient. Relevant Event IDs include 1002 (assignment validation failure) and 1009 (device scope mismatch). Use PowerShell to filter logs:
Get-WinEvent -LogName "Microsoft-Windows-IntuneClient/Operational" | Where-Object { $_.Message -match "0x87D00325" }.
Cross-reference the device's DeviceId from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\Client\DeviceId with the logs to isolate the affected device.
Root Causes
1. Incorrect Scope Tag Assignment
The device lacks a required scope tag defined in the application's assignment. Verify the device's scope tags viaIntune admin center > Devices > All devices > [Device] > Scope tags. Compare with the application's assignment scope tags in Intune admin center > Apps > [App] > Assignments.
2. Group Exclusion in Assignment
The device belongs to a group explicitly excluded in the application's assignment. Check the "Exclude groups" section in the application's assignment blade. UseGet-MgDeviceManagementDevice -Filter "id eq 'device_id'" to validate group membership.
3. Enrollment Profile Misconfiguration
The device was enrolled using a profile that does not inherit scope tags. Confirm the enrollment profile's scope tag settings inIntune admin center > Enrollment > Windows enrollment > [Profile] > Scope tags. Devices enrolled without a scope tag may fail assignments requiring one.
Fix Procedure
- Verify the device's scope tags:
Get-MgDeviceManagementDevice -Filter "id eq '$(Get-Content C:\DeviceId.txt)'" - Adjust application assignment scope:
Intune admin center > Apps > [App] > Assignments > Add scope tags - Remove conflicting group exclusions:
Intune admin center > Apps > [App] > Assignments > Remove excluded groups - Update enrollment profile scope tags:
Intune admin center > Enrollment > Windows enrollment > [Profile] > Scope tags > Add - Force device sync:
Invoke-IntuneDeviceSync -DeviceId $(Get-Content C:\DeviceId.txt)
Modifying the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Intune\Client\DeviceId directly may disrupt enrollment. Always back up the registry before changes.Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D00324 | Policy conflict during assignment | References policy enforcement rules |
0x87D00326 | Device compliance check failed | Includes compliance policy name |
0x87D00325 | Scope tag/group exclusion | Explicit mention of "not applicable" |
Verification
After applying fixes, monitorDeviceHealthService.log for the absence of 0x87D00325. In the Intune admin center, navigate to Devices > All devices > [Device] > Compliance and confirm the application appears under "Assigned apps." Use Get-IntuneApplicationAssignment -Filter "deviceName eq 'DEVICE_NAME'" to verify assignment status. A successful sync will show the application in the "Assigned" state with no errors in the Microsoft-Windows-IntuneClient/Operational log.
Prevention
Implement a baseline policy that enforces scope tag usage for all application assignments. Use PowerShell to audit assignments:Get-IntuneApplication | Where-Object { $_.assignments -notmatch "scopeTag" } | Select-Object displayName.
For group exclusions, create a dedicated "Exclusion" group and apply it consistently across assignments. Configure enrollment profiles to inherit scope tags by default. Additionally, deploy a custom OMA-URI policy to log scope tag mismatches:
./Device/Vendor/MSFT/Intune/ScopeTagValidation/LogLevel set to 3 (verbose). Regularly review DeviceHealthService.log for recurring patterns using:
Get-Content C:\ProgramData\Microsoft\IntuneManagementExtension\LogFiles\DeviceHealthService.log | Select-String "0x87D00325".
Use
dsregcmd /status to quickly check if a device is enrolled in Intune and its current scope tags.