Skip to main content

Azure DevOps

Visualize Azure DevOps projects, teams, and users, and monitor changes through queries and alerts.

Installation​

The Azure DevOps integration uses a read-only Personal Access Token (PAT) to ingest projects, teams, users, repositories, pipelines, pull requests, work items, and security findings from Azure DevOps Services (cloud). Before enabling the integration in JupiterOne, generate a PAT and grant the required permissions.

Prerequisites​

  • An Azure DevOps organization on Azure DevOps Services (cloud). On-premises Azure DevOps Server is partially supported — the Service Endpoints, Audit Streams, and Advanced Security steps require Azure DevOps Services.
  • An account with permission to create Personal Access Tokens in your organization.
  • Access to JupiterOne with permission to configure integrations.

Creating a Personal Access Token in Azure DevOps​

  1. Sign in to your Azure DevOps organization at https://dev.azure.com/{yourOrganization}.

  2. In the upper-right corner, click your profile picture and select Personal access tokens.

  3. Click New Token and provide a descriptive name (for example, JupiterOne Integration).

  4. Set the Expiration to a value appropriate for your organization's security policy.

  5. Under Scopes, select Custom defined, then enable the following permissions:

    ScopeRequired permission
    Project and TeamRead
    Work ItemsRead
    BuildRead
    EnvironmentRead & Manage
    CodeRead
    Advanced SecurityRead
    note

    Optional ingestion sources — if you enable Service Endpoints or Audit Streams in the JupiterOne integration settings, also grant:

    ScopeRequired permission
    Service ConnectionsRead
    AuditingRead

  6. Click Create and copy the generated token — it is shown only once.

For full instructions on creating PATs, see the Azure DevOps documentation.

Configuration in JupiterOne​

To install the Azure DevOps integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Azure DevOps. Click New Instance to begin configuring the integration.

Creating an Azure DevOps instance requires the following:

  • The Account Name used to identify the Azure DevOps account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Account ID — your Azure DevOps organization URL in the form https://dev.azure.com/{yourOrganization}. This is the URL you use to access your organization in the browser.

  • Personal Access Token — the token generated above.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.