How to get GitHub notifications in Microsoft Teams

Updated August 2026 · 5 min read

If your organization runs on Teams, routing GitHub activity into a channel seems like the obvious move. There are three realistic ways to do it — and one important caveat about what Teams integrations can't do for you as an individual developer.

Method 1: The official GitHub app for Teams

GitHub maintains an official Microsoft Teams integration, available from the Teams App Store (search "GitHub"). After an admin approves it, you can subscribe channels to repositories with:

The bot then posts pull requests, issues, commits and releases into the channel, with interactive cards for reviews and CI status.

The catch: it needs admin approval in most organizations, which can take weeks or never happen. And like its Slack sibling, it's team-level by design — everyone in the channel sees everything, and per-person filtering ("only my PRs") isn't really available.

Method 2: Webhooks into a channel via Power Automate or Workflows

If the official app is blocked, the common workaround is a repository webhook piped through Microsoft's automation layer:

• Create a Workflows flow (or Power Automate) triggered by an HTTP request, and paste its URL into the repo's Settings → Webhooks.
• Use the workflow to reshape GitHub's JSON payload into a message card and post it to the channel via the Teams connector.
• Add conditions in the workflow to filter by branch, label or author.

The catch: this is real plumbing. You own the code, error handling, and what breaks when either API changes payload formats. Power Automate also has licensing tiers that matter at volume — check before wiring a busy repo into it.

Method 3: Email-to-channel digests (low effort, low fidelity)

You can forward GitHub email notifications into a channel using a shared mailbox plus a connector, giving the team a daily digest of activity. The catch: it's delayed, unstructured and easy to ignore — fine for awareness, useless for "someone needs to review my PR right now."

The honest question: do you actually want them in Teams?

Most people searching this are trying to solve one problem: not missing the PR that needs them. A team channel is where the org communicates — but your review requests, @mentions and CI failures on your branches are personal signal, and they drown fast between deploy notices and channel chatter. No Teams integration fixes that, because the channel is shared by definition.

If you're on macOS, there's a more direct route: a menu bar app that keeps your personal unread GitHub count next to the clock all day. You glance, you click, you're in the exact PR or issue. Everything stays local on your machine — no admin approval, no webhook plumbing, no noise from anyone else's repos.

Which should you pick?

• Team visibility, and admins will approve it? Method 1 — the official app.
• Custom routing and you enjoy maintaining it? Method 2 — webhooks.
• Rough daily awareness only? Method 3 — email digest.
• Your own must-not-miss signal? Skip the channel entirely — use a menu bar app like DevNotify.