Teams integration
Configure integration between GitHub or Azure DevOps and Microsoft Teams
What it is for
Bringing events into the channel where the team already is, so nobody has to remember to check a portal. Azure DevOps offers apps for Azure Pipelines, Azure Boards and Azure Repos; GitHub has its own Teams app.
Choosing what to surface
The same rule as notifications: post what requires a decision or an action.
| Post | Not |
|---|---|
| Deployment awaiting approval | Every successful build |
Build broken on main | Every push |
| Pull request needing review | Every comment |
A channel that receives every event becomes a channel nobody reads — and the approval that needed attention is lost in it.
Approvals in the channel
Pipeline approvals can be actioned from Teams, which shortens the wait for a release gate. Worth being clear about what that changes and what it does not: the approval is still governed by the check on the environment, configured by the resource owner. Teams is a more convenient surface for the same control, not a way around it.
Scope
Connect specific projects and pipelines rather than everything. A channel subscribed to an entire organisation is the noisy failure mode again, arriving by a different route.
Primary sources