A typical scenario for users of VSTS (Visual Studio Team Services, formerly Visual Studio Online) need free access to external users. For example, a company that hires vendors for outsourced software development needs to grant access to teams in the supplier who will act in the projects stored in your VSTS.
VSTS allows this problem to be solved from different ways, which vary according to the ease of implementation and convenience in use. Come take a look in this post how to enable this scenario in his account of VSTS.
(This post is machine-translated. A proper translation is in the works)
OK, I understand that in spite of everything I mentioned in my post about TFS and VSTS you can have their reasons for wanting to use TFS on-premises. When a company decides to use the TFS and prepares to do the installation, discovers that one of the prerequisites of the installation is SQL Server. This is where the question arises: “How do I properly the SQL Server that will be used by TFS?”
The answer is so complicated but, like everything that involves licensing, requires care and attention. Here are the answers to some of the most frequently asked questions that we have made on this subject.