Skip to main content
TrustRadius
Azure DevOps Server

Azure DevOps Server
Formerly Team Foundation Server

Overview

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

36 people also want pricing

Alternatives Pricing

What is Azure DevOps Services?

Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.

What is CircleCI?

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…

Return to navigation

Product Details

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Azure DevOps Server Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Reviewers rate Usability highest, with a score of 8.7.

The most common users of Azure DevOps Server are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(280)

Attribute Ratings

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Azure DevOps server is being utilized as a centralized tool for our organization's code & release management. All departments in the organization have their own repositories where they check-in their codes. Azure DevOps server along with GIT integration is serving as a central code repository for our organization. Also its widget integration and inbuilt templates to automate code build and release from almost any tech stack is worthy to have it as a DevOps tool.
  • Vast range of Template for Automated Build and Release Pipeline with option to have conditional triggers
  • Code repository mechanism is aligned with GIT which is a well known public repository system
  • Bug Management is also an integral feature of this tool
  • Dashboard creation option of Build and Release pipeline is also available
  • Can add more build templates for specific technology requirements
  • Can have more features in dashboards which can help dev teams stream line their tasks and priorities
  • Can have raise alarm feature in case of any sort of failure in devops pipeline execution
Azure DevOps is well suited if you have a big team that is collaborating their codes and need to have devops pipeline for all build and release work. Also since this tool provides bug management facility, you don't need to purchase any other tool for that purpose. Moreover if you have your infrastructure built over Azure cloud then this is a best match for your requirements as it integrates well with it.
  • Helped to achieve better code management
  • Helped to get rid of a separate bug management tool
  • Helped to build the devops pipeline within it hence removing need for separate devops tool
Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose and hence always need to be integrated with some other tool for achieving the target. While Azure DevOps integrates within itself all features and utilities required to deliver the code from developer machine to the production environment.
Azure DevOps server have a lot of inbuilt features which helps it to integrate with external tools. Also Azure market place provides an extensive list of custom-built solutions or widgets that can be plugged and play with your Azure DevOps Server environment. Using its API connectivity you can automate most of the manual tasks of monitoring the pipeline flow or code check-ins etc
Vaibhav Choksi | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Dell Technologies uses Team Foundation Server for managing multiple projects across the North America region and rolling out in all other regions. If you use Visual Studio for development, TFS, or its online equivalent VSTS, you can have a fairly seamless end-to-end integration. Out of the box, it provides code management, testing, work hierarchy in agile formats, automated build, and deployment.

Dell manages source code, project reporting, engineering progress tracking and release management for agile software development. Microsoft TFS is also leveraged by the Product Management group to define and manage product requirements and managing the technical backlog. TFS really makes it easier to perform an end-to-end integration, reporting, tracking, code management, automated build, and deployment, etc.
  • TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
  • It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
  • It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
  • TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
  • Development in branches is hard to achieve and TFS has a room for improvement.
  • Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
Team Foundation Server is well suited in product management
  • Easier to build a technical backlog.
  • Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
  • Make a Product Manger's and engineering teams' life easier in meeting and tracking.
  • Project managers can easily track the work and create reporting.
  • Positive ROI for Microsoft Product Suits since TFS easily integrates with other Microsoft Product lines.
  • ROI is negative where you find it difficult and spent more time to integrate with Non-Microsoft product lines.
  • TFS server could have negative ROI if the number of users is really limited. However, for larger organizations, it is worth investing in TFS.
TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a decision making process.
Microsoft for years has offered user-friendly products that people love to use at work and home. TFS provides a seamless integration with other Microsoft products that helps you improve ROI, save time and resources.
The usability of TFS is great and I would like to see an improved UI and seamless integration with non-Microsoft products.
Bill Starling | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Team Foundation Server is used by the entire company across the globe. Development uses it for obvious reasons in developing new software and fixing bugs that are found and logged into Team Foundation Server by our quality assurance analysts. Support uses Team Foundation Server to log issues from clients and professional services uses it to make minor changes while in the field with clients. Sales uses it to demonstrate new features to clients and to set up environments when holding trade shows.
  • Allows a great deal of history detail on every issue found or new feature added. It keeps a detailed history of any code changes by developers so you can always see who changed what portion or code.
  • You can adjust users permissions down to a group of users (i.e. testers vs. developers vs. managers) and can get very technical with permissions for each group. The permissions can also be set based on certain portions of the code base not just on the entire thing.
  • The information that is tracked is great. When you find an issue and you log it in Team Foundation Server you have many options for fields to utilize and edit to make sure you get the correct team of developers to look at it. You can also have different requirements for each issue or when checking in code such as changes made, priority level, area and iteration (these are used for internal development purposes usually).
  • Simplify the permissions interface and navigation. Permissions are great but sometimes finding the correct screen is difficult.
  • Make the interaction between different versions easier. Sometimes you can run into issues when trying to use an older Team Foundation Server server with a new Team Foundation Server Build server. This occurs when you don't have the resources to upgrade all servers at once.
This is more suited for a larger corporation or development team as the cost of acquiring the software/hardware might be too large for a smaller company. Setting it up can also be hard for a small team if there is no experience with it. Finding experience can be hard because of this fact but the Team Foundation Server wizards are generally helpful and provide adequate help in setup and administration.
  • Team Foundation Server significantly improved efficiency by allowing everything to be integrated which allows the global teams to work together on items.
  • We can provide better support to our clients because our support teams can use Team Foundation Server to log problems and to check on existing issues.
  • Fixing issues in development is easier to overcome since the history tracking is so thorough and detailed.
  • N/A
I have not used any other source control software.
Research and Development, Support, Professional Services, Legal, Sales, and Marketing.
5
Experience with Team Foundation Server is a plus but any source control software is preferred. Experience with SQL Server and other Microsoft products. Knowledge of source control practices and software configuration management ideas are required. Also use with virtualization and Hyper-V is useful along with knowledge of general IT infrastructure such as servers, virtual machines, networks, etc.
  • Test Cases and test plans
  • Development of new software
  • Change tracking
  • Creating client specific branches or patches.
  • Change tracking allowing for the rollback of specific changesets without having to rollback changes that were done afterwards. Can also do partial rollbacks.
  • Utilize some of the new features of the newer versions of TFS and have all TFS servers on the latest versions.
  • Integrate newly acquired software into existing Team Foundation Server servers and databases.
  • Implement a more concise permissions plan.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Not Sure
  • Product Features
  • Vendor Reputation
  • Existing Relationship with the Vendor
  • Positive Sales Experience with the Vendor
My company is a Gold Certified Microsoft Partner and as such we utilize most Microsoft products and they are typically the go-to for any of our software needs. Having this existing relationship helps whenever a new need arises as Microsoft develops most of their software with larger corporations in mind.
I doubt it would be changed as we utilize many other Microsoft products and the integration between all products is fairly seamless when using software from the same vendor.
  • Implemented in-house
  • Connectivity to all network servers
  • Correct configuration of servers
Do research beforehand and, if possible, do a trial run before implementing into production environment.
I have never used Team Foundation Server support from Microsoft. Finding help on the internet is quite simple if you know source control methodologies and terminology.
No
I have used Microsoft's Technet website to find a few answers to the Team Foundation Server issues I have come across. It is very easy to do a search on Google, Bing, etc. and find Technet results that typically answer the question.
  • Code check ins
  • Connecting to TFS servers
  • Editing projects
  • Editing user permissions
  • Setting up initial build definitions and configuring Build servers with correct software
  • Upgrading TFS server to new hardware using newer version of software.
Yes
It works rather well. The biggest issue with it is with the overly complex permissions. Instead of having permissions for each area of TFS in their own spot it would be nice to just have them on one 'page' and then divide them into tabs or something of that sort rather than entirely different sections of TFS (i.e. for test permissions you must go into test cases then security, for build permissions you must go into builds then security, etc)
The complex permissions drags it down for me and since I nothing is perfect I'm subtracting one point for the permissions from my original score of 9.
Return to navigation