> 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/publisher-requirements/custom-app-requirements.md).

# Custom App Requirements

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

## Overview

Patch My PC Custom Apps allow you to package and manage your own applications alongside the Patch My PC catalog. The Publisher integrates with [Patch My PC Cloud](https://docs.patchmypc.com/patch-my-pc-cloud) to retrieve Custom App metadata and publish it into your environment using your existing publishing workflows. The requirements below explicitly apply only if you are publishing Custom Apps through the on-premises Publisher to either ConfigMgr or Intune.

## Requirements

To publish Custom Apps to either ConfigMgr or Intune using the the Publisher, you must meet **all** of the following requirements:

* Publisher version 2.1.20.0 or later.
* An active Enterprise Plus, Enterprise Premium, or MSP subscription.
* Your organization must be [onboarded ](#step-1-onboard-to-patch-my-pc-cloud)to Patch My PC Cloud by creating a Cloud Company.
* The Publisher must be [connected ](#step-2-connect-the-publisher-to-patch-my-pc-cloud)to the Cloud Company.

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

Customers with an MSP or MSP Plus subscription can connect the Publisher to only one Patch My PC Cloud company. We recommend connecting the Publisher to the MSP parent Cloud company, rather than an individual MSP customer Cloud company, to ensure proper management and visibility of the Custom Apps made available to the Publisher.
{% endhint %}

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

If you only plan to deploy your Custom Apps from Patch My PC Cloud, the Publisher is not required.
{% endhint %}

## Step 1: Onboard to Patch My PC Cloud

1. Sign in or sign-up to **Patch My PC Cloud**.
2. Create or select your **Cloud Company**

For detailed onboarding instructions, see <https://docs.patchmypc.com/patch-my-pc-cloud/onboard-to-cloud>.

## Step 2: Connect the Publisher to the Patch My PC Cloud Company

If you plan to publish Custom Apps or use Cloud-integrated features from the on-premises Publisher, you must create a Cloud connection.

1. Open **Patch My PC Publisher**.
2. Navigate to **Administration > Cloud Connections**.
3. Select **Add a Connection**.
4. Sign in using your Patch My PC Cloud credentials.
5. Complete the connection wizard and confirm the connection status.

Once connected, the Publisher can securely communicate with Patch My PC Cloud for supported features.

For detailed connection steps, see <https://docs.patchmypc.com/patch-my-pc-cloud/cloud-administration/manage-cloud-connections/add-a-connection>.

### Multiple Cloud Companies

If the account used to sign in is associated with multiple Patch My PC Cloud companies, a selection window will appear.

<figure><img src="/files/23lJX2Q3b8i6x3dxtl2t" alt="Select a Cloud Company" width="375"><figcaption></figcaption></figure>

Select the appropriate company from the list and click OK to complete the connection process.


---

# 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/publisher-requirements/custom-app-requirements.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.