> 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/technical-references/unsupported-reasons.md).

# "Unsupported" Reasons for ConfigMgr to Intune App Migration using Patch My PC Cloud

*Applies to: Patch My PC Cloud*

In most cases, Microsoft Configuration Manager (ConfigMgr) applications cannot be migrated to Patch My PC (PMPC) Cloud because the Publisher, running in the **SYSTEM** context, cannot access or correctly interpret the application’s content source.

The most common reasons are:

* The Publisher does not have SMB or NTFS access to the directory specified in the **Content location** field on the **Content** tab of the ConfigMgr deployment type.
* The **Content location** directory specified on the **Content** tab of the ConfigMgr deployment type is empty.
* The installer referenced in the **Installation program** field of the ConfigMgr deployment type cannot be found.
* The application content source contains more than 1,000 files.

These issues account for most unsupported applications.

Less common reasons may still apply and are surfaced directly in the [Migration Dashboard](/patch-my-pc-cloud/migration/about-migration-dashboard.md).


---

# 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/technical-references/unsupported-reasons.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.