> 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/advanced-tab/intune-tenant-mismatch-checker.md).

# Intune Tenant Mismatch Checker section of Patch My PC Publisher

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

{% hint style="danger" %}
**PRE-RELEASE DOCUMENTATION**

This article is for a feature that is currently under development.

This banner will be removed once this article is finalized.
{% endhint %}

The **Intune Tenant Mismatch Checker** section of Patch My PC (PMPC) Publisher helps you to identify applications that may have been published to the wrong Intune tenant by comparing your publishing history with actual tenant data.

<figure><img src="/files/UqudLBlDE0vl9jp5XFrQ" alt="&#x27;Intune Tenant Mismatch Checker&#x27; section" width="563"><figcaption></figcaption></figure>

This tool helps you find mismatched, orphaned, or misplaced applications across all configured tenants.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/advanced-tab/intune-tenant-mismatch-checker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
