We reviewed Microsoft Azure DevOps vs TFS according to our users’ review in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison results: Microsoft Azure DevOps is a more advanced solution than TFS. Regardless of the higher cost, it offers stronger capabilities, evolving features, and better support.
"Most of the features are very valuable for us, especially the source code control and task management."
"It's got something that you won't find in other products."
"My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good."
"The features that have a significant impact on us include CI/CD, where we have full integration with the source code repository and Azure Pipelines."
"It's a complete solution that has everything you need."
"Azure enables us to create a staging environment through to a production environment in an easier way and then get the code and run that."
"It is stable. I like Azure a lot. All our guys are Microsoft certified."
"The initial setup is quick and easy."
"Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code."
"Work item management integration with source control."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"The interface is good with TFS."
"It is a stable solution."
"Basically, the capacity to construct various products is something I find handy."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"When converting to DevOps, it was difficult to map."
"One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration."
"Azure has not yet advanced to the performance level of the other major competitors and is missing integration with important technologies."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"It's too technical sometimes because it's meant for network developers. The CI/CD pipelines are not very easy to manage because it requires a lot of input. So it could be easier to manage."
"Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves."
"The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
"There are many things that I cannot do, and I have a lot of bugs."
"TFS needs to be stable."
"Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements."
"TFS on-premise does not support integration with SharePoint Online."
"The user interface could be improved to make it simpler and increase usability."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"The price could be cheaper."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 126 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 93 reviews. Microsoft Azure DevOps is rated 8.2, while TFS is rated 8.0. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". Microsoft Azure DevOps is most compared with GitLab, Jira, Rally Software, ServiceNow Strategic Portfolio Management and OpenText ALM / Quality Center, whereas TFS is most compared with Jira, Rally Software, Visual Studio Test Professional, OpenText ALM / Quality Center and TestRail. See our Microsoft Azure DevOps vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very friendly user interface. I think TFS does have a few valuable features, though, such as its project management, which happens to not only include user stories, but task management as well. It would be good if TFS offered better integration for third-party tools like Jira. For my needs specifically, for example, I need to do a lot of manual tasks, and integration with SharePoint is not easy. Other than that, I consider the product to be pretty solid, stable, and also scalable, and haven’t experienced too many issues with it.
In contrast to TFS, Azure DevOps provides a seamless user experience that is not only consistent across Azure DevOps service, but is consistent across Azure DevOps server too. It also has great navigation and the user interface is responsive, helping employees focus better on their work. Azure also allows users to connect GitHub Enterprise with Azure Boards, with no disruption to other workflows.
While both Azure DevOps and TFS require SQL Server, Azure DevOps server can be hosted on virtual machines running on Azure. In turn, these support Azure SQL Databases give users superior backup and scaling options - and do so all without increased administrative costs that are usually tacked on to running such complex services. I also like that Azure DevOps has advanced search capabilities. For example, certain features allow information from different components of the product to be accessible from whichever parts users are working on. You can also expand the search box from the product header, which I find useful and a great addition to help improve navigation.
Conclusion:
Azure DevOps is a better match for me than TFS because it has several new features and more additional benefits than TFS can offer for my needs.
Hi @Netanya Carmi,
Both are good and in fact, TFS is now rebranded as Azure DevOps server.
Now the point is about your requirement, if your requirement is to work closely with Cloud Services Cloud Application and you are Ok to manage your code and CI/CD plans over the cloud platform then go for Azure DevOps whereas if you can't move the data to cloud use Azure DevOps Server.
But for such tools my first choice is Gitlab.
Rest you can call me at 9717996125 or drop me at kulbhushan.mayer@thinknyx.com to discuss further.
Both, it depends on what you want to do with it and what is your technical environment.