> 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/update-a-microsoft-teams-legacy-webhook-to-use-workflows.md).
# Update a Microsoft Teams Legacy Webhook to Use Workflows
*Applies to: Patch My PC Publisher V2.x*
## Overview
Older Office 365 connectors previously used for Microsoft Teams webhooks are deprecated. Microsoft announced the retirement of these connectors. For more information, see [Retirement of Office 365 connectors within Microsoft Teams on the Microsoft Developer](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) blog.
Microsoft Teams Workflows use the Adaptive Message Card format. Legacy Microsoft Teams webhooks created in earlier versions of the Publisher use the older Message Card format.
It is recommended that any webhook configured in the Publisher using the **MSTeams** message system be updated to use **MSTeamsWorkflow**.
## Update an Existing Webhook
1. Create a new Microsoft Teams workflow webhook URL by following the steps in [Create a Microsoft Teams Webhook URL](/patch-my-pc-publisher/administration/alerts/webhook-notifications/create-a-microsoft-teams-webhook-url.md).
2. In the Publisher, navigate to Alerts and expand Webhook Notifications.
3. Select the existing webhook that uses the Microsoft Teams legacy provider and click Edit.
4. Change the Webhook Provider from **Microsoft Teams (Legacy Webhook)** to **Microsoft Teams Workflow**.
1. Replace the existing Webhook URL with the new workflow webhook URL.
2. Click OK, then click Apply to save the changes.
After completing these steps, the webhook uses the modern Microsoft Teams Workflow model and sends notifications using the Adaptive Message Card format.
---
# 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/update-a-microsoft-teams-legacy-webhook-to-use-workflows.md?ask=&goal=
```
`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.