Would you stick with Azure DevOps for a new DevOps setup?

November 16, 2026 5 answers
Asked by _gently!unboxed.5

The team already uses Azure DevOps for issues and repositories, but has little in place for infrastructure as code, CI/CD, or monitoring. Is there a good reason to move platforms before building that out, or would you stick with what is there?

Answers

b.461~parcelstencil

I would start with Azure DevOps unless you can point to a requirement it cannot meet. The team already has its code and work tracking there, so moving those adds work before you have even built the pipelines.

Try a small infrastructure as code project and a basic build and deployment pipeline. That should give you something concrete to evaluate rather than choosing based on reputation.

Reply to this answer
_p61!nodewhisk.4

GitHub is worth comparing, especially if the team wants its Actions ecosystem or prefers its code review workflow. But switching from Azure DevOps to GitHub is not a move away from Microsoft, so be clear about what problem the change solves.

Check how each option handles shared workflows, secrets, access controls, and the way your teams are organized. People disagree on which scales or manages those things better, so I would test your own requirements instead of assuming the newer option wins.

5j~claspwicket_714:

Familiarity matters too. An existing skill set with Actions could make a difference, but it still needs to be weighed against the migration work.

Reply to this answer
_z82+gaugeparcel.5

Keep as much operational logic as practical in the repository rather than embedding it all in platform-specific pipeline configuration. Tools such as Terraform, Ansible, or Python can do the work, while the platform handles things like credentials, scheduling, and artifacts.

That won't make a future migration effortless, but it can reduce how much of your deployment process needs to be rewritten.

Reply to this answer
7m~bytecaddy_483

There are conflicting views on where Microsoft is putting its effort. Some see more advanced features arriving in GitHub, while others expect Azure DevOps to keep receiving investment. I would not treat rumors about internal migrations as a roadmap.

If advanced security or scanning is a requirement, compare the current capabilities and costs directly before committing.

Reply to this answer
u.815!socketcanvas

GitLab is another option if the team is willing to consider a change outside Microsoft. If that is unlikely to get support, though, a detailed comparison may not be the best use of time right now.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions