> 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/administration/alerts/webhook-notifications/create-a-microsoft-teams-webhook-url.md).

# Create a Microsoft Teams Webhook URL

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

## Create a Workflow

Microsoft Teams webhooks used by the Publisher are created using Teams Workflows. This workflow generates a webhook URL that can be used to send notifications to a specific Teams channel.

To create a webhook URL:

1. Open Microsoft Teams and navigate to the Channel where you want to receive Webhook Notifications.
2. Click the More Options button **…** and select **Workflows**.&#x20;

<figure><img src="/files/sNgOV0D7MvQsbnMVZtI0" alt="Teams Workflows" width="524"><figcaption></figcaption></figure>

3. Select **Send webhook alerts to a channel**.

<figure><img src="/files/0Z52MpTlX4kO053qhMyf" alt="Send webhook alerts to a channel" width="429"><figcaption></figcaption></figure>

4. Allow a moment for the template to load, it can take a minute. Optionally, update the **Name** of the workflow so it can be easily distingushed in PowerAutomate. Click **Next.**

<figure><img src="/files/eYH628jvtRfgtnktViBB" alt="Name the workflow" width="563"><figcaption></figcaption></figure>

5. Allow a moment for the details tab to load to verify which Team and Channel the webhook URL will be created for and click **Add workflow**.

<figure><img src="/files/4SuvtEcqrWHJwnp2tWp1" alt="Add the workflow" width="563"><figcaption></figcaption></figure>

6. Click the **copy** icon to copy the webhook URL to your clipboard before click **Done**.

<figure><img src="/files/jVJBiY9exIFlPRexr1oX" alt="Copy the webhook URL" width="563"><figcaption></figcaption></figure>

The copied URL can be used when [adding ](/patch-my-pc-publisher/administration/alerts/webhook-notifications/webhook-notification-settings.md#add-a-webhook)or [editing ](/patch-my-pc-publisher/administration/alerts/webhook-notifications/webhook-notification-settings.md#edit-a-webhook)a webhook in the Publisher.

## Consideration for Teams Private Channels

Microsoft Teams private channels have stricter permission boundaries than standard channels. Workflows created using Power Automate run as bots by default, and bots are not permitted to post messages to private channels unless explicitly configured.&#x20;

To allow webhook notifications to be delivered to a private channel, the workflow must be updated to post messages as a user instead of as a bot.

Update the Workflow **Post As** Setting:

1. Navigate to [https://make.powerautomate.com](https://make.powerautomate.com/)
2. Locate the workflow used for Teams notifications targeting the private channel and select **Edit**.

<figure><img src="/files/BVtvMWQCM73xFog5xv4r" alt="Edit the Workflow" width="563"><figcaption></figcaption></figure>

3. Select the workflow step named **Post card in a chat or channel**
4. Change the **Post As** value from **Bot** to **User**.

<figure><img src="/files/BZj4oYlvSLMbp7TcXYMa" alt="Post as User not Bot" width="563"><figcaption></figcaption></figure>

5\. Save the workflow.

After this change, webhook notifications can be successfully delivered to Microsoft Teams private channels.


---

# 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/administration/alerts/webhook-notifications/create-a-microsoft-teams-webhook-url.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.
