Skip to main content
Azure DevOps Server

Azure DevOps Server
Formerly Team Foundation Server


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


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

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Azure DevOps Server, and make your voice heard!

Return to navigation


View all pricing

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


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

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

30 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 New Relic?

New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.

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 Ease of integration highest, with a score of 9.

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


View all alternatives
Return to navigation

Reviews and Ratings


Attribute Ratings


(1-25 of 47)
Companies can't remove reviews or game the system. Here's why
Anubhav Singhal | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
It is being used for complete ci/cd process, used to create pipelines and manage project with ado board.
  • Continuous integration
  • Continuous development
  • Project management
  • Ease of usage
  • More integration with open source
  • Navigation
It is well suited for creating build pipelines to automate the complete release process and to create testing pipelines. Create and assign different task on ado board. It is also used for code analysis by integrating it with sonar . But it is less user friendly then hira board to mage the scrum and kanban board
Score 8 out of 10
Vetted Review
Verified User
We use Azure DevOps to manage the end-to-end lifecycle of our code. We use Boards to capture our backlog and manage the work through delivery, Pipelines for our code repository, and Pipelines for CI/CD.
  • Azure Boards is fast to use once you have a good structure in place. You can create or modify each task type quickly. The consequence of that is that is it reduces your admin overhead so its a no-brainer to create lots of smaller tasks.
  • Azure Repos is simple to set up compared to other on prem solutions that we have used. Most options come out of the box including user management.
  • The Pipelines tool is very powerful, and you can quickly create your CI/CD pipelines. Simple to see the state of each pipeline at a glance.
  • Azure Boards can be daunting to set up. There are a lot of different features and if you don't know what you are doing it's easy to overcomplicate things.
  • If you have lots of similar Pipelines to create there is no way to template them, each one has to be created and managed separately. So if your target K8s cluster changes, you have to manually edit each Pipeline.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Melissa Bryant | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
The firm as a whole makes use of Azure DevOps Server for project management, with its efficient capability to prioritize and approve project needs. Our IT team uses this top-notch application to streamline project management tasks like code versioning and test script administration and to make sure all of our requirements are met through thorough testing.
  • Simple tracking of progress throughout the project.
  • Perform project management duties with superior ability to set priorities and approve work.
  • In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
  • It doesn't work well with tools from other companies.
  • Improvements can be made to the user interface to make it more natural to use.
  • I also think capacity planning may use some fine-tuning.
Integrating with Visual Studio makes it easy to see where things stand in terms of different projects' requirements, and the product is great for prioritizing and approving changes as they come up. An easy-to-use tracking and testing system ensures that all criteria are met, making this a great tool for project managers trying to keep their projects within their allotted parameters.
Score 7 out of 10
Vetted Review
Verified User
We work according to Agile methodology and Azure DevOps Server (formerly known as TMS) helps us to track and follow the progress of our work efficiently. We use it for version control as well as to review backlog. As we are more of a Microsoft-based company, it helps us a lot since all Microsoft products can be integrated effortlessly with Azure DevOps Server which enhances user experience.
  • You can integrate it effortlessly with almost all Microsoft products
  • Supports Agile and can be used for version control
  • Bug tracking
  • Ease of use
  • I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
  • The user interface could have been better
  • Agile boards can be better
Scenarios where Azure DevOps Server is well suited: When the other tools you need to use are also Microsoft products bug tracking version control (although GitHub is better) Agile management backlog management scenarios where Azure DevOps Server is not well suited: When you need to integrate services other than Microsoft owned.
Score 9 out of 10
Vetted Review
Verified User
Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments.
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.
  • Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
  • Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
  • Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
  • Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
Score 9 out of 10
Vetted Review
Verified User
I work with an agile development team and we use DevOps for capturing and managing user stories and bugs. User stories are categorised into Epics and Features with ease, and it's a very valuable tool for planning and resource management.
  • Resource management
  • Sprint planning
  • Organising requirements
  • Could use a more intuitive interface
  • On-screen demo/tips would be helpful for new users
