> 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-cloud/migration/migrate-application/publish-migrated-app-catalog-app.md).
# Publish the App Migrated from ConfigMgr in Intune as a Patch My PC Catalog App
*Applies to: Patch My PC Cloud*
When migrating a Configuration Manager (ConfigMgr) application to a Patch My PC (PMPC) Catalog App, the deployment wizard starts, and you can follow [Deploying an App using Cloud](/patch-my-pc-cloud/deployments/deploy-app.md), but please note the following:
* Verify that the information on each tab is correct before clicking **Next**.
* On the **Configurations** tab, under the **Install Parameters** tool/section, check that the **Additional Argument** field is correct and includes any required additional arguments/command line options.
* On the **Assignments** tab, you can click **ConfigMgr Assignment List** to see a list of the current assignments in ConfigMgr, so you can then review this and set these up in Intune accordingly.
{% hint style="danger" %}
**Important**
We do not match ConfigMgr assignments to Entra ID groups. You need to manually configure your assignments during app deployment.
{% endhint %}
Once you have added your assignments, click **Migrate** and the **Deployment Created, Migration Pending** notification is shown.
The **Status** field also updates to **In Progress** whilst the deployment is created, with any required content (such as extra files) being zipped and sent to Azure Blob Storage.
You can also monitor deployment progress by clicking the **Deployments** node and watching for the deployment **Status** to change to **Success**.
{% hint style="success" %}
**Tip**
To see the migrated app in Intune, within the Microsoft Intune admin center navigate to:
**Home | Apps | Windows | Windows | Windows Apps | <*****app\_name*****>**
{% 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-cloud/migration/migrate-application/publish-migrated-app-catalog-app.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.
