> 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/overview.md).
# Overview of the Intune Apps and Intune Updates tabs in Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **Intune Apps** and **Intune Updates** tabs in Patch My PC (PMPC) Publisher let you select which third-party applications and updates to publish to Intune. Products enabled here determine which third-party applications and updates Publisher publishes and maintains in your environment.
Third-party applications *and* updates appear in the **All Apps** node in the Intune Admin Center.
{% hint style="info" %}
**Note**
You can configure additional behavior related to application and update publishing from the [Intune Options](/patch-my-pc-publisher/manage/intune-tabs/intune-options.md) tab on either the **Intune Apps** or **Intune Updates** tabs.
{% endhint %}
## Differences 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 they handle applicability.
*Intune Apps* are designed for initial installation and lifecycle management. They generally apply to any targeted device unless assignment filters or requirements restrict them.
However, although *Intune Updates* are still Win32 apps, they include an additional requirement script. This script evaluates whether an older version of the app is already installed on the device. The update Win32 app is considered applicable only if it detects a previous version. This ensures that updates target existing installations rather than installing new apps.
Because Intune does not have a native compliance evaluation model like WSUS, this requirement uses script-based logic to simulate update applicability while remaining fully integrated with the native Intune Win32 application model.
---
# 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/overview.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.
