Hosted agents

Last Update: 4/25/2017

Team Services

If you use Visual Studio Team Services, to build or deploy your app, then it's more convenient to use our hosted agents, but some limitations apply.

TIP

You can try a hosted agent for no charge. If it doesn't work, the issues will be reported in the build or release logs.

Use a hosted agent

To use a hosted agent, while editing your build definition, on the Options or General tab, for the Default agent queue, and then select either:

  • Hosted

  • Hosted VS2017 if your team uses Visual Studio 2017

If your team uses Linux, select Hosted Linux Preview.

During the preview, we provide only one of these preview agents at a time.

Capabilities and limitations

Hosted agents:

Hosted agents do not offer:

  • Interactive mode.

  • Administrator privileges.

  • The ability to log on.

  • The ability to drop artifacts to a UNC file share.

  • The ability to run XAML builds.

  • The potential performance benefits of running incremental builds on a private agent. For example, if you use a private agent and you define a CI build process that does not clean the repo and does not perform a clean build, your builds will typically run faster. When you use a hosted agent, you don't get these benefits because the agent is destroyed after the build or release process is completed.

If our hosted agents don't meet your needs, then you can deploy your own private agents.

Avoid hard coded references

When you use a hosted agent, you should always use variables to construct any references to resources used by your build. We recommend you avoid making hard-coded presumptions about resources provided by the hosted agent (for example, the drive letter of folder that contains the repo).

Software

Hosted

  • Windows Server 2012 R2, 64-bit environment, with Windows PowerShell
  • Team Foundation Build (Team Foundation Server 2013)
  • Visual Studio 2015 Update 3
  • Visual Studio SDK 2015 RTM
  • Visual Studio 2013 Update 5
  • Visual Studio SDK 2013 RTM
  • Visual Studio 2012 Ultimate Update 4
  • Visual Studio SDK 2012 RTM
  • Visual Studio 2010 SP1

  • The .NET Framework

    • .NET 4.6.2
    • .NET 4.5.2
    • .NET 4.5.1
    • .NET 4.5
    • .NET 3.5 SP1
    • .NET Core 1.0
    • .NET Core 1.1
  • Microsoft Azure

    • SDK 2.9.6
    • SDK 2.8
    • SDK 2.7
    • SDK 2.6
    • SDK 2.5
    • SDK 2.4
    • SDK 2.3
    • SDK 2.2
    • Azure CLI 0.10.7
    • Azure PowerShell 3.6.0
    • AzureRM PowerShell 3.6.0
  • Other components

    • Android Native Development Kit r13b
    • Android Software Development Kit 25.2.5
    • Android support repository version 30
    • Apache ANT 1.9.7
    • Apache Maven 3.2.2
    • ASP.NET 3.5
    • ASP.NET MVC 2
    • ASP.NET MVC 3
    • ASP.NET Web Tools for Visual Studio 2015 (Beta 8)
    • ASP.NET Web Tools for Visual Studio Express 14 for Web (Beta 8)
    • Bing Maps SDK
    • CMake 3.7.1
    • Cordova 6.1.0
    • Git 2.10.1
    • Git for Windows 2.10.2
    • Git LFS 1.5.2
    • Google Repository version 29
    • GTK# 2.12.30
    • Java Standard Edition Development Kit 1.8
    • Let's Encrypt root certs for JDK certificate store
    • Microsoft Office Developer Tools for Visual Studio 2012
    • Microsoft Office Developer Tools for Visual Studio 2013 (March 2014 Update)
    • Multilingual Application Toolkit 4
    • Node.js 6.9.1
    • Node.js Tools 1.0 Beta for Visual Studio 2013
    • Node.js Tools 1.0 for Visual Studio 2015
    • Python 2.7
    • Python Tools for Visual Studio 2012 and Visual Studio 2013
    • Service Fabric 5.4.164.9494
    • Service Fabric SDK 2.4.164
    • SharePoint 2010 and SharePoint 2013
    • SharePoint Online Shell
    • SQL Lite for WinRT 8.0, WinRT 8.1, and Windows Phone 8.0, 8.1
    • SQL Server DAC Framework for x86 and x64 (July 2015)
    • SQL Server Data Tools for Visual Studio 2010, Visual Studio 2012, Visual Studio 2013, and Visual Studio 2015
    • SQL Server Data Tools BI for Visual Studio 2012 and Visual Studio 2013
    • TFS Build Extensions
    • TypeScript 1.4 for Visual Studio 2013
    • TypeScript 1.6 for Visual Studio 2013 and Visual Studio 2015
    • TypeScript 1.7.5 for Visual Studio 2013
    • TypeScript 1.7.6 for Visual Studio 2015
    • TypeScript 1.8.6 for Visual Studio 2013 and Visual Studio 2015
    • TypeScript 2.0.6 for Visual Studio 2015
    • WIX Toolset 3.10
    • Web Deploy 3.0
    • Windows 10 SDK 14393
    • Windows 8 Shared SDK Tools
    • Windows Phone SDK 8.0
    • Xamarin for Visual Studio 4.2.2.11
    • Xamarin Studio 6.1.4.1
    • Xamarin Stable Cycle 9

