Kevin Chant shares some thoughts:
In this post I want to share my thoughts about disabling classic pipelines in Azure DevOps. Which I know there are mixed feelings about.
In addition, I want to raise awareness that this is now possible. Due to the fact that towards the end of January Microsoft announced that you can now disable creation of classic pipelines in Azure DevOps.
In other words, you can now disable the use of the GUI-based Classic Editor and the Releases features in Azure Pipelines.
I agree with Kevin here: it’s generally time to bite the bullet on infrastructure as code if you haven’t already. We talk about it in the data platform context a lot (database schemas in source control, repeatable deployment processes, maintaining config files and applying them) and it matters just as much elsewhere.