Another big difference between Git and TFVC is when it comes to handling changes. This is connected to the fact that TFVC uses a central repository and Git is, by its nature, distributed. TFVC, with its central server, keeps all the files in a project under a single root path. Within this context, it is possible to apply permissions at a file level or lock files on the central server. By default, this is not possible with Git or with the basic GitLab configuration since there is no central place where you can enforce these authorizations. You can lock files somewhere, but a developer can happily continue developing locally and change code.

On the other hand, with Git, you can have multiple repositories in a GitLab project and have protection on a branch level or repository level. You have the option to define multiple remotes to which you can push code. This means that you can store code in GitLab and also on Windows Azure. The following screenshot shows the menu that you can use to lock a file in TFVC:

With TFVC, the files are all under one path and under control while in Git, there can be many branches and files spread over different remote servers. It's hard, if not impossible, to enforce centralized control.