# Custom Apps "Detection Rules" tab

*Applies to: Patch My PC Cloud Custom Apps*

{% hint style="info" %}
**Note**

Configuring Native Detection Rules is optional.
{% endhint %}

If you want to configure Native Detection Rules:

1. On the **Detection Rules** tab, click **Use Custom** to use a custom detection rule, then choose the relevant type of rule from the **Rule Type** dropdown.

{% hint style="info" %}
**Note**

You should only choose to use a custom detection method if our default method of scanning the uninstall registry on the endpoint to find a **Display Name** matching your **Apps & Features Name** entry and a **Display Version** that meets or exceeds the **Version** in the **Configuration** tab is unsuitable for this app.
{% endhint %}

{% hint style="danger" %}
**Important**

If you configure Detection Rules in the PMPC Cloud portal you:

* Cannot deploy the same app in Publisher as Publisher does not support Native Detection Rules.
* Should not create and manage detection rules in the Intune admin center as they will not be detected and shown in the PMPC Cloud portal.
* Cannot mix our default detection method with custom detection methods for the same Custom App.
  {% endhint %}

<figure><img src="/files/1bpMEHLjampM6qWhAfcE" alt="Clicking &#x27;Use Custom&#x27; to use a custom detection rule and choosing the relevant type of rule from the &#x27;Rule Type&#x27; dropdown" width="563"><figcaption></figcaption></figure>

2. Go to Step 8 if you chose the **Use Custom Script** option.
3. If you choose the **Configure Manually** option, click **Add Rule**.

<figure><img src="/files/1YmmIGs2Y4NMaDNiPZWv" alt="Clicking &#x27;Add Rule&#x27;" width="563"><figcaption></figcaption></figure>

4. On the **Add Detection Rule** screen, select the relevant type of rule from the **Rule Type** dropdown, then configure the required options as required.

<figure><img src="/files/bhO1SCMD3D7bNXZIuktq" alt="Selecting the relevant type of rule to configure from the &#x27;Rule Type&#x27; dropdown" width="380"><figcaption></figcaption></figure>

<table><thead><tr><th width="99.111083984375">Rule Type</th><th>Available Options</th></tr></thead><tbody><tr><td>File</td><td><p><strong>Path –</strong> The path to the folder you are checking for</p><p><strong>File or Folder –</strong> The folder containing the file you are checking for</p><p><strong>Detection Method –</strong> Choose from the list of available checks.</p></td></tr><tr><td>MSI</td><td><p><strong>MSI Product Code –</strong> This is the MSI product code extracted from the file you imported.</p><p><strong>MSI Product Version Check (optional)</strong> – Click this slider to enable this check for a specific version number that matches the options you configure in the <strong>Operator</strong> and <strong>Value</strong> fields.</p></td></tr><tr><td>Registry</td><td><p><strong>Key Path –</strong> The path to the Registry key</p><p><strong>Value name (optional) –</strong> The name of a value contained within the specified <strong>Key Path</strong> that you want to check for</p><p><strong>Detection Method –</strong> Choose from the list of available checks.</p></td></tr></tbody></table>

{% hint style="info" %}
**Note**

You can only create up to a maximum of 25 rules of all types per deployment. Of these 25, only one can be an MSI detection rule and the rest can be a mixture of **File** and **Registry** rules.

See the following Microsoft resources for more information:

* [win32LobAppFileSystemRule resource type](https://learn.microsoft.com/en-us/graph/api/resources/intune-apps-win32lobappfilesystemrule?view=graph-rest-1.0)
* [win32LobAppPowerShellScriptRule resource type](https://learn.microsoft.com/en-us/graph/api/resources/intune-apps-win32lobapppowershellscriptrule?view=graph-rest-1.0)
* [win32LobAppProductCodeRule resource type](https://learn.microsoft.com/en-us/graph/api/resources/intune-apps-win32lobappproductcoderule?view=graph-rest-1.0)
* [win32LobAppRegistryRule resource type](https://learn.microsoft.com/en-us/graph/api/resources/intune-apps-win32lobappregistryrule?view=graph-rest-1.0)
  {% endhint %}

5. If you have created either a **File** or **Registry** detection rule, click the **Associated with a 32-bit app on 64-bit clients** slider to enable it to expand any path environment variables in the 32-bit context on 64-bit endpoints.<br>

   <figure><img src="/files/iDpXiVpzysF3gxhQIwWX" alt="Enabling the &#x27;Associated with a 32-bit app on 64-bit clients&#x27; slider" width="377"><figcaption></figcaption></figure>

6. Click **Add Rule** to add the rule.<br>

   <figure><img src="/files/vqOw7n5IeNwiYq8cCNRp" alt="Clicking &#x27;Add Rule&#x27; to add a rule" width="377"><figcaption></figcaption></figure>

   \
   The rule is added to the list of detection rules.

<figure><img src="/files/UuaayiXEIeq1zu9jMm7i" alt="Rule is added to the list of rules" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

You can:

* Edit a Detection Rule by clicking the pencil icon beside the relevant rule, making the required changes then clicking **Save rule** to save the changes.
* Delete a Detection rule by clicking the red trashcan beside the relevant rule to remove it from the list of rules.
  {% endhint %}

7. Go to step 10 if you do not want to add a detection rule that uses the **Use Custom Script** option.
8. If you choose the **Use Custom Script** option, click **Import Script**, then browse to and select the relevant script you want to import.

{% hint style="info" %}
**Note**

In the current version:

* We only support PowerShell (.ps1) scripts
* You can only import a single script
* We do not sign your scripts if we use them in one of our deployments. If this is a requirement, you will need to sign the scripts yourself.
  {% endhint %}

<figure><img src="/files/ptRFk2a5r8mSTxRCiJ67" alt="Clicking &#x27;Import Script&#x27;" width="563"><figcaption></figcaption></figure>

A preview of the script is shown in the **Script Preview** window.

{% hint style="info" %}
**Note**

You cannot edit the script in the **Script Preview** window.
{% endhint %}

<figure><img src="/files/51X4ecky2wt6vOpshEHS" alt="Preview of the script shown in the &#x27;Script Preview&#x27; window." width="563"><figcaption></figcaption></figure>

9. Click the **Associated with a 32-bit app on 64-bit clients** slider to enable it to expand any path environment variables in the 32-bit context on 64-bit endpoints.

<figure><img src="/files/6YzZI8hSiLATIvEGW9Yg" alt="Enabling the &#x27;Associated with a 32-bit app on 64-bit clients&#x27; slider" width="563"><figcaption></figcaption></figure>

10. Repeat the steps in this section to add any additional detection rules.
11. If you are happy you have entered all of the details for the app correctly, click **Create** to complete the creation of the Custom App.\
    \
    However, we recommend you click **Next** to move to the [Summary](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-summary-tab.md) tab where you can  verify the configuration before saving the Custom App.

{% hint style="info" %}
**Note**

You can use the [Check Detection Rules](/patch-my-pc-cloud/technical-references/intune-reference/check-detection-rules-in-intune.md) process to verify your detection rules have been successfully created in Intune by PMPC Cloud.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-detection-rules-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.