Create Cloud Hosted Build VM

Need an extra build box? Look no further for how to set that up.

If you need an extra build box, those are easy to setup as a cloud-hosted VM. To get started, you'll need to have performed the following:

1. Create a generic servicing account for environment creation like DynamicsServicing@Contoso.com
2. Add the generic servicing account to Azure DevOps (AZDO)
3. Generate a personal access token for the generic servicing account in AZDO (and securely record it)
4. Setup the connection to Visual Studio Team Services (aka Azure DevOps) in your LCS project. (Hamburger > Project Settings > Visual Studio Team Services and follow the wizard)

First, go to LCS, click on the hamburger and go to cloud-hosted environments.

Click Add.

Select the version you want. This should default to the most recent version which is what you should provision.

Select "DEVTEST"

Select "Finance and Operations - Build and Test"

Give the environment a name that is unique, select the size if you want something different than a D13 then click on advanced settings. You will need a size that has at least 8 CPU but you can scale this down after the environment is provisioned in Azure if long(er) build times aren't an issue.

Give the build agent a name. I typically give it the same name as the environment name. Enter the branch name for the default build branch. This will also commit some required assets to this branch that will need to be merged to other branches for builds to run. The assets will be committed to (branch)/Main.

Typically no changes are required on Visual Studio Customization

Typically no changes are required on Supported Version

For Application database, select none.

Typically no changes are required in disk space configuration. You can change this to whatever you would like but I suggest you take the defaults.

Typically you want to leave premium storage disabled unless you have a specific reason to use it. It costs extra and doesn't net you a lot in reduced build times (typically).

Typically managed disks are not required.

Give the VM a name. Here we will give the name of the machine less then final number which will be concatenated onto the name. 

Leave "Publish This Environment" to disabled.

I typically put each VM on its own vNet. When VMs are on the same vNet, you can easily move files around but this should only need code and the build agent will handle that.

Click next, check the checkbox to confirm you accept the terms and conditions then click next again. You will get a confirmation, click deploy and that's it.