I decided to share my thoughts about the perfect combination of Azure DevOps services for an end-to-end Microsoft Fabric CI/CD story. Since the topic came up in a forum recently.
Before I go any further, I will explain what I mean by Azure Devops services. Even though a lot of people think of Azure DevOps as a service in reality Azure DevOps itself contains a collection of services by default. Including Azure Repos to manage Git repositories and Azure Pipelines to orchestrate deployments.
To manage expectations, this is post is aimed at those seeking the perfect combination of Azure DevOps services for an end-to-end Microsoft Fabric CI/CD story when working as part of a team.
Perfect combination of Azure DevOps services for an end-to-end Microsoft Fabric CI/CD story
In reality, to perform CI/CD with Microsoft Fabric you only need two of the default services. Azure Repos to store your underlying Git repository and Azure Pipelines to orchestrate the pipelines.
Some would say this is all you need for an end-to-end Microsoft Fabric CI/CD story. In reality, when looking to perform CI/CD independently this can be true.
However, when working as part of a team I personally think that the perfect combination of Azure DevOps services for an end-to-end Microsoft Fabric CI/CD story should contain at least four of the services in Azure DevOps. So that they work together to help you deliver your CI/CD story efficiently. As shown below.
Azure Boards
Ideally, you should be working with Azure Boards to define work items about what you are going to create and maintain in your repositories and pipelines. Which is essential. Especially when working on new Microsoft fabric developments in larger teams and/or larger organizations.
I personally think Azure Boards is a great way to manage working in an Agile related way. Because it has so many great features and introduces some interesting possibilities.
For example, you can become more efficient with your daily stand-ups by working with native dashboards in Azure DevOps. Allowing you to quickly go through outstanding tasks and reminding others of your sprint goal. By the way, I highly recommend adding the sprint goal extension if you intend to do this.
Because Azure Boards is integrated with Azure Repos you can link your work items to changes in your Git repository. Providing greater insight into why a change was performed in your Git repository.
In addition, you can report on your work items by adding analytic views as a source of your Power BI reports. Allowing you to view your work status inside Microsoft Fabric.
Basically, Azure Boards is very powerful. Which is why I recommend it as part of your Microsoft Fabric CI/CD story.
Azure Test Plans
In addition, I recommend managing your tests with Azure Test Plans. So that you can create your test cases directly in Azure DevOps instead of in spreadsheets. Which can avoid a lot of potential issues. Including multiple versions of the same spreadsheet.
Plus, it keeps your test cases closer to the work that is performed. Azure Test Plans also allows methods to automatically detect what work items to test as well. Which is ideal. Especially when looking to test new developments within Microsoft Fabric.
If you want to avoid multiple versions of your tests cases I recommend looking into it. I covered Azure Test Plans in a number of previous posts. Including one that covers Azure Test Plans jargon for Data Platform professionals.
Final thoughts about the perfect combination of Azure DevOps services
With the perfect combination of Azure DevOps services for an end-to-end Microsoft Fabric CI/CD story you can deliver efficient solutions in your environment. With that being said, I purposely added the term perfect to this post for a reason.
Striving for perfection is good. However, I am very aware that people work with alternative solutions to manage work items and tests. If this applies to you then you can apply your solution as a replacement for the necessary service to still deliver a fantastic CI/CD story.
Alternatively, you can look to migrate to the Azure DevOps alternative of course. Which can introduce advantages such as reduce costs and easier integration. Plus the opportunity to work with the Azure DevOps MCP server.
Anyway, I hope this helps others with your way of working.