How to integrate GitHub with Microsoft Teams (2026 guide)

The 5 integration options compared

Office 365 Connectors retired on March 31, 2026. The five remaining options for sending GitHub events to Microsoft Teams are: the official @github bot, PullNotifier, Power Automate Workflows, custom GitHub Actions, and direct webhooks. Each has a different trade-off between setup time, maintenance burden, and feature depth.

1. Official @github bot

The official GitHub for Microsoft Teams app is free, supported by Microsoft and GitHub, and works for basic notifications.

Setup:

• Open Microsoft Teams → Apps → search "GitHub" → Add
• Run @github subscribe owner/repo in the channel
• Authorise on GitHub when prompted

Best for:

One team, one channel, one repo. Free tier of GitHub events without smart filtering.

2. PullNotifier (recommended for engineering teams)

PullNotifier is purpose-built for engineering teams that need per-channel routing, smart filtering, code review reminders, daily digests, and GitHub-to-Microsoft-Teams user mapping.

Setup:

• Install PullNotifier from Microsoft AppSource
• Sign in with GitHub
• Map repos to Microsoft Teams channels in the dashboard

Best for:

Engineering teams with 2+ teams, multi-channel routing, or compliance requirements. Also: anyone migrating off retired Office 365 Connectors.

3. Power Automate Workflows (Microsoft's official replacement for O365 Connectors)

Microsoft recommends Power Automate Workflows as the official Office 365 Connectors replacement. The Workflows app inside Microsoft Teams provides templates for posting GitHub events.

Setup:

• Open the Workflows app in Microsoft Teams
• Pick a GitHub template (or build a custom flow)
• Configure GitHub auth + Microsoft Teams channel
• Repeat per repo + per channel

Best for:

Power Platform-heavy organisations that already have Flow expertise and want to keep all automation in one place. Maintenance burden is real — every flow is your responsibility.

4. GitHub Actions (DIY YAML)

Several open-source GitHub Actions exist for posting Microsoft Teams notifications. Add the action to your workflow YAML, set a webhook URL secret, and the action sends a card on configured events.

Note:

After Office 365 Connectors retired, many of these Actions broke or required webhook URL migration to Power Automate Workflows. Maintenance burden grows with repo count.

5. Custom webhook (advanced)

Build your own webhook handler that receives GitHub events and posts adaptive cards to Microsoft Teams. Maximum flexibility, maximum maintenance. Worth it only if you have very specific custom logic that no commercial tool provides.

Which one should you pick?

• 1 team, 1 channel, 1 repo, want free: Official @github bot.
• 2+ engineering teams, need routing / filtering / mentions: PullNotifier.
• Heavy Power Platform tenant, must use Microsoft tools only: Power Automate Workflows.
• Migrating from retired Office 365 Connectors: PullNotifier (5 min) or Power Automate (30+ min per repo).
• Highly custom logic, willing to maintain code: GitHub Actions or custom webhook.