> 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/product-integrations.md).

# Product Integrations category of Patch My PC Publisher

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

The **Product Integrations** category on the **Advanced** tab of Patch My PC (PMPC) Publisher allows you to configure:

* [Product Integrations](#product-integrations)
* [ARM application support](#arm-architecture-application-support)

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FPuYVrPVNsoKgDtqhbNNn%2Fimage.png?alt=media&amp;token=1ac0bec3-d7ad-4f3f-9182-e6efbe1dad38" alt="&#x27;Product Integrations&#x27; category" width="563"><figcaption></figcaption></figure>

## Product Integrations

The **PRODUCT INTEGRATIONS** section is used to control which integrations and tabs are visible in Publisher.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F9vw733ZsmuhQUspt6HXt%2Fimage.png?alt=media&amp;token=c89cab93-9764-4e26-8b5f-14da8b67b084" alt="&#x27;PRODUCT INTEGRATIONS&#x27; section" width="252"><figcaption></figcaption></figure>

The following options are available:

* **Disable ConfigMgr Apps**\
  When enabled, the **ConfigMgr Apps** tab is hidden. Publishing applications to ConfigMgr is no longer available from the Publisher interface.
* **Disable WSUS Updates**\
  When enabled, the **WSUS Updates** tab is hidden. Publishing software updates to WSUS is no longer available from the Publisher interface.
* **Disable Intune**\
  When enabled, the **Intune Apps** and **Intune Updates** tabs are hidden. Publishing apps and updates to Intune is no longer available from the Publisher interface.

## ARM Architecture Application Support

The **ARM ARCHITECTURE APPLICATION SUPPORT** section controls whether Publisher evaluates and publishes ARM64 applications.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fs2NWKQMjErijggEPP04S%2Fimage.png?alt=media&amp;token=c6107814-8abf-45bf-9df4-79a09346e095" alt="&#x27;ARM ARCHITECTURE APPLICATION SUPPORT&#x27; section" width="254"><figcaption></figcaption></figure>

### ARM support

When you enable the **ARM support** option (which is disabled by default), Publisher prompts you to confirm.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FV4ywDhCa0RCw1Z2Kpdaj%2Fimage.png?alt=media&amp;token=70484d1d-02f0-4177-b733-a66df9beb69b" alt="&#x27;Arm Support&#x27; confirmation" width="464"><figcaption></figcaption></figure>

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

Once enabled, this setting cannot be disabled.
{% endhint %}

Once enabled, Publisher begins supporting ARM64 applications. ARM64 products are evaluated during Publisher syncs using existing auto-publishing rules.

Enabling this option causes ARM64 applications to be included in evaluation and publishing logic. Existing auto-publishing rules are applied without modification, which may result in new ARM64 applications being published automatically.

As this setting is permanent, you should only enable it after confirming that ARM64 application support is required in your environment.

### ARM64 Application Naming

When ARM64 support is enabled, ARM-based applications are shown alongside existing products in the Product Tree on the following tabs:

* **WSUS Updates**
* **ConfigMgr Apps**
* **Intune Apps**
* **Intune Updates**

ARM applications are identified by **ARM64** appended to the application name. This naming clearly distinguishes ARM64 installers from x64 and x86 variants.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FMZRJ8Gjk3fvkM4UWAo5G%2Fimage.png?alt=media&amp;token=b76dceb0-256a-4ac9-b3ee-8edf0eede300" alt="ARM64 Products in the Product Tree" width="259"><figcaption></figcaption></figure>

### Automatic Requirement Handling

For third party updates published to WSUS, ARM64 applicability is controlled by a well-known detectoid defined in the Patch My PC catalog software distribution package. This detectoid limits the update to supported architectures only.

```xml
<sdp:Prerequisites>
  <sdp:AtLeastOne>
    <sdp:PackageID>4103af66-247a-4782-b970-8899394c27c3</sdp:PackageID>
  </sdp:AtLeastOne>
</sdp:Prerequisites>
```

For ConfigMgr applications, ARM64 applications automatically include an operating system requirement that limits installation to Windows ARM64. This ensures the application is only offered to supported devices.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F8Bby2OhhPMTvcd2kK5bl%2Fimage.png?alt=media&amp;token=301401e5-19e3-4cb1-a23b-cde9fca4cd0a" alt="ConfigMgr OS Requirements" width="563"><figcaption></figcaption></figure>

For Intune Win32 applications, the operating system architecture requirements are automatically configured during publishing. ARM64 applications are limited to ARM64 devices, while most x64 applications are allowed to install on both x64 and ARM64 devices.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FSRuz2O2eNP95ZCHulwJs%2Fimage.png?alt=media&amp;token=13d7367d-71f0-425e-b309-c5ebd1358245" alt="Intune OS Requirements" width="563"><figcaption></figcaption></figure>

### Assignments

Architecture-specific apps may report as **Installed** on devices with a different architecture due to a known detection script limitation. This is a reporting issue only and does not result in any software being installed.&#x20;

{% hint style="info" %}
Note

See [ARM64 update may show as Installed on x64 devices](https://patchmypc.com/kb/arm64-update-may-show-as-installed-on-x64-devices/) for details and a recommended workaround.
{% 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 dynamically 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/manage/advanced-tab/product-integrations.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 `build a script that syncs our docs to a CMS` 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.