source is the future
It’s no secret that Microsoft’s attention is currently primarily focused on GitHub. As a result, a lot of features that were once unique to Azure DevOps, like workflow management and test plans, are being added to GitHub as well. That means it’s likely that we’ll move to a one-tool solution in the near future. Since recently, GitHub even has its own powerful editor, GitHub Codespaces, enabling developers to write code live in the cloud. For people who are used to working in Visual Studio Code, the lay-out will be immediately familiar.
All of which is to say that, even if Azure DevOps is the best fit for your organization right now and you want to keep getting value out of your current investment, keeping a close eye on GitHub is always a good idea. Not only does the tool come with a lot of advantages, it’s also the place where innovation is happening. Where possible, allow your teams to experiment and learn with GitHub. Think of it as an electric car: the diesel version will still get you from A to B reliably, but sooner or later you’ll probably have to make the switch either way.
However, a full phase-out of Azure DevOps seems unlikely in the short term. Microsoft has a solid track record of continuing to support its older solutions. Given Azure DevOps merits and the amount of users that continue to rely on it, both slutions are likely to coexist for many years to come.