This folder contains two templates, azuredeploy.json will deploy a high-availability version of the Team Foundation Server and deployagents.json can be used to deploy build agents. The templates assume that you already have established some network infrastructure with domain controller(s). You can use the core-network template to deploy that. You also need a SQL Server, for the high-availability deployment, you can use the sql-alwayson template.
Since TFS establishes a web endpoint on the TFS servers, it is recommended that you secure that with SSL certificates. If you do not provide a certificate, a self-signed one will be generated. You can replace it after installation too. The way to provide it during deployment is through the secrets and sslThumbprint parameters. The secrets parameter is used to provide an array of certificates from Azure Key Vault. The sslThumbprint parameter instructs the TFS installation script on which certificate to install. The repository includes a convenience script, which you can use to create a key vault to hold domain admin password and the SSL certificate. This script will create the key vault, upload all secrets, and generate a deployment parameters file with the details needed for deployment.
If you are looking for a complete template deployment of networking, SQL server, TFS, and agents, please use the devnet-tfs-ha template.
Deploy this solution to either Azure Commercial or Azure Government:
- Add databases to availability group
- Log into the first database node in the SQL cluster.
- Start SQL Server Management Studio (SSMS).
- Backup the databases "Tfs_Configuration" and "Tfs_DefaultCollection"
- Make a share that is accessible from all database nodes in the cluster, e.g.
F:\Backup - In SSMS find "Availability Databases" by expanded a few levels under "Always On High Availability", right-click and choose "Add Databases"
- Add the two TFS databases and follow the wizard. Choose "Full Database and Log Backup" option and point to the share you created.
- Run the Wizard.
- Install build agents. *Agents are not included in the base template, but you can use the template below if you would just like generic Windows agents.
Deploying build agents is not part of the high availability template itself, since they are likely to require specific configuration related to the workloads they are to support. However, you can use the deployagents.json template as inspiration or if you simply want some Windows build agents with Visual Studio installed, deploy build agents:
Note : If you are experiencing problems with registering build agents. Specifically, an error message like TF400813: Resource not available for anonymous access. Client authentication required., reboot the TFS nodes and try again.