Announcing the Azure Pipelines app for Microsoft Teams

Karthik RG


As developers, we spend considerable time and energy on monitoring builds and releases. To help us be more efficient, we are excited to announce the availability of the Azure Pipelines app for Microsoft Teams. If you use Microsoft Teams, you can now set up subscriptions to receive notifications for completed builds, releases, pending approvals and much more in your channels. You can also approve releases from within your channel.

For details, please take a look at the documentation here.

To install the app, click here.

We will be continuously improving the app. Please give the app a try and send us your feedback using the ‘@azure pipelines feedback’ command in the app or on Developer Community.

Karthik RG
Karthik RG

Program Manager, Azure DevOps

Follow Karthik   


    • Karthik RG
      Karthik RG


      Currently we do not have immdediate plans of supporting this for TFS. You can use the existing ‘Team Foundation Server’ app in Microsoft Teams market place instead.

  • Avatar
    Daniel Strommen

    Our agile feature team has lots of small PR’s and CI releases happening on a regular basis.  We would love to get notifications about these, but AZDO creates a brand new conversation for each one so the net effect is that your team channel just gets spammed with AZDO updates, and you can’t see at a glance what is closed and what is not.  It was too spammy, we had to disable it.
    PR notifications should reply on their own thread when there is an update about the same PR.  Same for releases.  Also, the connector should update the subject of the thread with a status emoji so you can more easily see what the latest status of the PR or release is.

  • Avatar
    Andrew Fisher

    The workflow for these and the UI is not great to say the least, subscribe to something and it subscribes to all alerts. Go and edit the alert to reduce scope, for just failed builds for example, and all it does it create a new alert for that scope. Ended up deleting them all from within ADO because that UI in teams was poor also and setting up using the connectors on the channel instead

Leave a comment