> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-automatic-deployment-rules.md).

# Manage Automatic Deployment Rules option in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*\
*Available at level: All Custom Products, All Products*\
*Available on tab: Intune Updates*

The **Manage Automatic Deployment Rules** right-click option in Patch My PC (PMPC) Publisher allows you to automatically create Intune assignments for newly published updates based on predefined catalog criteria.

Instead of assigning every update to the same Entra groups, Dynamic Assignments evaluates each update during a Publisher [synchronization](https://docs.patchmypc.com/patch-my-pc-publisher/manage/sync-tab.md) and applies assignments only when the update matches your configured rules. This enables targeted deployment based on update attributes rather than static grouping.

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

Dynamic Assignments are conceptually similar to Automatic Deployment Rules in ConfigMgr, but they apply to Intune Updates managed by Publisher.
{% endhint %}

## How Dynamic Assignments Work

During each sync, Publisher evaluates newly published Intune Updates against your configured criteria. Criteria can include attributes such as the presence of a Common Vulnerabilities and Exposures (CVE), CVE severity, keywords in the update title, or the update classification.

If an update meets the defined conditions, Publisher automatically creates assignments for the Entra groups you specify. If an update does not meet the criteria, then no assignment is created.

This approach allows different updates to follow different deployment paths based on risk, urgency, or relevance, without requiring manual assignment for each update.

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

Intune allows only a single assignment per app per group. If the same group is targeted by both a static assignment (through the [Manage Assignments](https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-assignments.md) right-click option) and a dynamic assignment, the dynamic assignment will take precedence.
{% endhint %}

## Evaluation Criteria

Dynamic Assignments evaluate newly published updates using one or more of the following criteria.

* **Has CVE -** A Boolean value that evaluates whether the update has one or more CVE IDs associated with it.
* **Severity -** A multi-select list that includes Critical, Important, Moderate, and Low.
* **Title -** Plain text or regular expression strings used to match update titles. Exclusions can be defined by prefixing a value with a minus sign.
* **Update Classification -** A multi-select list that includes Updates, Critical Updates, and Security Updates.

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

Criteria options that allow multiple values use an **OR** operator. All different criteria types are joined together using an **AND** operator.

In practical terms, this means an update must meet all selected criteria types, but only one value within each type.
{% endhint %}

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

Dynamic Assignments are evaluated **only for products that are currently enabled** in Publisher's Product Tree and **only for the current version of a product** at the time it is published.

When Dynamic Assignments are used together with [auto publishing rules](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/auto-publishing-rules.md), there is an important timing consideration. During the first Publisher synchronization, auto publishing rules enable the product and publish the update. Because the product was not enabled at the start of the sync, Dynamic Assignment evaluation does not occur at that time.

A second Publisher synchronization is required for Dynamic Assignments to evaluate the newly enabled product and determine whether the update meets the configured criteria for assignment.

This behavior is expected and should be accounted for when designing automation workflows that combine auto publishing rules with Dynamic Assignments.
{% endhint %}

## To configure Dynamic Assignments

1. Load Publisher and click the **Intune Updates** tab.
2. Right-click **All Vendors** on either the **Catalog Products** or **Custom Products** tabs, and select **Manage Automatic Deployment Rules**.
3. On the **Manage Dynamic Assignments** screen, click **Add** to create a new Dynamic Assignment rule.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fe7vhoyM4vc0nrEM1aB1N%2Fimage.png?alt=media&amp;token=d82ea438-0582-41ee-ad50-7647f1089c02" alt="Clicking &#x27;Add&#x27; on the &#x27;Manage Dynamic Assignments&#x27; screen" width="563"><figcaption></figcaption></figure>

4. Enter a **Name** and optional **Description** for the rule.
5. Select one or more **Property Filters** to define the evaluation criteria.
6. Configure the **Search Criteria** values for each selected filter.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FMAhfW6ANqwJmJLqXttu2%2Fimage.png?alt=media&amp;token=3d88dbbd-f9cf-4ff8-99b9-40abb9dfc337" alt="New Dynamic Assignment Rule Settings" width="448"><figcaption></figcaption></figure>

7. Click **Preview** to open the **Preview Updates** screen that shows which updates currently match the rule.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fu8Y42EE30PyMbI4VVjqC%2Fimage.png?alt=media&amp;token=bf7845b7-7f0b-42b2-b194-55abc3306f1a" alt="Preview Updates" width="524"><figcaption></figcaption></figure>

8. Click **Close**.
9. Click **Manage** on the **New Dynamic Assignment Rule** screen to configure assignments for the rule.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FDgJcG8I8ETR08Etje5jY%2Fimage.png?alt=media&amp;token=d2e1cfcf-2c05-4f92-8ddb-34025473d7ad" alt="Clicking &#x27;Manage&#x27;" width="448"><figcaption></figcaption></figure>

10. &#x20;Add the required Intune assignments using the standard Manage Assignments window.
11. Click **OK** to save the rule.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FgcSPM4fJairH5l8d86NG%2Fimage.png?alt=media&amp;token=88ecda72-3b01-46ba-a05d-34973ef1abcd" alt="Clicking &#x27;OK&#x27; to save the rule" width="447"><figcaption></figcaption></figure>

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

You can also edit an existing Dynamic Assignment Rule by selecting it and clicking **Edit** or delete an existing Dynamic Assignment Rule by selecting it and clicking **Remove**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-automatic-deployment-rules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
