Microsoft Teams incoming webhook for GitHub (2026)

The classic Office 365 Connector incoming webhook retired on March 31, 2026. Today, the right path is a Power Automate Workflow URL — or skip the manual webhook plumbing entirely with a managed service.

Targeting: microsoft teams github webhook · Last updated 2026-05-02

Skip the manual setup

PullNotifier installs from Microsoft AppSource in 5 minutes — no YAML, no Power Automate flows.

Step-by-step

Create a Workflow that accepts an HTTP request

Open the Workflows app in Microsoft Teams → New flow → "Post to a channel when a webhook request is received". Pick the destination Microsoft Teams team and channel.

Save the flow and copy the generated webhook URL

After saving, the flow surfaces an HTTP POST URL. This is your modern Microsoft Teams incoming webhook URL — replacement for the retired O365 Connector URL.

https://prod-NN.westus.logic.azure.com/workflows/{guid}/triggers/manual/...

Add the URL to your GitHub repository as a webhook

In GitHub: Repo → Settings → Webhooks → Add webhook. Paste the Workflow URL as Payload URL. Pick application/json content type. Choose which GitHub events to send.

Format the payload as an Adaptive Card

GitHub sends raw event JSON. The Workflow needs a "Compose Adaptive Card" step before the Post action. Use our adaptive card template at /tools/microsoft-teams-pr-notification-template as a starting point.

Test with a sample PR

Open a test PR in GitHub. Watch the Microsoft Teams channel for the adaptive card. If nothing appears, check the GitHub webhook delivery log for HTTP errors and the Workflow run history for compose failures.

Why the old Office 365 Connector URL stopped working

Office 365 Connectors retired on March 31, 2026. URLs of the form `https://{tenant}.webhook.office.com/...` no longer accept incoming requests. Any GitHub webhook still pointing at one of those URLs is now silently failing. Migrate to a Power Automate Workflow URL or use a managed service.

Common pitfalls

GitHub webhook returns 200 but nothing appears in Teams: the Workflow received the request but the adaptive card compose step failed silently. Check the Workflow run history.
Adaptive card looks broken: Microsoft Teams supports up to Adaptive Card v1.5. Newer schema features won't render.
Mentions show as plain text: add a "msteams" entities array to the card with the mentioned user's AAD ID. Hard to do without a user mapping table.
Webhook URL leaked: rotate by editing the Workflow trigger, which generates a new URL. Update the GitHub webhook config.

Why most teams switch to a managed service

Managing webhooks per repo, per channel, per Microsoft Teams workspace becomes a part-time job at scale. Smart filtering, user mapping, code review reminders, and daily digests aren't in the box — you build them yourself. PullNotifier handles all of this with a single AppSource install.

Frequently asked

How do I send a GitHub webhook to Microsoft Teams in 2026?

Create a Workflow in the Microsoft Teams Workflows app, copy its HTTP URL, and add that URL as a GitHub repo webhook. Format the payload as an Adaptive Card v1.5 in the Workflow.

Is the old Office 365 Connector webhook URL still valid?

No. Office 365 Connector URLs retired on March 31, 2026. Migrate to a Power Automate Workflow URL or use a managed service.

Can I send GitHub webhooks directly to Microsoft Teams without Power Automate?

Microsoft Teams no longer accepts direct incoming webhooks since the O365 Connector retirement. The supported path is via Power Automate Workflow URLs.

How do I @mention someone in a GitHub-triggered Microsoft Teams card?

Add a "msteams" entities object to the adaptive card payload with the mentioned user's AAD ID. PullNotifier handles this automatically via GitHub-to-Teams user mapping.