Per-channel GitHub routing for Microsoft Teams

Send PR notifications to the right Microsoft Teams channel — automatically — by repo, label, branch, or author. No more one-firehose-per-channel.

Targeting: github channel notifications microsoft teams · 5-minute setup · Works alongside the official @github bot

One channel doesn't scale

The official GitHub Microsoft Teams app supports one notification firehose per channel. As soon as you have 3+ teams sharing one channel, every PR pings everyone — and the channel goes silent because everyone mutes it. Per-channel routing rules fix that by sending each PR only to the channel that actually cares.

How it works in Microsoft Teams

Connect your GitHub orgs and Microsoft Teams workspace from the dashboard.

Define routing rules: "PRs labeled `frontend` go to #ui-team", "PRs from author group `infra` go to #devops".

Layer rules: a single PR can hit multiple channels if it matches multiple rules.

Microsoft Teams channels stay focused — every notification is relevant to the team that owns the channel.

Why teams pick PullNotifier for this

Route by repo

Each repository can map to its own Microsoft Teams channel. The simplest setup that already beats the official app.

Route by label

Send `bug` PRs to #qa, `security` PRs to #sec, `docs` PRs to #docs — all from one configuration screen.

Route by author or team

PRs from the platform team route to #platform-prs. Junior engineers' PRs route to #mentorship-channel.

Route by branch

PRs targeting `main` go to the release channel. PRs targeting `dev` stay in the working channel.

Multi-channel mode

A single PR can post to multiple Microsoft Teams channels when it matches multiple rules.

No-config fallback

Anything that doesn't match a routing rule lands in your default channel. Nothing gets dropped.

How this compares to the official GitHub Microsoft Teams app

Capability

PullNotifier

Official @github

Per-repo routing to Microsoft Teams channels

—

Per-label routing

—

Per-author / team routing

—

Per-branch routing

—

Multi-channel mode for one PR

—

Related Microsoft Teams features

Personal Notifications User Mapping Daily PR Digest

Frequently asked

How do I route GitHub PRs to specific Microsoft Teams channels?

Open the PullNotifier dashboard and add a routing rule: select the GitHub trigger (repo, label, branch, or author) and the Microsoft Teams channel destination. Rules apply immediately.

Can one PR notify multiple Microsoft Teams channels?

Yes. Multi-channel mode sends a single PR to every Microsoft Teams channel whose routing rule matches.

What happens if a PR doesn't match any routing rule?

It lands in your default Microsoft Teams channel so nothing is dropped.

Does the official GitHub Microsoft Teams app support this?

No. The official app uses one subscription per channel with no filtering. Per-channel routing is a key reason teams switch to PullNotifier.