The Azure DevOps connector is a Palantir-provided driver for Azure DevOps.
To create a new Azure DevOps source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Azure DevOps-specific configuration and networking. For the complete property reference, see the official Azure DevOps driver documentation ↗.
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
AzureDevOpsEdition ↗ | Mandatory | The edition of AzureDevOps being used. Set either [AzureDevOps Online] or [AzureDevOps OnPremise]. | AzureDevOps Online |
Organization ↗ | Mandatory | The name of the Organization or Collection, depending upon the value of AzureDevOpsEdition . | — |
AuthScheme ↗ | Recommended | The type of authentication to use when connecting to Azure DevOps. Azure DevOps OnPremise connections support only Basic authentication. | Basic |
Catalog ↗ | Recommended | Specify this property to connect with a particular catalog. | — |
IncludeCustomFields ↗ | Recommended | A boolean indicating if you would like to include custom fields in the column listing. | TRUE |
InitiateOAuth ↗ | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
PersonalAccessToken ↗ | Recommended | The personal access token used for accessing the data in your organization. | — |
Schema ↗ | Recommended | Specify this property to connect with a particular schema. | REST |
The table below lists the domains that the source needs to be able to access in order to successfully run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| dev.azure.com | If Schema=REST (default) AND AzureDevOpsEdition='AzureDevOps Online' (default) |
| analytics.dev.azure.com | If Schema=Analytics AND AzureDevOpsEdition='AzureDevOps Online' (default) |
| <URL> | If AzureDevOpsEdition='AzureDevOps OnPremise' |
| login.microsoftonline.com | If AuthScheme=AzureAD (default) AND AzureEnvironment=GLOBAL (default) |
| login.chinacloudapi.cn | If AuthScheme=AzureAD (default) AND AzureEnvironment=CHINA |
| login.microsoftonline.us | If AuthScheme=AzureAD (default) AND AzureEnvironment=USGOVT or USGOVTDOD |