Great job! Reason 11 in my own opinion: Azure DevOps Service is a SaaS meaning that we do not need to manage the infrastructure, setup and patching! :)
That's a very good point. I thought of putting that into the list as well, but there are since there are some other tools offered in SaaS (even though not many) I decided to consider other points which are more unique in Azure DevOps
It was announced during the Build conference prior to the release of the video. Keep in mind that the video is almost 2 years old, so many things have changed since then. As a former Microsoft employee, I can tell you than more and more companies are switching over from Azure DevOps to GitHub, and lately with all the new features in GitHub Actions they are also moving from Azure Pipelines to Actions.
I have used Jira only marginally with some clients, I don't have an extensive personal experience with it. I know they work differently, both are pretty customizable but in their own ways so if you are used to one it may be difficult adapting to the other one. I also know that most of the time Jira is loved by PMs but hated by the development teams, while Azure Boards is liked by both when they get to understand it better. :) One thing I'm pretty sure Jira lets you do it while it is not present in Azure Boards is controlling who can change the state of a work item. For example, you can specify that only a certain user or team can move a Task from "Doing" to "Done". This is not present OOB in Azure DevOps because of a different philosophy in the tool (collaboration over control)
HI. Unfortunately I've never worked with GCP so I do not know their products. Azure DevOps, however, is a different product from AWS DevOps. AWS DevOps is a set of tool to manage, deploy, and monitor AWS services, and as such works only with AWS Azure DevOps instead, despite the name, is not tied to Azure in the sense that is a proper DevOps suite that works with any cloud or on-prem environment.
