Skip to content

Latest commit

 

History

History
88 lines (47 loc) · 4.13 KB

day.79.AZDO-Teams-Integrate-Pt2.md

File metadata and controls

88 lines (47 loc) · 4.13 KB

Day 79 - Azure DevOps Integration with Microsoft Teams - Part 2

In Day 78, we discussed Azure DevOps integration with Microsoft Teams, adding a tab to display backlogs in Azure Boards. But yesterday, we only scratched the surface, as integration between Teams and any of the components within Azure DevOps is possible. Today, in the second installment of a 3-part mini-series, we are going to continue exploration of Azure DevOps integration with Teams.

Previous installments: Day 78 - Azure DevOps Integration with Microsoft Teams - Part 1


SPONSOR: Need to stop and start your development VMs on a schedule? The Azure Resource Scheduler let's you schedule up to 10 Azure VMs for FREE! Learn more HERE


By clicking the ellipsis (...) by the team, shown in Figure 1...

001

Figure 1. Manage Apps link in Teams

I added another Tab with a view of this dashboard of my work in a particular project within Azure Devops.

009

Figure 2. Azure DevOps Project Dashboard (Teams tab)

I'll then select Azure DevOps from the list of apps added to Teams, which includes App DevOps that I added yesterday in Day 78.

002

Figure 3. Select organization in Azure DevOps

Clicking on the app, I'll add a new Azure DevOps component - Azure Pipelines!

003

Figure 4. App selection dialog

You'll get a splash screen with a description of some of Azure Pipelines features available in Teams. (I'll show you how to get the detailed info from the Teams chat interface near the end of this installment)

004

Figure 5. Azure Pipelines integration screen

Next, you'll get the consent dialog, granting consent for Azure Pipelines / Teams integration. The list of permissions in the consent dialog gives you more insight, but this isn't what I am talking about.

005

Figure 6. Consent dialog for Azure Pipelines integration with Teams

Then, we'll pick the Organization and Project we want to target in Azure Pipelines.

006

Figure 7. Select organization for Azure Pipelines integration

Clicking the Azure Pipelines icon below the chat interface reveals a search feature for pipelines and releases.

007

Figure 8. Search releases in Azure Pipelines from Teams

From the search box at the top of the Teams client, you'll see I can also query release info from Azure Pipelines.

010

Figure 9. Release search from Teams

If I type @Azure, Teams shows me the full list of bot integrations I can use to enable Azure DevOps notifications, workflow, and management capabilities, directly from Teams. Notice you see Azure DevOps, Boards, Pipelines, and Repos!

011

Figure 10. Querying the full range of Azure DevOps integrations

And when I add Azure Pipelines to the channel, Teams returns the following message...

👋 "Hi! Let's start monitoring your pipelines Subscribe to one or more pipelines or all pipelines in a project with: @Azure Pipelines subscribe [pipeline url/ project url] To see what else you can do, type @Azure Pipelines help To know more see documentation."

AND the guidance on how to use chat to subscribe to pipeline notifications, and add or remove subscriptions for this channel. It's great to bring targeted notifications to the interface where the team collaborates, rather than adding to the flood of email overwhelming my inbox.

012

Figure 11. Azure Pipelines integration capabilities (Bot)

Conclusion

As you can see, Teams can really enhance the DevOps experience for your Infrastructure-as-Code life, reducing your context switching between apps and portals and other tools. Tomorrow, we'll wrap up this mini-series with a look at integration with Azure Repos I think you'll find handy.