A TFS server setup in a Azure VM, in a virtual network and a domain, can be exposed to public access by following below steps.
The TFS server should be up and running and it should be accessible other virtual machines in the domain. DNS in setup in domain controller to resolve the TFS server internal static IP.
It is required to identify the public IP of the TFS server. Public IP can be found by clicking on Azure VM and then going to dashboard of the VM.
In a local machine which have internet access, this public IP can be added to the host file to allow to resolve name.
When try to access TFS server in azure VM in local machine it fails.
Attempt with IP address does not work.
This is due to TFS port 8080 in Azure VM is not accessible publicly (form local machine).
Fist allow 8080 port for public access in TFS Server.
To enable access add an endpoint allowing 8080 publicly as shown below for the TFS VM.
Specify TCP port 8080 for Public and Private ports.
Once end point is successfully configured TFS hosted in cloud can be accessed with local machine.
It is great if the latest updates to TFS can be applied as and when they are released. But for a large organization it might not be sometime...
Resolve MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-rc4-004771\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found or Unable to start the process. No executable found matching command "dotnet-projectmodel-server"You might encounter compilation error in Visual Studio 2015 when a new .NET Core 1 web app is created, if you have installed Visual Studio 2...
You needed to setup dedicated machines for testing when using Run Functional Tests and you had to execute, Deploy Test Agent step and Copy...
TFS 2018 RC1 is now available and you can download it from https://www.visualstudio.com/downloads/ . Release note here explains the new fea...
If you have upgraded the TFS from TFS 2015 to TFS 2018 you will encounter a situation where your vNext build agents 1.xx are no longer valid...