> 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/wsus-updates-tab/wsus-options/configmgr-connection.md).

# ConfigMgr Connection section of Patch My PC Publisher

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

The *SMS Provider* is the interface that enables all interactions with Microsoft ConfigMgr, including actions performed in the ConfigMgr console and through supported APIs.

Patch My PC (PMPC) Publisher also relies on the SMS Provider to perform operations such as triggering Software Update Point (SUP) synchronizations, creating and modifying applications, and distributing content.

The **CONFIGMGR CONNECTION** section on the **WSUS Options** tab lets you configure the SMS Provider Connection.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2F9i5pCLr5kBg7BVRXJGEm%2Fimage.png?alt=media&amp;token=dea6338e-5cf7-42ad-a35a-dd50c377f993" alt="&#x27;CONFIGMGR CONNECTION&#x27; section" width="563"><figcaption></figcaption></figure>

As the SMS Provider configuration is shared across Publisher, when you configure the SMS Provider from any of the following locations, the same settings are automatically used in other areas of Publisher:

* **WSUS Updates | WSUS Options**
* **ConfigMgr Apps | Base Install Options**
* The **Sync Schedule** tab.

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

See [Configure the SMS Provider Connection](/patch-my-pc-publisher/technical-references/configure-sms-provider.md) for information on how to configure the SMS Provider connection.
{% 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/manage/wsus-updates-tab/wsus-options/configmgr-connection.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.