r/azuredevops • u/kantzkasper • Mar 14 '25
Why is Azure DevOps competing with GitHub?
First we heard moving from Azure DevOps to GitHub / GitHub Enterprise is the right direction as it's a matter of time before Microsoft will discontinue AzDO. Now we are seeing that they both are actively developing overlapping features with no end date in sight https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline? This causes a whole bunch of confusions in management decisions. Personally, I was hoping to see GitHub Actions will take over DevOps Pipelines and we will be done with nonsensical disparities in yaml configs once and for all..
12
u/JNikolaj Mar 14 '25
Our company had the same questions so we reached out to a few mvps and even product owners of DevOps / GitHub to get a better understanding of what was happening because we ( assumed ) DevOps was going to replaced by GitHub.
Anyway all of them told us there wasnāt any plans ( they were ) aware of to remove support for either one of them.
5
Mar 14 '25
Last information I have is that they even started reinvesting with it and itās going nowhere. I havenāt seen any enterprise use GitHub so I donāt see Microsoft pulling the plug unless there is a one on one migration to GitHub available
9
u/mycroft-holmie Mar 14 '25
Azure DevOps isn't going away any time soon. GitHub and AZDO will be running side by side easily for the next 5 years.
AZDO is definitely a mature product. It's targeted at the enterprise market. GitHub is *also* a relatively mature product but it's traditionally been aimed at a less enterprise-focused market. When I look at the release notes for Azure DevOps, I see efforts to *unify* the two rather than kick one or the other off the planet.
https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline
1
u/TrumpIsAFascistFuck Mar 15 '25
There's a fair bit of intentional effort to converge where possible, but not to the point of betraying the principles of the design. As a result the teams have often aligned on the same feature areas, solving the same problem domains together in parallel with collaboration and sharing ideas. Both products are better for it. But it is a shame we haven't seen more convergence. I remember when Microsoft bought GitHub, I was working at Microsoft on an internal product in our engineering systems space, and we were trying to figure out if we should pause our devops investments and pivot to GitHub or not.
11
u/moswald Staff Mar 14 '25
I shouldn't comment on the first few years of Microsoft's ownership of GitHub, but I can acknowledge the messaging has not always been entirely clear or perhaps accurate. However, I will say that nearly all of Microsoft's projects are hosted in Azure DevOps, and that is unlikely to change without some sort of fundamental paradigm shift in source control and product development. I expect to continue working on it until I retire, which I don't expect will be for over a decade.
4
u/piense Mar 14 '25
Yeahhhh. Someone made a comment shortly after the acquisition that sent our folks into some kind of kerfuffle. It was mildly entertaining. I got the GH pitch of āfeature parityā and said itād take them 10 years at a decent pace. Development on both platforms has been pretty minimal lately with GH seemingly spending all their money on AI. Few bug fixes and features Iād love to still see from Azure DevOps but having a platform that doesnāt release a shiny feature and break a few things with every release is a nice contrast to another vendor Iāve been dealing with. Bit silly for Microsoft to own GH and Azure DevOps but they bought GH for the market and itās still way behind Azure DevOps in a lot of areas important to enterprises. Now if either one would get a decent artifact hosting solution Iād be really happy.
2
u/moswald Staff Mar 16 '25
Development on both platforms has been pretty minimal lately
We're (AzDevOps) mostly focusing on more enterprise- and security-related features that aren't exactly flashy, but there are several new user features being added soon (including one for Boards that I'm super excited about).
Now if either one would get a decent artifact hosting solution Iād be really happy.
What don't you like about the artifact hosting in AzDevOps?
2
u/piense Mar 16 '25
Iāll have to go look at both of those again and give you a good answer. Off the top of my head ..
I vaguely recall the security stuff not working well for monorepos among other things. Think you all are still working on a lot of that.
Oh artifacts. Iirc the implementation was okish for NuGets for internal purposes. The processes around downloading and uploading for generic artifacts were no where near adaptable to our custom internal package formats, like I donāt even think thereās an official way to download them without the magic download task. Overall it was also very AzDO identity centric, like I donāt think theres a great path forward to distribute to customers straight from AzDO hosting short of giving them an account. More important for docker than NuGets for us. Those are my vague recollections, I can certainly go through and do a more detailed write up. We use a certain amphibious company for hosting ~40 TB of NuGets, maven, Conan, npm, docker and our custom generic one now (the bulk of that data), and honestly their architecture is okish but very much designed for on-prem and the darn thing is just super buggy, especially for NuGets.
Honestly I could talk your ear off on both topics and Iām sure you could get something formally setup through our reps. Especially for security AzDO is close but not there for us from what I recall last time and I think weāre still pondering it. Artifacts is further from the mark feature wise from what I recall but with the problems Iāve had with our current one I could make a case to switch if AzDO had one more architected to our needs.
1
u/piense Mar 16 '25
Though we also need a read through cache for our artifacts. I donāt think any incarnation of Azure Artifacts supports that, especially when using our own host names. With our current system we have a few points of presence both on prem and cloud hosted to accommodate our large build cluster and global developers - all using the same URL and auth today with a split horizon & geo dns setup to locate them. Works great when it works.
2
u/JellyfishLow4457 Feb 11 '26
Has that shift happened yet, u/moswald ?
2
u/moswald Staff Feb 11 '26
lol absolutely not. It's possible that our various git repos will someday be hosted by GitHub, but at this time, no. Everything is still on Azure DevOps.
--And even if Microsoft did move to using GitHub as the repo host, pipelines and tests and boards and ... will all still be within Azure DevOps.
6
u/Top_Violinist5861 Mar 15 '25
GitHub has some pretty massive weaknesses - user account management, a lack of repository grouping into say projects - which for me make it unsuitable for most organisations compared to Azure DevOps
1
u/LencoTB Mar 16 '25
Is anyone using AZDO for Boards and then using GitHub for everything code and deployment related? And how is it setup and does it work well for your team?
2
u/kantzkasper Mar 16 '25
This setup is familiar. It's for those who prefer structural hierarchies (epics -> features -> PBI and so on), states, iterations, tagging and various types of linking between the items and beyond. Board items can be linked with GitHub PRs such that merging the GitHub PRs change the states of items in similar was as it does with DevOps PRs.
GitHub has a flat hierarchy; everything is an issue where categorization is done using labels and templates with a very efficient filtering/searching facility.
I prefer the latter because it is succinct and efficient, there is not much to spend time wrapping your head around. From my viewpoint, people spend way too much time bickering about "the right" way of using DevOps Boards and dealing with its complexities / versatilities than it deserves (for what it brings to the table). YMMV!
2
u/Warm-Relation1458 Mar 08 '26
I have never seen this - if the company is using ADO for boards they use the ADO repos.
if they use Jira - they want to use Github.
I have seen Jira/Github and ado pipelines. which is the dumbest setup.
if you are a MS shop you get DevOps included, and you can remove a person using AD. Guthub, you have to manually remove them, and they can just use their personal accounts, which is not real secure.
3
u/1superheld Mar 14 '25
Eventually only one of the two will be the winner.
But first to preface, this most likely won't be in the next 5 (most likely not the next 10) years. At this moment there isn't any good reason to migrate to GH from ADO.
They are investing in both services, but both have a different focus, if you look at GH action runners and managed azure devops agents they run kn the same underlying infra/os options. Most investments in GH are either catch up (boards etc) and AI (all github copilot related features) while AD has more focused on stability and implementing highly requested features which are 'must have' to compete (this is based on what Microsoft thinks the market needs)
Looking at the appcenter deprecation, by far the easiest way was a export/import to azure devops.
GitHub advanced security scanning is available in azure devops and works quite well.
I would say they compliment eachother very will, remain with azure devops unless you have a very specific requirement. But create that github enterprise account and let users benefit from github copilot and friends.
3
u/MindlessPositive7298 Mar 15 '25
See the presentation below made at Ignite last Nov, basically enterprises love Azure Boards for project management, but devs love Github for repos and dev tools. Thus the products are slowly gaining interoperability where enterprises can have ADO boards but also have tight Github repo integration. Licensing is also being worked on so enterprises dont have to pay twice to get this ADO boards plus Github repos best of both worlds.
One just has to look at the Github Advanced Security Services that were also integrated into ADO to see when some of the interop already started happening in 2023.
2
u/nebinomicon Mar 15 '25
Microsoft product teams develop all types of overlapping stuff. Ideally the best products rise to the top and become really popular.
At some point when financial needs require a cut back on overhead or when some type of review takes place to drop unpopular/unprofitable products it will get cannibalized.
2
u/jba1224a Mar 15 '25
Ado is (currently) a better choice for enterprises.
I guess technically this is an opinion but itās about as close as objective fact as you can get. If the long term roadmap at Microsoft is to retire ado - they have a massive amount of work in setting up feature parity.
If Microsoft said tomorrow ADO was being retired in a year - enterprises would largely move to Atlassian, not GitHub - and thats why ADO isnāt going anywhere for a long long time.
1
u/Technical_Fee7337 Sep 10 '25
...what? I don't think u can have your source code and pipelines in Atlassian lol
1
u/jba1224a Sep 10 '25
Atlassian is a large company with a huge software suite?
Jira = workload management Butbucket = source code and pipelines
The integrated nature of ado (specifically with workload requirements) is why itās so good.
Atlassian is the only other enterprise level setup that has that.
1
u/Technical_Fee7337 Sep 10 '25
Afaik people use Jira for management, not many are using it for source code lol. And you mean "bitbucket"? GH has way more projects, including open sources projects. It has more AI supports for pipeline and code reviews. So I wouldn't bet on Atlassian. For developers who are using VScode (with copilot), I don't think they want to buy another license. Not to mention bitbucket is bad
1
u/jba1224a Sep 10 '25
So besides the fact that you necroed a post from like a year ago.
I think youāre missing the point.
Good vs bad is irrelevant - itās about what enterprises will buy and who has integrated āgood enoughā solutions.
Enterprises buy Microsoft, Atlassian, and Gitlab.
You can believe what you want but that doesnāt change the truth of the industry.
For what itās worth I agree, bitbucket sucks.
1
u/Technical_Fee7337 Sep 10 '25
The post was 6 months ago bro. So not that long ago. There is also GitHub Enterprise and at the conference I attended this year. Many companies use GitHub Enterprise for their frontend solutions including banks and big tech companies
1
u/jba1224a Sep 11 '25
Yes but none of this changes the point that GitHub was not (and is not) a feature pared competitor to ADO. GitHub enterprise is literally GitHub with a self hosted option.
I manage multiple enterprise GitHub implementations - many companies do use it.
Itās not remotely as feature rich as ADO nor does the tool serve the same purpose.
Like I said in another comment a GitHub is primarily a framework to visualize git version control with some other nice to haves (like package repos and container registries).
ADO is an enterprise software development suite that rolls source control, workload requirements, and cicd into same package.
Iām not sure what youāre trying to argue here, that people donāt use jira for source code? I never said they did.
1
u/Technical_Fee7337 Sep 11 '25
ADO is not a flagship product of Microsoft anymore. Their main focus is clearly CoreAI which GH is in it under the umbrella. ADO is just a cloud version of TFS. Microsoft itself has been actively promoting companies to migrate their source code over to GH if you haven't noticed. Their main idea is to have code on GH while ADO for planning but majority use Jira or Asana anyway. You can try to ask any AI model, they all think GH will be the winner if you have to pick between ADO vs GH and they also think GH will most likely survive rather than ADO. Truth hurts
1
u/Warm-Relation1458 Mar 08 '26
You are basing you argument on AI? seriously.
10 years from now both ADO and GH will be around. MS makes tons of money off each of them.
if they for ADO to move to GH, they company could just say Sorry we are going to Jira.
they will not give up the money
1
u/Warm-Relation1458 Mar 08 '26
Um you did when you forgot a comma
Jira = workload management Butbucket = source code and pipelines
2
1
u/Flip81 Mar 14 '25
What's frustrating for us though is not being able to use our azure devops subscription for copilot in vscode. It still requires a github account which our company doesn't have.
1
u/mr_eking Mar 14 '25
You mean GitHub Copilot requires a GitHub account? You don't say... :)
1
u/beth_maloney Mar 15 '25
To be fair GitHub advanced security is available in ADO so it's not that crazy.
1
u/esyekas Mar 15 '25
This is interesting discussion as we are using Github repos and ado pipeline as a best option. Whenever I think of migration and using single tool, I was hoping for ADO.
As it will be easy for migrating repos than pipelines.
However GitHub has a lot of features than ADO. Any thoughts?
1
u/Warm-Relation1458 Mar 08 '26
Sorry late to the game, GH have a lot LESS features that ADO. The only think give hub give you is a repo and an issue board, the ADO repos and boards are far superior. Both repos reside in the Github backbone.
1
u/Diligent-Method-785 Mar 15 '25
The most likely situation is these two products would merge overtime. Already there is some licensing merge where GitHub enterprise comes with a level of ADO for free. I think there is a pretty good cases to be made that if the licensing makes sense these are complementary products. One huge mess though is the RBAC and user account management in GitHub repos.
1
u/MingZh Mar 24 '25
The two platforms have different points of focus. Azure DevOps has been a staple for enterprise-level DevOps workflows, offering comprehensive tools like Azure Boards, Pipelines, Repos, and Test Plans. GitHub, on the other hand, has been the go-to platform for developers, especially for open-source projects, with its focus on collaboration and version control.
Until Microsoft provides clearer guidance, the decision between Azure DevOps and GitHub will depend on your organization's specific needs and priorities.
1
u/thinkriver Jun 05 '25
I think these two will eventually become one, Microsoft can call it Azure GitOps :-)
1
u/jobou363 Aug 12 '25
I don't think they merge rigth now but i found it hard to choose one of the products because github is more advance with AI and AI intƩgration and azure devops is a lot more advanced in "devops" and software deployment pipeline than Git hub action.
I see in the Q4 2025 they plan to intƩgrate github copilot agent in Azure devops.
1
u/Professional_Bad1331 Sep 19 '25
Do you have any source for the information about Q4 2025 devops agent? Would be awesome because I was thinking of moving to github just because of the advance with AI.
1
u/jobou363 Oct 05 '25
After looking into the roadmap ( i found a task for copilot but for the board) and seeing this post i paste at the end I don't think that the agentic task is planned for now i don't see it.
Here is the answer from the team, looks like they think and want to do things but nothing is well defined :
https://github.com/orgs/community/discussions/165681
I found it strange that the GitHub team tells users to move to github to use the agent.
I have used a GitHub agent locally and for now I'm not sure that i really need to have an agent running in the cloud and doing tasks.
I prefer to run it locally and see what he does and adjust the task.
I'm not sure anymore that a github copilot will be the choice to use in the future.
The space is growing fast and new products are built I will give a try to augment code.
I think for now i will wait to migrate my git to azure devops.
https://developer.microsoft.com/blog/azure-devops-with-github-repositories-your-path-to-agentic-ai
1
u/bherasgd Mar 07 '26
would like to know the latest stats and key differences between both tools ? Enterprise are being asked to move to GitHub from ADO and ADO does support pretty good D365 pipeline support
1
u/Warm-Relation1458 Mar 08 '26
ADO have way more features an better UI - I use both system daily and always dread doing stuff in GH
1
u/bherasgd Mar 08 '26
Thanks Mate. What should be the points or features we should keep in mind especially for presale purposes? What should be rational if any organization is asking to migrate from ADO to GH? Sorry about creepy questions š
1
u/AccomplishedDemand61 Mar 15 '25 edited Mar 15 '25
The irony is not lost on me that github sales pitch was very convincing for some and some are finally realizing they now pay for two platforms in the same space owned by the same company. And pay more for the more trendy of the two. And now have fragmented processes in two platforms.
Microsoft never, ever, said Azure DevOps was going away in fact they often repeated that message. The only people saying that it were github sales reps eagar to sell more github.Ā
Having managed Azure DevOps environments with user bases of thousands it is still far superior to github in many ways and Microsoft has owned gh for a long time now.
GitHub was popular because it was free not because it was necessarily better. It was a savvy purchase for Microsoft to grab market share.
Imho adding more gh integrations into Azure DevOps makes it worse and only causes further fragmentation which helps no one. It doesn't make it better.
0
Mar 15 '25
[deleted]
2
u/LencoTB Mar 16 '25
I never quite understood what the federated workload credentials are. We are currently using Service Connection in AZDO. And you are saying that GitHub pipelines do not have approval gates like when deploying to PROD for instance?
0
Mar 16 '25
[deleted]
1
u/LencoTB Mar 16 '25
Thank you for the detailed explanation. We have been using Sevice Connection in AZDO for years now so I guess our organisation Admin have not set any policies to have them expire. We have everything in Azure so Bicep deployments in AZDO pipelines use the Service Connection to connect to KeyVault and get the secrets in a pipeline Task and then use them for subsequent Task for Bicep deployment. This all works fluently without much consideration about security and federated workload credentials. But maybe I have to start looking into that.
So for GitHub Actions it is not possible to connect to an Azure KeyVault and download the secrets and use these secrets in subsequent Actions to do the rest of deployment stuff? That would be a major blocker for our team if we consider to move code and deployment to GitHub.
26
u/mr_eking Mar 14 '25
Well, Azure DevOps predates GitHub by a few years (it used to be called Team Foundation Server), and has been entrenched in enterprise environments for quite a long time. It had been in use for over a decade by the time Microsoft acquired GitHub.
For those enterprises that use it successfully, there's not much reason to switch to GitHub. If it ain't broke, why fix it? Microsoft knows that, and continues to support and enhance a product that many of its customers want.
Of course, there is quite a bit of overlap in functionality between the two products, so Microsoft may decide some day to shut one of them down. And if they did that, it's quite likely to be GitHub that survives.