> 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/configure/product-selection-discovery/discover-intune-apps-updates.md).

# Discover Intune Apps and Updates using Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

This page provides guidance on how to discover apps in your environment or manually select products for publishing as Microsoft Intune apps and Intune updates using Patch My PC (PMPC) Publisher.

When integrated with Intune, you can scan your tenant to identify supported third party apps that are already discovered. You can also manually browse and select products directly from the Publisher catalog.

After completing the steps in this section, you will be able to enable and publish third party apps and updates to Intune that align with your organization’s requirements.

## Difference Between Intune Apps and Intune Updates

Products on both the **Intune Apps** and **Intune Updates** tabs are published as Win32 apps and use the same core detection method to determine installation state. The key difference is how applicability is handled.

*Intune Apps* are designed for initial installation and lifecycle management. They are generally applicable to any targeted device unless restricted by assignment filters or requirements.

*Intune Updates*, while still Win32 apps, include an additional requirement script that evaluates whether an older version of the app is already installed on the device. The update of a Win32 app is only considered applicable if a previous version is detected. This approach ensures that updates target existing installations rather than installing new apps.

As Intune does not have a native compliance evaluation model like WSUS, this requirement-script-based logic is used to simulate update applicability while remaining fully integrated with the native Intune Win32 app model.

### Discovering and Selecting Applications

You can enable apps and updates for publishing in one of two ways:

* [Automatically discover installed products by querying Intune](#automatically-discover-installed-products-by-querying-intune)
* [Manually browse and select products directly from the Product Tree on the Intune tabs](#manually-browse-and-select-products-directly-from-the-product-tree-on-the-intune-tabs)

### Automatically discover installed products by querying Intune

Running a [query](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#query-button) on the  [Scan Intune](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune.md) tab is the recommended starting point, as it leverages Intune Discovered Apps data to identify supported third-party products currently present in your environment and compares those results against the Patch My PC catalog. This allows you to review what is installed today before enabling publishing.

After running a [query](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#query-button), review the results carefully. The device [count](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#count-column) and version information help validate inventory accuracy and determine publishing priority. [Exporting the results to CSV](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#to-export-the-results-to-a-csv) can support internal review, change-control discussions, or phased rollout planning.

A common and effective approach is to begin conservatively. Enable a small number of familiar, low-impact apps to understand how Intune apps and updates are created by Publisher. Many customers start with widely used utilities such as 7-Zip or Notepad++ to gain confidence in the workflow.

Once you are comfortable with how apps and updates are created and maintained, you can expand your product selection or consider enabling [auto-publishing rules](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs/scan-intune/auto-publishing-rules.md) to automate app lifecycle management over time to create new apps and updates based on discovery thresholds.

### Manually browse and select products directly from the Product Tree on the Intune tabs

Apps and updates can also be enabled manually by selecting products directly from the [Product Tree](https://docs.patchmypc.com/patch-my-pc-publisher/fundamentals/product-tree/working.md) on the [Intune Apps and Intune Updates](https://docs.patchmypc.com/patch-my-pc-publisher/manage/intune-tabs.md) tabs.

Manual selection remains a valid and flexible option, especially when you want to proactively publish apps that may not yet appear in the inventory returned by the scan results.

You can expand vendors to browse available products or use the [Filter](https://docs.patchmypc.com/patch-my-pc-publisher/fundamentals/product-tree/working.md#filter-field) field to quickly locate a specific app or update by name.

When selecting *apps*, we recommend you standardize on a single installer variant whenever multiple options are available. For example, some products may provide:

* MSI and EXE variants
* x86 and x64 architectures
* ARM64 variants.

In most environments, it is recommended to standardize on a single architecture and installer type, such as MSI (x64), unless there is a specific requirement for an alternative variant.

When selecting *updates*, it is often appropriate to enable multiple update variants if they exist in your estate. For example, if both x86 and x64 variants are detected, publishing updates for both ensures all devices remain compliant while you work toward long-term standardization.


---

# 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/configure/product-selection-discovery/discover-intune-apps-updates.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.
