We just raised a $30M Series A: Read our story

Compare Microsoft Azure DevOps vs. TFS

You must select at least 2 products to compare!
Microsoft Azure DevOps Logo
53,739 views|45,173 comparisons
TFS Logo
Read 17 TFS reviews.
17,033 views|14,309 comparisons
Featured Review
Find out what your peers are saying about Microsoft Azure DevOps vs. TFS and other solutions. Updated: November 2021.
554,873 professionals have used our research since 2012.
Quotes From Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

"It is a really easy way to define all of the features that you need to deliver. You can link those features to epics and break them down into user stories. You can also assign the user stories into sprints for doing your product improvement planning.""The simplicity is very good and the customer experience is also great.""The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason.""One of the main features is the user interface is very good.""Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release.""We are able to generate many different types of reports from Azure.""Overall, so far we have no major issues to report.""It is a well-integrated product in terms of the development lifecycle."

More Microsoft Azure DevOps Pros »

"The most valuable feature is the backlog.""Basically, the capacity to construct various products is something I find handy.""The most valuable features are test case writing and bug tracking.""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.""I feel that the test plan and test tools are more manageable in TFS.""The most valuable feature is simplicity.""The interface is easy to navigate.""The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."

More TFS Pros »

"There are certain areas in Azure DevOps that are better in other products.""Definitely, there should be more integration between GitHub and Azure DevOps.""We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up.""The main issue that I have is the connection speed. Sometimes, the response is too slow. I am based in Taiwan, and I am not sure if it is because of broadband or something else. Its initial configuration is also a little bit difficult.""There are certain features, and reporting that can only be used in PowerBI, but not directly in DevOps.""We are currently in the process of moving all of our on-prem to the cloud platform. We are trying to make that move and host the majority of our DevOps services in the cloud because the cloud is where most of the things are going nowadays. However, the process of this transfer is not straightforward, and it could be a lot easier. Microsoft hasn't provided the maturity for migration tools. It could be a lot easier in that respect. I want to see them continue to advance the API capabilities. They could add some more robust functionality to the administrative layer within ADO services. There are a lot of configuration elements that you need to take care of at the organization level and the project configuration level from an administrative capacity. When you're dealing with process templates and things of that nature, you have to do them all manually. Being able to automate some of that using scripts or API functionality would be really nice.""The solution can improve by adding integration with on-premise tools. The only built-in repository options are GitHub and DevOps.""Not all companies use the same methodology which could limit the use of this solution."

More Microsoft Azure DevOps Cons »

"There should be management of the project built-in.""The reporting functionality is something that they should work on.""I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects.""The execution of test cases could stand improvement.""The interface can be improved and made more user-friendly.""It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies.""I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress.""The dashboard and the customization of dashboards is an area they have to work on."

More TFS Cons »

Pricing and Cost Advice
"It is a subscription model and I only pay for what I use.""The licensing costs are reasonable.""It is the least expensive product in this class.""Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective.""As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month.""We pay a monthly license for Microsoft Azure DevOps.""Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs.""The price is cheaper than Jira and some of the other competing tools."

More Microsoft Azure DevOps Pricing and Cost Advice »

"We pay subscription fees on a yearly basis and the price is reasonable.""I am not in a position to comment on the licensing terms, as we are talking about an enterprise arrangement.""I was working with the engineering team, and that was not under my umbrella. From what I can remember, its license was yearly. They had the licenses on a per-user basis, and they included MTM.""We are using the open-source version.""TFS is more competitively priced than some other solutions.""We pay for the license yearly.""The pricing is reasonable at this time.""The price of the solution is cheaper than other competitors and it is a per-user license."

More TFS Pricing and Cost Advice »

Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
554,873 professionals have used our research since 2012.
Answers from the Community
Netanya Carmi
author avatarKulbhushanMayer
Real User

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.

author avatarSameh-Hablas
Real User

Both, it depends on what you want to do with it and what is your technical environment. 

Questions from the Community
Top Answer: Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalable… more »
Top Answer: 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… more »
Top Answer: The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user.
Top Answer: Basically, the capacity to construct various products is something I find handy.
Top Answer: The overall ability in the Agile process has some room to improve, even though it is interconnected. When I worked on Jira, it had the capability of better linkage. When it comes to project… more »
Average Words per Review
Average Words per Review
Also Known As
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
Team Foundation Server
Learn More

Azure DevOps Services is a cloud service for collaborating on code development. It provides an integrated set of features that you access through your web browser or IDE client, including the following:

  • Git repositories for source control of your code.
  • Build and release management to support continuous integration and delivery of your apps.
  • Agile tools to support planning and tracking your work, code defects, and issues using Kanban and Scrum methods.
  • A variety of tools to test your apps, including manual/exploratory testing, load testing, and continuous testing.
  • Highly customizable dashboards for sharing progress and trends.
  • Built-in wiki for sharing information with your team.
Visual Studio Team Foundation Server (TFS) is the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution. TFS supports agile development practices, multiple IDEs and platforms locally or in the cloud and gives you the tools you need to effectively manage software development projects throughout the IT lifecycle.
Learn more about Microsoft Azure DevOps
Learn more about TFS
Sample Customers
Alaska Airlines, Iberia Airlines, Columbia, Skype
Vendex KBB IT Services, Info Support, Fujitsu Consulting, TCSC, Airways New Zealand, HP
Top Industries
Computer Software Company21%
Energy/Utilities Company19%
Financial Services Firm15%
Computer Software Company26%
Comms Service Provider18%
Financial Services Firm7%
Financial Services Firm34%
Computer Software Company16%
Manufacturing Company13%
Energy/Utilities Company8%
Computer Software Company28%
Comms Service Provider17%
Manufacturing Company7%
Company Size
Small Business33%
Midsize Enterprise21%
Large Enterprise46%
Small Business25%
Midsize Enterprise25%
Large Enterprise51%
Small Business12%
Midsize Enterprise26%
Large Enterprise62%
Find out what your peers are saying about Microsoft Azure DevOps vs. TFS and other solutions. Updated: November 2021.
554,873 professionals have used our research since 2012.

Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 69 reviews while TFS is ranked 5th in Application Lifecycle Management (ALM) Suites with 17 reviews. Microsoft Azure DevOps is rated 8.0, while TFS is rated 7.8. The top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". On the other hand, the top reviewer of TFS writes "Good traceability for managing workflows, but not flexible enough for agile environments". Microsoft Azure DevOps is most compared with Jira, GitLab, ServiceNow IT Business Management, Red Hat Ansible Automation Platform and Micro Focus ALM Quality Center, whereas TFS is most compared with Jira, Rally Software, Visual Studio Test Professional, Micro Focus ALM Quality Center and TestRail by Gurock. 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.