As for the why, we were originally using TFVC and the on-premise TFS implementation. Now we are on our way to eliminating TFVC, moving everything to fine-grained git repositories. Azure DevOps seemed the logical choice for a migration, as we didn't have to do everything at once, and the user experience remained similar to our on-premise solution.
As for features, we heavily use Azure DevOps Repos, Artifacts, and Pipelines. It allows us to fully automate everything, with Artifacts allowing us to consume services and libraries produced internally.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As for the why, we were originally using TFVC and the on-premise TFS implementation. Now we are on our way to eliminating TFVC, moving everything to fine-grained git repositories. Azure DevOps seemed the logical choice for a migration, as we didn't have to do everything at once, and the user experience remained similar to our on-premise solution.
As for features, we heavily use Azure DevOps Repos, Artifacts, and Pipelines. It allows us to fully automate everything, with Artifacts allowing us to consume services and libraries produced internally.