> 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/manage/intune-tabs/scan-intune/auto-publishing-rules.md).
# Auto-Publishing Rules section of Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **AUTO-PUBLISHING RULES** section on the **Scan Intune** tab of Patch My PC (PMPC) Publisher allows Publisher to automatically enable products for publishing based on what is detected in your Intune environment, removing the need to manually review scan results and enabling a more hands-off approach to keeping third-party applications and updates current.
When these rules are enabled, Publisher evaluates discovered application inventory data collected by the Intune Management Extension on managed devices, compares detected applications against the Patch My PC catalog, and automatically enables supported products that meet the configured device threshold.
Auto-publishing rules are evaluated during scheduled [synchronizations](/patch-my-pc-publisher/manage/sync-tab.md). Each time a sync runs, Publisher scans application inventory data from the AppInvRawData report, obtained from the Intune Reporting Endpoint, through Microsoft Graph, and automatically enables any newly detected products that meet the configured thresholds.
This automation can be extremely powerful, but it’s important to configure it thoughtfully.
{% hint style="info" %}
**Note**
Automatic enablement of products is based solely on configured device thresholds. Filters in this form only control what is displayed in the query results and do not influence which applications or updates are automatically enabled.
{% endhint %}
## Auto-enable products to be published as an update
When you enable the **Auto-enable products to be published as an update** option, products detected in the inventory report obtained through Microsoft Graph are automatically enabled on the **Intune Updates** tab once they are found on at least the specified number of devices.
* The device count acts as a threshold to prevent enabling products seen only on a small number of machines
* Once enabled, updates for the product are published according to your existing sync and deployment processes.
This option is commonly used to keep patching coverage up to date as new applications appear in the environment.
## Auto-enable products to be published as an application
When you enable the **Auto-enable products to be published as an application** option, products detected in the inventory report obtained through Microsoft Graph are automatically enabled on the **Intune Apps** tab once they are found on at least the specified number of devices.
* This allows Patch My PC to automatically manage application creation for newly detected software.
* The same device threshold concept applies to avoid enabling applications prematurely.
This option is typically used in environments that want application lifecycle management to be driven directly from inventory data.
## Auto-enabled Products and Assignment Inheritance
When products are automatically enabled by auto-publishing rules based on the configured device threshold, any Intune assignments configured at the **All Products Level** or **Vendor** level in the [Product Tree](/patch-my-pc-publisher/fundamentals/product-tree/working.md) are not inherited by newly enabled products. Newly detected products are enabled for publishing only and do not automatically receive existing assignment configurations.
Customers should review the publishing reports after each synchronization to identify products that were automatically enabled. After reviewing the report, configure the desired assignments directly on those products in Publisher.
Alternatively, customers can use the [Manage Assignments](/patch-my-pc-publisher/customizations/list-customizations/manage-assignments.md) right-click customization option to automatically apply assignments to auto-published Intune updates.
{% hint style="info" %}
**Note**
See [Auto-Enabled Products and Dynamic Assignments](#auto-enabled-products-and-dynamic-assignments) for more information.
{% endhint %}
{% hint style="danger" %}
**Important**
Reapplying assignments at a higher level in the Product Tree to force inheritance on products enabled through auto-publishing rules is supported but should be used with caution. Reapplying assignments at the product or vendor level overwrites any assignments already configured on child products. This action can unintentionally replace specific assignment configurations that were intentionally set on individual products.
{% endhint %}
## Auto-Enabled Products and Dynamic Assignments
Customers can use the [Manage Assignments](/patch-my-pc-publisher/customizations/list-customizations/manage-assignments.md) right-click customization option, at the **All Products** level, for **Intune Updates** to automatically apply assignments to auto-published updates. This automates assignment behavior for newly enabled products.
Dynamic Assignments are evaluated only for products that are currently enabled in Publisher's Product Tree on the **Intune Updates** tab 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, there is a timing consideration. During the first synchronization, auto publishing rules enable the product and publish the update. Because the product was not enabled at the start of the synchronization, Dynamic Assignment evaluation does not occur then.
A second 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 considered when designing automation workflows that combine auto publishing rules with Dynamic Assignments.
{% hint style="info" %}
**Note**
Assignments added using the Manage Dynamic Assignments feature do not persist indefinitely in Publisher's configuration. Dynamic Assignments are evaluated during each synchronization and applied only to updates that meet the configured criteria at that time.
{% endhint %}
## Device Threshold Best Practice
Patch My PC releases about 100 new applications per month, so a scheduled scan can easily detect multiple new products. When low device thresholds are used, auto-publishing can enable these products very quickly, ensuring new additions don’t go unnoticed.
However, this speed should be balanced with operational readiness, as downstream processes such as phased deployments and change control may not be prepared for a sudden influx of new applications and updates, particularly when assignments are broadly scoped.
{% hint style="danger" %}
**Important**
While it may be tempting to set the device threshold to a very low number, even **1**, this is generally not recommended for most environments. This would be especially impactful for new customers who have not yet reviewed and enabled products in the Product Tree, as a very low threshold can cause newly discovered applications to be enabled simultaneously, potentially resulting in a large number of updates being synchronized at once.
{% endhint %}
A common and effective approach is:
1. Use the Scan Wizard to identify products currently installed in your environment.
2. Enable the products from the Scan Wizard [query](broken://pages/FL8382g8t5tZXwz5oTKP) window or [Product Tree](/patch-my-pc-publisher/fundamentals/product-tree/working.md), and [customize](/patch-my-pc-publisher/customizations.md) them in the Product Tree (conflicting processes, content options, etc.).
3. Enable auto-publishing rules to catch newly introduced applications over time.
This lets you stay in control initially, while still benefiting from automation going forward.
---
# 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/manage/intune-tabs/scan-intune/auto-publishing-rules.md?ask=&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.