DevOps is great for managing backlogs, requirements and resources. I don't have enough experience with this sort of software to comment on any downsides, my use is fairly limited but, it's great for my requirements.
Score 10 out of 10
Vetted Review
Verified User
Managing software development across several phases can be extremely difficult due two it’s complexity. DevOps and CI/CD can help to control this complexity. However, these methodologies need software solutions that suit this agile approach. In this case Microsoft DevOps is the best suite available at the moment. We use Microsoft DevOps end to end to manage the development of a cross-platform mobile application. As said we use the suite end to end. Starting with „Azure Boards“ to derive, document, and manage backlogs; „Azure Repos“ to manage repositories and changes/change requests; ending with automating testing and pipelines with „Azures Testing“ and „Azure Pipeline“. Integration and extensibility features are used for productivity purposes as well. In this way, Azure DevOps brings together all levels of information at code in one single tool. Especially the automation options in the pipeline Tier helped us to automate delivery processes for both platforms (iOS & Android).
  • Integration and Extensibility Features.
  • Pipeline automations.
  • Configuration and flow of change requests workflows.
  • Configuration of Boards (backlogs).
  • Flexibility and ease of use of dashboards.
  • Change logs of items.
  • Expand automation options for iOS pipeline (include further triggers).
  • Mass handling of backlog items could be improved.
The repro Feature “Azure Repros” was especially valuable in our use case as it was very easy to orchestrate the development of several developers via change requests. In this way, tasks/bugs execution was easy to plan and assign via boards and dashboards, and commits were documented in relation to planning objects and reviewed via the four-eye principle. Senior developers were able to oversee and review junior developers' work easily.
Score 8 out of 10
Vetted Review
Verified User
We leverage Azure DevOps to manage the Agile backlog of one of our biggest internal platforms. The main functionality is leveraged to track stories and move things along from requirement drafting, to design and right through the development and QA. Some other functionality that is leveraged is the calendar to ensure that we are capturing the agile team's OOOs since most of us are from various orgs/teams throughout the enterprise.
  • Organizes tasks with space for all the added context one would need (requirements, design links, etc.)
  • Ability to capture a backlog of items to better visualize a roadmap to help with planning/prioritizing.
  • Streamlines the work being done across a large project team with various specialists.
  • Intuitive to use with minimal learning curve for those new to the tool.
  • It is very utilitarian looking, maybe consider a more personable UI aesthetic
Our project team uses Azure DevOps to manage the epics and stories associated with one of our biggest internal enterprise-wide tools. It easily captures all stories in a simples way, creating room to include story points (for estimations), requirement notes, and design links (once ready). Additionally, it is simple to move tickets through the various stages of the process making it easy to tell the status of any given task - the ability to color-code tickets has made it exceptionally easy for me to locate the tickets specifically created for my design team to address.
Matthew Budram | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
One product to cover the most common engineering activities in tech irrespective of the domain. Whether the team is in medical tech, fintech, aerospace tech, or a business process outsourcing firm, this platform has all the common tools needed in an Agile workspace with extreme collaborations across DevOps, Product, and Engineering. This gives the best centralized toolset, especially if your organization is already a Microsoft-based firm.
  • Version control
  • Requirements definition
  • Secrets library management
  • Continuous integration and deployment
  • Wiki Markdown customization
  • Better Syntax Highlighter in Repository
  • Improvements in Requirements Definition Customization
