Compliance status - Not applicable on some devices

Question

Compliance status - Not applicable on some devices

Denys Pasternak 85

Hello,

I have a problem: 40 devices are applying a compliance policy that uses a script to check for the presence of an application. Of these 40 devices, 10 have a "Not applicable" status.

I would like to provide an example script, but for some unknown reason, my previous question was deleted. I replaced the PowerShell script and the example JSON response by pasting the code, but my question was deleted.

The devices are the same, and the application is searched for through the registry, while the other application is searched through Win32_Product. In one case, there are approximately 10 devices with a "Not applicable" status, and in the second case, there are also approximately 10 devices with a "Not applicable" status, but the devices are different.

powershell_ise_nYIxNGwk0r

powershell_ise_vyexnGnSfN

The crux of the matter is this: what could be the possible reasons for the "Not applicable" status? The script always returns either the found application or the "Not found" value.

Thank you in advance for your advice.

0 comments

2 answers

Your answer

Answer 1

Denys Pasternak 85

Looks like I needed to wait a few days. Everything seems to be fine now.

0 comments

Answer 2

The "Not applicable" status for compliance policies in Microsoft Intune can occur for several reasons:

Unsupported Settings: The specific setting being checked may not be supported on the version or edition of Windows running on the device. For instance, if the compliance policy is looking for a feature or application that is only available in newer versions of Windows or specific editions (like Professional or Enterprise), devices running older versions or different editions may show as "Not applicable".
Script Evaluation Issues: If the script used to check for the application does not execute correctly or if it returns an unexpected result, it could lead to a "Not applicable" status. Ensure that the script is functioning as intended and returning the expected values.
Device Configuration: There may be configurations on the devices that prevent the compliance checks from being applicable. For example, if the registry key or the application being checked does not exist on the device, it may result in a "Not applicable" status.
Timing Issues: Sometimes, there can be delays in applying compliance policies after devices enroll or after changes are made. If the devices were recently enrolled or if the compliance policy was recently updated, it might take some time for the status to reflect correctly.

To troubleshoot further, you may want to review the compliance reports for any error codes or additional insights that could help identify the specific reasons for the "Not applicable" status on those devices.

References:

Some settings in a Windows profile return "Not Applicable"

Share via

Compliance status - Not applicable on some devices

2 answers

Your answer