> 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/technical-references/multi-tenant-support/overview.md).

# Overview of Multitenant Support in Patch My PC Publisher

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

{% hint style="danger" %}
**IMPORTANT**

This article has not been updated for Version 3.x. Once it has, this banner will be removed.
{% endhint %}

Multiple Intune tenants can be supported from a single instance of the Patch My PC (PMPC) Publisher. This capability is designed for managed service providers who require centralized control while maintaining tenant-level separation.

{% hint style="danger" %}
**Important**

The multi-tenant form controls are only visible if Publisher is licensed with an MSP or MSP Plus license.
{% endhint %}

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FoVbTdUJMJV5zG0scKX2M%2Fimage.png?alt=media&amp;token=24f9ca32-01d9-4932-96f4-a38c28305091" alt="Multi-tenancy in the Publisher" width="545"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Important**

For managed service providers, Patch My PC Cloud is the recommended solution. It reduces infrastructure requirements and removes the need to maintain a Publisher installation.

See [Managed Service Provider Overview](https://docs.patchmypc.com/patch-my-pc-cloud/managed-service-provider-feature/overview.md) for more information.
{% endhint %}

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

Publisher still remains useful in scenarios where customers operate in sovereign or government cloud environments. In these cases, the Publisher allows you to modify Microsoft Graph endpoints to ensure publishing targets the appropriate cloud environment.
{% endhint %}


---

# 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/technical-references/multi-tenant-support/overview.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.