In my capacity as an architect, the platform gives me the ability to define the architecture within a wiki. I can include details including flow, UML, and ER diagrams in the User Story of Features being defined by the Product Owner, and my engineering team can link the repository pull requests to the story being developed. My Product Owners can now view the business definitions, software architecture, code written, and QA tests performed all on one central platform.
Christopher Sawyer | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We are using Azure DevOps [(formerly Team Foundation Server)] in our IT department to help us with Agile software development. It helps us to track code changes with various work items like Tasks and Bugs. It also helps to test, build and deploy those changes to multiple environments. It easily integrates with Visual Studio to create a seamless experience.
  • All-in-one product (don't need a bunch of separate connected products)
  • Integrates easily with other Microsoft products
  • Can use git or its own version control with less steep learning curve
  • More stable than Atlassian products
  • No clear-cut way to track items in a release, especially if they are not code change related
  • Agile boards still lag behind Jira in terms of functionality
  • Bamboo and Confluence have nice features over DevOps Build and Sharepoint
More stable than Atlassian products but not quite as feature rich. I've supported both TFS (now Azure DevOps) and Atlassian products in the past. Nice to have an all-in-one stable suite but you may not have quite as many bells and whistles. I would choose less features over having to restart servers.
Mark Orlando | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
We use Azure DevOps to manage and store all our corporate source code and deploy our applications to a string of various environments from development to production. In addition, we use Azure DevOps on a daily basis to manage our agile-based projects. Azure DevOps is used to track and follow the progress of customer support tickets as well. Our business analysts use the Agile Project Management feature to log user stories.
  • Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
  • Our business analysts use its features to document and assign user stories for Agile-based projects.
  • Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
  • For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
  • Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
  • The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
Azure DevOps works great if you spend most of your day in Visual Studio. If you plan on using VS Code, then skip it because Azure DevOps doesn't really work with VS Code. VS Code works with Git. For project management, Azure Dev Ops is okay, but project managers need to provide their team with links to where things are. Additionally, you might be better off using OneNote to document requirements and simply add links to your user stories where developers and testers can read the stories. The Word-like editor in Azure DevOps is extremely primitive.
Ross Borissov | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Azure DevOps in our business unit as an end to end solution for our ALM / SDLC. We have several organizations with various projects, repos and pipelines. We are following Scaled Agile Framework (SAFe) which is well served by Azure DevOps backlog module. We are happy that we could back trace a cloud release through the pipelines back to the work items in the backlog.
  • End to end tracing of released artifacts
  • Scaled Agile Framework implementation with Azure DevOps backlog
  • Versatile and powerful pipelines as code
  • Ability to automatically link automated tests executions to Test Cases
  • A better file editor (like VS code) in the git repo UI
Well suited:
  • Large teams developing heterogeneous applications
  • Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
  • Company undergoes regular external audits of their SDLC practices
  • Comprehensive reporting is required
  • Pipeline templating is required
  • Many git repositories are needed having to link to a unified backlog
  • Access to backlog work items and reporting is required for business stakeholders
Jeffrey Staw | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
The biggest and best use of Azure DevOps Server (formerly Team Foundation Server) is the gathering and management of user stories for development, coupled with the other elements of information sharing and the metrics it can provide. The ability to track bugs, and the fixes to those bugs, and generally track the evolution of your agile development group is a major plus. While primarily focused on the development organization, Azure DevOps Server (formerly Team Foundation Server) is used by the lines of business by product owners and their associates.
  • User story management
  • Integrations with other products
  • Reporting
  • It does not necessarily play very well with non-Microsoft stacks
  • Upgrades have been cumbersome; however, with the cloud offering, that is mostly off the table as a major issue
  • Some of the search functionality is unclear and difficult to use
  • Could have more pre-built templates; it offers so much it can be challenging at times
If you are a large organization that needs structure, Azure DevOps Server (formerly Team Foundation Server) is a great place to go. It does really benefit from others that have experience with the tool--that is a major plus. Azure DevOps Server (formerly Team Foundation Server) is particularly well suited for organizations that are looking to become more agile in the way they do business, especially in the way they code.
April 14, 2021

Still TFS to Me

Jordan Comstock | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Our dev team uses [Azure DevOps Server] to receive requests for our site from all departments in the company. I have used it as a marketing user. It is being used across the entire organization. It helps to address the business problem of prioritizing the work that we need to be done on our website.
  • Orginazation
  • Notifications
  • Complex nesting of projects
  • So many options, getting the team on the same page
  • Formatting
  • Tricky for new users
We still call it TFS. It is very useful for our marketing team and working with our developers. Every time we have a page, a bug, a user story, or an epic project, we can put the details into [Azure DevOps Server] and work back and forth with our dev team in there to complete the work.
Score 10 out of 10
Vetted Review
Verified User
TFS is used for ALM of all in house supportive software, development of our flagship product and clinical studies for our latest version. TFS acts as a central hub for requirements, code, tests and reports. It links these facets of the product life cycle together.
  • Linking together all aspects of the application life cycle, from requirements to code to builds and test.
  • Trace-ability of all application life cycle via reports and queries.
  • Automated testing.
  • Flexibility of source code management. Centralized or distributed.
  • Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
  • Capacity planning could be improved.
  • Dot Net framework 260 character path limit is ridiculous.
Team Foundation Server (TFS) is best for large scale enterprise deployments. Not needed for a small company. With the infrastructure investment, TFS can aid large scale software development immensely. TFS is highly customizable, but if you go the route of heavy customization, don't upgrade to the latest version aggressively. Plan to invest in at least one full time TFS administrator. Make sure the users are properly trained.
Score 10 out of 10
Vetted Review
Verified User
Azure DevOps Server is being used across the organization as a defect/bug tracking system for IT projects similar to Jira. The business problems it addresses are mainly related to issue tracking and traceability. There is a multitude of IT deployments at our company, and hence, lots of QA/UAT testing. When defects are captured during these phases, they are logged in Azure DevOps Server and tracked.
  • Organization
  • Defect tracking
  • Severity
  • Escalation
  • Issue/user traceability
  • Easier interface.
  • Less drop downs and tabs.
  • Email notifications.
The best use for Azure DevOps Server is for issue tracking and reconciliation for defects during the QA process.
Score 8 out of 10
Vetted Review
Verified User
Our IT department uses Azure DevOps Server to manage all our projects and for software development.
  • Ease to manage code.
  • Compatible with several services.
  • Version control.
  • Need more templates.
  • Can be confusing to use at first.
  • Reporting could be better.
It is well suited for any IT team, provides a great way to manage and track projects. Great for code reviews and bug management.
Score 10 out of 10
Vetted Review
Verified User
I am currently using Azure DevOps Server with a client on a scrum project to build a business application. In the company, Azure DevOps Server is mostly used by our specific project but does have other users and different projects. It helps manage the scrum process and provides organization and clarity to a project with many moving parts and members.
  • Organization of tasks per team member
  • Statistics provider for data related to capacity and output
  • Good UX/UI experience for clarity
  • Copy/Paste functionality could be improved
  • Ability to see all team members more clear visually
  • Sort feature on columns could be better
Azure DevOps Server is a great tool for keeping large projects organized. It is well suited for building large, business applications that require a lot of organization and history of the project that is accessible.
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.
Score 7 out of 10
Vetted Review
Verified User
Source control for application code, for the most part. For database code, it integrates well with Red Gate software. Besides scripting out database schema, Red Gate will even script out static data so it can be source controlled as well within TFS/ADS. My previous employer used TFS/ADS to automate builds and as a ticketing system.
  • It allows you to view the history of any piece of code. Shows the differences. If you are a good 'code archaeologist' you can figure out why things were changed and when.
  • It provides a repository of your code so you can reconstruct it in case of a catastrophe. With code history, you can restore the code as it was before some change that didn't work, was made.
  • The tickets it creates can be linked to the changes in the code. This adds an important element showing causation. This code change resolves or is associated with this ticket which includes the purpose of the change.
  • The way it uses workspaces is non-intuitive. I required help from our resident expert to get TFS set up initially.
  • Don't forget to refresh again and again. Yes, of course, you want the latest changes - you shouldn't have to remember to keep hitting that button.
  • Even though it uses a Microsoft SQL Server database to store its data, it uses the database in a non-standard way. Don't try to do the usual MS SQL backups - let TFS handle the backups.
Git is very popular right now and can be used instead of TFS for source control, but TFS can integrate with Git. Git has more of a learning curve than TFS, IMO.
F A | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
It was used as an Application Lifecycle Management (ALM) system that takes care of all aspects of software development from planning, requirements gathering to coding, testing, deployment, and maintenance. Also as a Source Code Control(SCC), Bug Tracking, Project Management, and Team Collaboration platform.
SDLC Management (SDLC – Software Development Life Cycle):
  • Software Team Collaboration
  • Source Code Management
  • Supports Agile, Scrum, CMMI
  • Bug Tracking
  • Integrated Test Tools
  • Automated Builds
  • SDLC Management (SDLC – Software Development Life Cycle).
  • Software Team Collaboration.
  • Supports Agile, Scrum, CMMI.
  • Bug Tracking.
  • Reporting
  • Code integration
  • Project Management integrations
Team Foundation Server (TFS), provided by Microsoft, provides you a wide array of collaborative software development tools that integrate with your IDE providing secure version control, extensible integrations, agile tooling among many others. You can set up an on-premise version of TFS or you can sign up for Visual Studio Team Services which is backed by Microsoft Azure if you don’t want the hassle of managing the infrastructure.
Score 10 out of 10
Vetted Review
Verified User
Azure DevOps is being used by the entire company. We use that to build our build and release pipeline to continually release our deployment.
For our department, we build infrastructure with Terraform and deploy it to the Google Cloud Platform. It solves our problem of not having a CI/CD pipeline. It makes our development cycle much faster.
  • It is compatible with so many services. You can deploy to GCP, AWS, and with any kind of developing language.
  • It has a clear developing logic. You build first and then deploy things to the destination you want.
  • When you develop with Microsoft products, you can do a lot more.
  • There is a little window tells you small jokes and information. It just annoys me.
  • The UI might use more careful design. it can be confusing when you want to find the thing you want.
  • There are small things can be added to improve productivity, such as cloning the whole agent job.
For companies, especially big companies, when they adopt the way of CI/CD, they need a build pipeline to realize all these. Either they develop websites with languages like Python, Ruby, or C#, or they set up infrastructure with Terraform, Ansible, or Puppet. Azure DevOps integrates everything together and provides a solution that works with all the technologies you use.
Brendan McKenna | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use the Azure Dev Ops server throughout the IT department of our organization. It is utilized by Business Analysts, Scrum Masters, Developers, and QA. We have Git integration enabled and it has been an awesome experience with its integration to our source code. I especially love the built-in ability in the latest version to perform source code wide string searches. This makes it exceptionally easy to find code references and delve into new areas quickly. Aside from source control, it is our UI interface for all of our SCRUM project management needs. We create all of our tasks on the work items board and it makes it easy to see the progress of the overall team. Overall it's just been a great experience and I can't think of any complaints.
  • Git integration has been fantastic.
  • Provides a convenient UI for managing the SCRUM process.
  • Built-in Code Review feature and completion policies.
  • I wish I could default to a specific dashboard on load.
Great for source control, project management, and code reviews. It is really critical to put in place code review policies with required reviewers before a pull request can ever be merged into a target branch. As a senior developer sometimes I feel this can be cumbersome but there have been a few instances where I have caught a major error in a pull request and was able to prevent the code from being merged.
Score 8 out of 10
Vetted Review
Verified User
We have been using Azure as one of our cloud providers for a few months. Not all departments in my company are using it but a few of the critical applications that need multi-cloud for managing resilience are using it. How these departments use it is for an end to end infrastructure on the cloud and set up and launch an app in Azure.
  • Not only does it provide a way to manage your code, but you can also do most of the other activities such as planning for a release, planning test cycles and, in a sense, true product management
  • The reporting is great out of the gate. They will enable you to draw insights into how the teams are managing and pushing the changes to production.
  • It integrates pipeline and DevOps, making it true life cycle management.
  • Most of the companies use AWS, GitHub, etc. and generally the support on the internet is relatively less.
  • Being a Microsoft service, it works very well with Microsoft apps.
If you are using Azure as a cloud provider and want to build solid code management and overall software life cycle management, then azure DevOpsSserver is a great fit and should generally work. Also, the reporting features out of the box are really helpful and the higher management can get great visibility on how the code and product are being managed.
Score 9 out of 10
Vetted Review
Verified User
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.
Vaibhav Choksi | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
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.
Return to navigation