Home / Using Microsoft Teams as Your DevOps Hub


Microsoft Teams is the chat-centered workspace that provides instant access to everything needed for DevOps teamwork. It is that dedicated hub that brings your teams, conversations, content, and tools from across Azure DevOps, GitHub, and Office together into one place.

Task 1: Integrate Microsoft Teams with Azure DevOps and GitHub

  1. Launch Microsoft Teams - you can either open the web app or download the app to your desktop from here

  2. Azure DevOps Services integration with Microsoft Teams provides a comprehensive chat and collaborative experience across the development cycle. Follow the instructions here to integrate Teams with your Contoso-Air Azure DevOps project.

  3. Install and configure the Azure Pipelines app with Teams to monitor the events for your pipelines. Follow the instructions here to set up and manage subscriptions for releases, pending approvals, completed builds etc. and get notifications right into your Teams channel

  4. Install GitHub for Microsoft Teams application from Microsoft Teams App Store.

  5. Setup a tab for GitHub Pull requests in your Teams channel. While configuring the tab, select the repository for which you would like to pin the issues or pull requests view. Once the tab is pinned, everyone in the team can view the tab but only those who’ve access to the repository would be able to see the issues/pull requests content.

Task 2: Using Microsoft Teams as Your DevOps Hub

  1. Open the Conversations tab.

  2. You have subscribed to the updates from Azure DevOps for work items, build summary etc.. by installing Azure DevOps Services connector in the previous task.

  3. You should be able to see work item notifications as shown below.

  4. You can also manually link items from GitHub and Azure DevOps in conversation.

  5. Select the recently closed user story.

  6. Enter a message and press Enter to share with the team.

  7. Now everyone on the team can see the progress.

  8. Select the Pull requests tab which you have set up in the previous task. This provides a way to check in on GitHub pull requests without having to leave the context of other conversations and collaboration being done for this specific project.

  9. You can open pull requests directly from Teams. Click the newly created one to open it in a new browser tab. Close the tab when satisfied.

  10. Switch to the Stories Board tab. If you have not setup earlier follow the instructions here to bring in your team’s kanban board or favourite dashboard directly into Microsoft Teams. This provides interactive access to the Azure DevOps Kanban board directly from Microsoft Teams.

Task 3: Managing DevOps Processes from Microsoft Teams

Microsoft Teams is a great place to manage certain DevOps processes, such as approving deployments. To illustrate this, we’ll add a pre-deployment approval to the release pipeline and invoke it using the same GitHub pull request model as before.

  1. Navigate to the Azure DevOps browser tab.

  2. Select your Release pipeline. Select Edit | Edit pipeline.

  3. Click Pre-deployment conditions for Stage 1.

  4. Select the option to Enable the Pre-deployment approvals and add yourself as an approver.

  5. Click Save.

  6. Return to the GitHub browser tab. You need to make a minor change to the codebase so that you can create a pull request and generate an approval request.

  7. Select the Code tab in your repo.

  8. Click the Edit button to make a quick update to the readme.

  9. Make a minor change (such as adding a new line). Check Create a new branch and give it a name. Click Propose file change.

  10. Click Create pull request.

  11. Switch to Microsoft Teams now. There should be new conversation notifications for the commit and pull request as shown below.

  12. Return to GitHub and click Merge pull request.

  13. Click Confirm merge.

  14. Return to Microsoft Teams. When the release pipeline is ready to deploy, you will receive an approval notification in Teams. Click Approve to approve the release.

  15. Once the deployment succeeds, you will receive another notification of the success.