What's New
Product Documentation
Installing Enterprise Agents with Microsoft Azure
ThousandEyes Enterprise Agents can be deployed natively in some infrastructure-as-a-service providers. This article covers the steps to deploy an Enterprise Agent in a Microsoft Azure environment.

Prerequisites

  • A Microsoft Azure login with virtual machine provisioning permissions.
  • A ThousandEyes account with organizational permissions to add/edit Enterprise Agents.

Deployment

  1. 1.
    Log into the ThousandEyes web application.
  2. 2.
    Navigate to Cloud & Enterprise Agents > Agent Settings > Enterprise Agents > Agents.
  3. 3.
    Click Add New Enterprise Agent.
  4. 4.
    Navigate to the Cloud Templates tab.
  5. 5.
    Click Launch in Azure.
  6. 6.
    Log into your Microsoft Azure account.
  7. 7.
    Complete the custom deployment template. Most of the fields are pre-filled for you. The following fields require input:
    • Account Group Token: The ThousandEyes organization's Account Group Token.
    • Hostname: The hostname of the Enterprise Agent.
    Note: Proxy support is also available. See Azure Proxy Support for configuration details.
  8. 8.
    Click Review + Create to move to the next stage.
  9. 9.
    Review the terms and conditions of creation, then click Create.
Once the deployment is complete, it will be listed in the resource list in Microsoft Azure:
It will also be available in the list of Enterprise Agents within the ThousandEyes application, and is ready for testing.

Additional Configuration Options

Proxy Support

ThousandEyes supports installing an Enterprise Agent in a proxied Microsoft Azure cloud environment. When configuring the custom deployment template (step 7 in the Deployment section above), set the following configuration options:
  1. 1.
    Open the Proxy Type drop-down menu and select STATIC.
  2. 2.
    Configure the Proxy Host field, including the port number. For example, if the proxy server is at 10.2.1.1 and uses port 8030, set the field to 10.2.1.1:8030.
  3. 3.
    Optional: Use the Proxy User and Proxy Password fields if necessary to configure a user/password combination.
The deployment template does not support configuring a proxy via a PAC file.