I was interested to know just what the hardware specifications of the hosted build agent is. So I added some PowerShell to read out the info below:


2016-06-29T09:23:31.3935358Z systemname   Name                   DeviceID NumberOfCores NumberOfLogicalProcessors Addresswidth
2016-06-29T09:23:31.3935358Z ----------   ----                   -------- ------------- ------------------------- ------------
2016-06-29T09:23:31.3935358Z TASKAGENT5-0010 Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz CPU0         2             2      64
2016-06-29T09:23:31.4095356Z Total memory: 7167.55078125

What piqued my interest greater was that this is the exact same spec for a D2 v2 box that is available via Azure. Clearly, Microsoft have a build agent template which is built, stored in a pool, and provisioned whenever a build takes place. One must assume that it is disposed of after a single use to prevent and nefarious activity by other people trying to steal code….

![d2v2_png” alt="d2v2” width="983” height="396](/assets/g class="alignnone size-full wp-image-4375” src="https://phoenixultd.files.wordpress.com/2016/08/d2v2.png” alt="d2v2” width="983” height="396)