---
title: Azure DevOps
description: "[Azure DevOps](https://dev.azure.com/) will be the service we will use for source control. Microsoft Dynamics 365 for Finance and Operations supports TFVC out of the box as its version-control system. But Azure DevOps does not only offer a source control tool.…"
url: "https://ariste.info/dynamics365almguide/azure-devopsen/"
updated: "2024-08-25"
category: "Legacy Guide / Dynamics 365 for Finance & Operations & Azure DevOps"
---

# Azure DevOps

[Azure DevOps](https://dev.azure.com/) will be the service we will use for source control. Microsoft Dynamics 365 for Finance and Operations supports TFVC out of the box as its version-control system.

But Azure DevOps does not only offer a source control tool. Of course, developers will be the most benefited of using it, but from project management to the functional team and customers, everybody can be involved in using Azure DevOps. [BPM](https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/bpm-overview?WT.mc_id=BA-MVP-5003976) synchronization and task creation, team planning, source control, automated builds and [releases](http://ariste.info/en/2019/02/setting-up-release-pipeline-in-azure-devops-for-dynamics-365-for-finance-and-operations/), are some of the tools it offers. All these changes will need some learning from the team, but in the short-term all of this will help to better manage implementations.

As I said it looks like the technical team is the most affected by the addition of source control to Visual Studio, but it’s the most benefited too…

#### Subscribe!

Receive an email when a new post is published