> 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.md).

# Scan Intune in Patch My PC Publisher

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

The **Scan Intune** tab of Patch My PC (PMPC) Publisher requires access to your Intune tenant through Microsoft Graph. It inventories installed apps to determine which third-party products are present in your environment.

The scan results are compared against Publisher's catalog to identify supported products. This information helps you decide which products to enable on the **Intune Apps** or **Intune Updates** tabs for deploying newer versions of apps and updates through Intune as Win32 apps.

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

The **Scan Intune** tab is shared between the **Intune Apps** and the **Intune Updates** tab and behaves identically in both locations. As a result, you can use the settings on the **Intune Apps** tab to configure and control auto-publishing behavior on the **Intune Updates** tab, and vice versa.

Although the **Scan Intune** tab is shared, manually selecting products in the query results enables them only on the tab from which you launched the form. For example, launching the scan wizard from the **Intune Apps** tab enables products for apps, whereas launching it from the **Intune Updates** tab enables products as updates.
{% endhint %}

{% hint style="success" %}
**Tip**

The **Scan Intune** tab uses the Entra ID App Registration, configured from the [Intune Options](/patch-my-pc-publisher/manage/intune-tabs/intune-options.md) tab, to connect to Microsoft Graph to retrieve data from the Intune Reporting Endpoint. For more details about the required API permissions and authentication options, see [Entra ID App Registration](/patch-my-pc-publisher/requirements/intune-requirements/entra-id-app-registration.md).
{% endhint %}

The following actions can be configured from the **Scan Intune** tab:

* [Configure Auto-Publishing Rules](/patch-my-pc-publisher/manage/intune-tabs/scan-intune/auto-publishing-rules.md)
* [Configure Filters](/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md)
* [Perform a Query](/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#query-button)
* [Export to a CSV file](/patch-my-pc-publisher/manage/intune-tabs/scan-intune/filters-discovered-products.md#export-to-csv-button)


---

# 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.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.