Visualize Azure DevOps projects, teams, and users, and monitor changes through queries and alerts.
- Installation guide
- Azure DevOps data model
To install this integration, you will need to configure settings both within Azure DevOps and on JupiterOne. Before enabling in JupiterOne, ensure that you have completed the setup within Azure DevOps.
Configuration on Azure DevOps
The Azure DevOps integration uses a read-only, personal access token to ingest data from the Azure DevOps platform.
You must have the necessary permissions to generate a personal access token in Azure DevOps.
You will need to generate your Personal Access Token (PAT), and grant the following permissions for the PAT:
- Project and Team :
- Work Items:
With your PAT created, and the credentials at hand, proceed to JupiterOne for the remaining setup.
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 AirWatch account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle 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
DISABLEDand manually execute the integration.
Your Azure DevOps URL (example: "https://dev.azure.com/jupiterone") and your Personal Access Token generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
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.
The following entities are created:
|Resources||Entity ||Entity |
|Azure Devops Account|
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |
The following mapped relationships are created:
|Source Entity ||Relationship ||Target Entity ||Direction|