Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Deployment type not applicable — device assignment filter condition not met for app targeting | Intune client logs | -> |
| Affected OS build range | Windows 11 22H2 | Microsoft Intune documentation | -> |
| Registry key or OMA-URI involved | HKLM\Software\Microsoft\IntuneMdm | Windows Registry | -> |
| Relevant service/endpoint URL | https://graph.microsoft.com/v1.0/deviceManagement/appConfigurations | Microsoft Graph API | -> |
| Log line signature | [IntuneClient] Error 0x87D00269: Deployment type not applicable — device assignment filter condition not met for app targeting | DeviceInstall.log | -> |
Log Files to Check
C:\Windows\Temp\DeviceInstall.logC:\ProgramData\Microsoft\IntuneClient\Logs\IntuneClient.log
What This Error Actually Means
The error code0x87D00269 is raised by the **Intune Management Extension (IntuneMdm)** component during app deployment to Windows 11 22H2 devices. This error indicates that the device does not satisfy the **assignment filter conditions** defined in the app's targeting rules. Specifically, the deployment fails because the device's attributes (e.g., hardware model, group membership, or compliance state) do not align with the filter criteria specified in the Intune app configuration. The error is logged in both C:\Windows\Temp\DeviceInstall.log and C:\ProgramData\Microsoft\IntuneClient\Logs\IntuneClient.log, with the exact line: [IntuneClient] Error 0x87D00269: Deployment type not applicable — device assignment filter condition not met for app targeting. This is not a general deployment failure but a **targeting mismatch**, meaning the app was never intended to apply to the device based on its current state.
Affected Versions and Scope
This error is specific to **Windows 11 22H2 (OS build 22621.x or 22623.x)**. It does not occur on earlier OS versions like Windows 10 or newer builds of Windows 11 (e.g., 23H2 or 24H2) unless explicitly configured. The scope is limited to tenants using **device-based assignment filters** for app targeting. Tenants relying on **user-based targeting** or **group-based targeting without filters** are unaffected. Additionally, this error does not apply to devices enrolled via **Microsoft Endpoint Manager (MEM) co-management** unless the app is explicitly assigned with device filters. Tenants using **Microsoft Graph API** to manage app configurations (e.g., viahttps://graph.microsoft.com/v1.0/deviceManagement/appConfigurations) must ensure their filter syntax adheres to the schema for Windows 11 22H2.
Where To Look First: Logs and Event IDs
Begin by inspecting theDeviceInstall.log and IntuneClient.log files for the exact error string. Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to check for related events. Two critical **Event IDs** to review are:
- **Event ID 10000**: Logs app deployment failures with detailed filter evaluation results.
- **Event ID 10001**: Indicates device attribute mismatches during filter validation.
Use PowerShell to search logs:
Get-Content -Path "C:\ProgramData\Microsoft\IntuneClient\Logs\IntuneClient.log" | Select-String "0x87D00269"
Get-Content -Path "C:\Windows\Temp\DeviceInstall.log" | Select-String "device assignment filter"
Root Causes
1. Invalid or Unsupported Filter Syntax
The filter may use attributes not supported on Windows 11 22H2 (e.g.,device.deviceModel -eq "Surface Pro 9" when the device is a Surface Pro 8). Validate the filter using Get-MgDeviceManagementDeviceAndAppManagementAssignmentFilter -FilterId "YourFilterId" | Select rule.
2. Device Attributes Missing or Incorrect
The device may lack required attributes (e.g., missingdevice.operatingSystemVersion due to incomplete enrollment). Use Get-MgDeviceManagementManagedDevice -Filter "deviceId eq 'DeviceID'" to inspect device properties.
3. Filter Scope Misconfiguration
Filters applied at the **device group level** may conflict with **user group targeting**. Check the app's targeting rules in the Intune admin center: **Intune admin center > Apps > All apps > [App] > Assignments**.Fix Procedure
- **Review Assignment Filters**: Navigate to
Intune admin center > Apps > App management policies > [Filter Name] > Edit. Ensure the filter uses attributes valid for Windows 11 22H2 (e.g.,device.operatingSystem -eq "Windows 11"). - **Validate Device Attributes**: Run
Get-MgDeviceManagementManagedDevice -Filter "deviceId eq 'DeviceID'" | Select operatingSystem, deviceModel, complianceStateto confirm device metadata. - **Modify Registry for Debugging** (Advanced): Set
HKLM\Software\Microsoft\IntuneMdm\EnableFilterDebugLoggingto1to enable verbose filter evaluation logs. - **Update Filters via Graph API**: Use
Invoke-MgGraphRequest -Method PATCH -Uri "https://graph.microsoft.com/v1.0/deviceManagement/assignmentFilters/{id}" -Body @{"rule"="device.deviceModel -eq 'Surface Pro 9'"}to correct syntax. - **Reassign the App**: In the Intune admin center, remove and reassign the app with updated filters under
Intune admin center > Apps > All apps > [App] > Assignments.
Modifying assignment filters can disrupt app deployments for multiple devices. Test changes in a staging group before applying to production.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x87D00269 | Filter condition not met | Logged in DeviceInstall.log with filter evaluation details |
0x87D00204 | Policy not applicable | Relates to device compliance policies, not app targeting |
0x87D00205 | App not found | Occurs when the app is removed from Intune but still assigned |
Verification
After applying fixes, verify by: 1. CheckingIntuneClient.log for absence of 0x87D00269.
2. Running Get-MgDeviceManagementManagedDevice -Filter "deviceId eq 'DeviceID'" | Select appliedPolicies to confirm the app is listed.
3. Reviewing the app's status in the Intune admin center: Intune admin center > Apps > All apps > [App] > Devices should show successful deployment.
Prevention
To prevent recurrence: - **Test Filters in Staging**: UseGet-MgDeviceManagementDeviceAndAppManagementAssignmentFilter -ValidateRule to test filters against sample devices.
- **Enforce Baseline Policies**: Create a device baseline in the Intune admin center (Intune admin center > Devices > Windows > Baselines) to standardize attributes.
- **Monitor with PowerShell**: Schedule Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" to alert on filter mismatches.
Use
dsregcmd /status to quickly verify device enrollment status and attributes without querying Graph API.