In YAML pipelines, if you do not specify a pool, pipelines will default to the Azure Pipelines agent pool. An upgrade is requested when a platform feature or one of the tasks used in the pipeline requires a newer version of the agent. In Azure DevOps Server, agent pools are scoped to the entire server; so you can share the agent machines across projects and collections. The best way to prevent this is to avoid the need to access internal resources. If you refer to your server by its IP address, make sure that the IP address is publicly accessible on the Internet. You cannot use private connections such as ExpressRoute or VPN to connect Microsoft-hosted agents to your corporate network. Roles are also defined on each project agent pool, and memberships in these roles govern what operations you can perform on an agent pool at the project level. You'll use the following tasks in your build definitions to analyze your projects: Euler: A baby on his lap, a cat on his back thats how he wrote his immortal works (origin? If your pipelines are in Azure Pipelines, then you've got a convenient option to run your jobs using a Microsoft-hosted agent. In the following example, the hosted agent IP address ranges for an organization in the West US region are retrieved from the weekly file. For more information, see the Single hosted pool release notes from the July 1 2019 - Sprint 154 release notes. Each agent is dedicated to a single organization, and each VM hosts only a single agent. Thanks for contributing an answer to Stack Overflow! First make sure you're a member of a group in All agent pools with the Administrator role by navigating to agent pools page in your organization settings. Instead of managing each agent individually, you organize agents into agent pools. You need to be an agent pool administrator to register an agent in that agent pool. Azure Pipelines Agent is open source on GitHub. To determine your geography, navigate to https://dev.azure.com/