Hosted VS2017

  • Visual Studio 2017 (15.1 Update)

  • .NET Core SDK

    • '1.0.0-preview2-1-003177'
    • '1.0.0-preview2-003121'
    • '1.0.0-preview3-004056'
    • '1.0.0-preview4-004233'
    • '1.0.0-rc3-004530'
    • '1.0.0-rc4-004771'
    • '1.0.0-rc4-004834'
    • '1.0.0-rc4-004802'
    • '1.0.0-rc4-004847'
    • '1.0.0'
  • Android SDK, including support for repositories

  • ANT 1.9.7 w/ Cobertura
  • Azure CLI 2.02 (Python)
  • Azure PowerShell 3.6.0
  • AzureRM PowerShell 3.6.0
  • Bower
  • CMake 3.8
  • Docker Compose
  • Git for Windows 2.12
  • GIT LFS 2.0.2
  • Grunt
  • Gulp
  • JDK 1.6.0_45
  • JDK 1.7.0_75
  • JDK 1.8.0_102
  • Let's Encrypt certificates for JDK 1.8.0_102
  • Maven 3.2.2
  • Microsoft.DataTools.AnalysisServices
  • Microsoft.DataTools.ReportingServices
  • Multilingual App Toolkit 4.0
  • Node 6.10.0
  • NPM Packages
  • Python 2.7.13
  • Python 3.6.1
  • Service Fabric 5.4.164.9494
  • Service Fabric SDK 2.4.164
  • SQL Lite for UWP apps
  • SQL Server Data Tools "Extras"
  • WIX Toolset 3.10

Hosted Linux Preview

See https://github.com/Microsoft/vsts-agent-docker/blob/master/ubuntu/16.04/docker/1.12.1/standard/Dockerfile

Q & A

I can't select the hosted queue and I can't queue my build or deployment. How do I fix this?

By default, all project contributors in an account have access to the hosted queue. But, your account administrator may have limited the access of hosted queue to select users or projects. Ask the owner of your Team Services account to grant you permission to use the queue. See agent queue security.

I need more agents. What can I do?

A: The hosted pool provides all Visual Studio Team Services accounts with a single agent and a limited number of free minutes each month. If you need more minutes, or need to run more than one build or release concurrently, then you can buy concurrent pipelines.

I'm looking for the hosted XAML build controller. Where did it go?

The hosted XAML build controller is no longer supported. Accounts created on or after April 2016 do not have access to it. We plan to remove the hosted XAML build controller from all accounts, possibly as soon as March 2017.

Important:

  • If you have an account in which you still need to run XAML builds, you should set up an on-premises build server and switch to an on-premises build controller now.
  • If you used the hosted XAML build controller, you might have been paying for build minutes, which is a model we no longer support. Please go to the billing portal and buy concurrent pipelines. See Buy pipelines for Build & Release. We will soon block the hosted pool from using the per-minute billing model. By making this switch we enable you to run longer builds (unlimited minutes within reason).