Azure DevOps Connector for SSIS

Azure DevOps Connector can be used to integrate Azure DevOps data in your App / BI Tools. You can create, read, query, modify, and delete WorkItems, Projects, Teams and more.

In this article you will learn how to quickly and efficiently integrate Azure DevOps data in SSIS without coding. We will use high-performance Azure DevOps Connector to easily connect to Azure DevOps and then access the data inside SSIS.

Let's follow the steps below to see how we can accomplish that!

Download Documentation

Azure DevOps Connector for SSIS is based on ZappySys API Connector Framework which is a part of SSIS PowerPack. It is a collection of high-performance SSIS connectors that enable you to integrate data with virtually any data provider supported by SSIS, including SQL Server. SSIS PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few (if you are new to SSIS and SSIS PowerPack, find out more on how to use them).

Connect to Azure DevOps in other apps

Connect to Azure DevOps in SQL Server

Connect to Azure DevOps in Power BI

Connect to Azure DevOps in SSRS

Connect to Azure DevOps in Informatica

Connect to Azure DevOps in MS Access

Connect to Azure DevOps in MS Excel

Connect to Azure DevOps in SSAS

Connect to Azure DevOps in C#

Connect to Azure DevOps in Python

Connect to Azure DevOps in JAVA

Connect to Azure DevOps in Tableau

Connect to Azure DevOps in SAP Crystal Reports

Connect to Azure DevOps in Azure Data Factory (Pipeline)

Connect to Azure DevOps in Azure Data Factory (SSIS)

Connect to Azure DevOps in Talend Studio

Connect to Azure DevOps in UiPath

Connect to Azure DevOps in PowerShell

Connect to Azure DevOps in ODBC

Video Tutorial - Integrate Azure DevOps data in SSIS

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

How to download and install the required PowerPack for Azure DevOps integration in SSIS
How to configure the connection for Azure DevOps
Features of the ZappySys API Source (Authentication / Query Language / Examples / Driver UI)
How to use the Azure DevOps in SSIS

Watch this video on YouTube

Prerequisites

Before we begin, make sure the following prerequisites are met:

SSIS designer installed. Sometimes it is referred as BIDS or SSDT (download it from Microsoft).
Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
SSIS PowerPack is installed (if you are new to SSIS PowerPack, then get started!).

Read data from Azure DevOps in SSIS (Export data)

In this section we will learn how to configure and use Azure DevOps Connector in API Source to extract data from Azure DevOps.

Begin with opening Visual Studio and Create a New Project.
Select Integration Service Project and in new project window set the appropriate name and location for project. And click OK.
In the new SSIS project screen you will find the following:
1. SSIS ToolBox on left side bar
2. Solution Explorer and Property Window on right bar
3. Control flow, data flow, event Handlers, Package Explorer in tab windows
4. Connection Manager Window in the bottom
Note: If you don't see ZappySys SSIS PowerPack Task or Components in SSIS Toolbox, please refer to this help link.
Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.
From the SSIS toolbox drag and API Source (Predefined Templates) on the data flow designer surface, and double click on it to edit it:
Select New Connection to create a new connection:
Use a preinstalled Azure DevOps Connector from Popular Connector List or press Search Online radio button to download Azure DevOps Connector. Once downloaded simply use it in the configuration:

Azure DevOps

Proceed with selecting the desired Authentication Type. Then select API Base URL (in most cases default one is the right one). Finally, fill in all the required parameters and set optional parameters if needed. You may press a link Steps to Configure which will help set certain parameters. More info is available in Authentication section.

OAuth [OAuth]

Steps how to get and use Azure DevOps credentials
Connecting to your Azure DevOps data requires you to authenticate your REST API access. Follow the instructions below:

Go to https://app.vsaex.visualstudio.com/app/register to register your app.
Fill in your application and company's information as required, and then select the scopes that your application needs. This should typically be Project and team (read and write) and Work items (read and write).

Your selected scopes when registering your app must match the scopes you enter here on the connector screen. If they don't match, the connector will not be able to work with your Azure DevOps account!

If you need further information about the scopes used in Azure DevOps, or need to see what to enter into the connector screen to match up with your selected scopes, visit https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops.

NOTE: For Authorization callback URL use your company's OAuth Redirect URL (if IT administrator provides you one) or you can use https://zappysys.com/oauth (it's safe).
Select Create Application and then the Application Settings page will be displayed.
Record the App ID for us to use later:
And do the same with Client Secret:
Then go to https://aex.dev.azure.com and select relevant organization on the left.
Then copy Organization's host name part (e.g. acmeinc, if full host name is acmeinc.visualstudio.com), save it to a file, and click it:
Back at the connector screen, enter the App ID into the Client Id (App ID) field that was recorded in the previous step.
Enter the Client Secret that was recorded in the previous step into the Client Secret field. In order to edit the text in this field, select the ellipses (...) button that appears when the textbox is clicked, and edit the Client Secret with the dialog box that appears.
Enter the organization that was recorded in step 5 into the Organization name or Id for url field.
Click Generate Token. If proper authentication occurs, you will see a notice saying so. You can click Yes to save a backup file of your generated tokens.
Select the project you want to connect to by default from the Default Project (Choose after Generating Token) field.
Select the Security tab.
Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com into the Additional Trusted Domains field.
Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
If the connection test succeeds, select OK.
To edit previously created app you can visit https://app.vsaex.visualstudio.com/me and see Applications and services section. Click on your desired app name.

Configuring authentication parameters

Azure DevOps

OAuth [OAuth]

https://dev.azure.com

Required Parameters
Client Id (App ID)	Fill-in the parameter...
Client Secret	Fill-in the parameter...
Organization name or Id for url (e.g. mycompany)	Fill-in the parameter...
Return URL	Fill-in the parameter...
Scopes (Must match with App Registration)	Fill-in the parameter...
API Version	Fill-in the parameter...
Optional Parameters
Default Project Name (Choose after Generating Token)
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Personal Access Token (PAT) [Http]

Steps how to get and use Azure DevOps credentials
To connect to Azure DevOps using a Personal Access Token (PAT), you must first create a valid PAT:

Start by by going to https://aex.dev.azure.com and selecting relevant organization on the left.
Then copy Organization's host name part (e.g. acmeinc, if full host name is acmeinc.visualstudio.com), save it to a file, and click it:
Next, click User settings icon and then click Personal access tokens:
Then click New Token button to create a new personal access token:
Continue by...
- naming your token
- selecting the right Organization
- setting token's Expiration date (it's recommended to use Custom defined option and make it expire after one year or later)
- and setting the Scopes:
NOTE: You may be restricted from creating full-scoped PATs. If so, your Azure DevOps administrator in Azure AD has enabled a policy which limits you to a specific custom defined set of scopes.
Now click Copy button and save the newly created token into a file for quick access later:
Go back to the connector screen, input the token you saved in a previous step into the Personal Access Token (PAT) field.
Then enter the Organization host name part that you noted recorded in previous step into Organization name or Id for url field.
Enter the name or Id of the project you want to connect to by default in the Default Project (Choose after above fields) field.
Select the Security tab.
Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com,https://analytics.dev.azure.com into the Additional Trusted Domains field.
Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
Done!

Configuring authentication parameters

Azure DevOps

Personal Access Token (PAT) [Http]

https://dev.azure.com

Required Parameters
Personal Access Token (PAT)	Fill-in the parameter...
Organization name or Id for url	Fill-in the parameter...
API Version	Fill-in the parameter...
Optional Parameters
AuthScheme	Bearer
AuthHeader	Authorization
UserName
Default Project Name (Choose after Generating Token)
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Select the desired endpoint, change/pass the properties values, and click on Preview Data button to make the API call.

API Source - Azure DevOps

Azure DevOps Connector can be used to integrate Azure DevOps data in your App / BI Tools. You can create, read, query, modify, and delete WorkItems, Projects, Teams and more.
That's it! We are done! Just in a few clicks we configured the call to Azure DevOps using Azure DevOps Connector.

You can load the source data into your desired destination using the Upsert Destination, which supports SQL Server, PostgreSQL, and Amazon Redshift. We also offer other destinations such as CSV, Excel, Azure Table, Salesforce, and more. You can check out our SSIS PowerPack Tasks and components for more options. (*loaded in Trash Destination)

Write data to Azure DevOps using SSIS (Import data)

In this section we will learn how to configure and use Azure DevOps Connector in the API Destination to write data to Azure DevOps.

Video tutorial

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

How to download SSIS PowerPack for Azure DevOps integration in SSIS
How to configure connection for Azure DevOps
How to write or lookup data to Azure DevOps
Features about SSIS API Destination
Using Azure DevOps Connector in SSIS

Watch this video on YouTube

Step-by-step instructions

In upper section we learned how to read data, now in this section we will learn how to configure Azure DevOps in the API Source to POST data to the Azure DevOps.

Read the data from the source, being any desired source component. In example we will use ZappySys Dummy Data Source component.
From the SSIS Toolbox drag and drop API Destination (Predefined Templates) on the Data Flow Designer surface and connect source component with it, and double click to edit it.
Select New Connection to create a new connection:

API Destination - Azure DevOps

Azure DevOps Connector can be used to integrate Azure DevOps data in your App / BI Tools. You can create, read, query, modify, and delete WorkItems, Projects, Teams and more.
Use a preinstalled Azure DevOps Connector from Popular Connector List or press Search Online radio button to download Azure DevOps Connector. Once downloaded simply use it in the configuration:

Azure DevOps

OAuth [OAuth]

Steps how to get and use Azure DevOps credentials
Connecting to your Azure DevOps data requires you to authenticate your REST API access. Follow the instructions below:

Go to https://app.vsaex.visualstudio.com/app/register to register your app.
Fill in your application and company's information as required, and then select the scopes that your application needs. This should typically be Project and team (read and write) and Work items (read and write).

Your selected scopes when registering your app must match the scopes you enter here on the connector screen. If they don't match, the connector will not be able to work with your Azure DevOps account!

If you need further information about the scopes used in Azure DevOps, or need to see what to enter into the connector screen to match up with your selected scopes, visit https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops.

NOTE: For Authorization callback URL use your company's OAuth Redirect URL (if IT administrator provides you one) or you can use https://zappysys.com/oauth (it's safe).
Select Create Application and then the Application Settings page will be displayed.
Record the App ID for us to use later:
And do the same with Client Secret:
Then go to https://aex.dev.azure.com and select relevant organization on the left.
Then copy Organization's host name part (e.g. acmeinc, if full host name is acmeinc.visualstudio.com), save it to a file, and click it:
Back at the connector screen, enter the App ID into the Client Id (App ID) field that was recorded in the previous step.
Enter the Client Secret that was recorded in the previous step into the Client Secret field. In order to edit the text in this field, select the ellipses (...) button that appears when the textbox is clicked, and edit the Client Secret with the dialog box that appears.
Enter the organization that was recorded in step 5 into the Organization name or Id for url field.
Click Generate Token. If proper authentication occurs, you will see a notice saying so. You can click Yes to save a backup file of your generated tokens.
Select the project you want to connect to by default from the Default Project (Choose after Generating Token) field.
Select the Security tab.
Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com into the Additional Trusted Domains field.
Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
If the connection test succeeds, select OK.
To edit previously created app you can visit https://app.vsaex.visualstudio.com/me and see Applications and services section. Click on your desired app name.

Configuring authentication parameters

Azure DevOps

OAuth [OAuth]

https://dev.azure.com

Required Parameters
Client Id (App ID)	Fill-in the parameter...
Client Secret	Fill-in the parameter...
Organization name or Id for url (e.g. mycompany)	Fill-in the parameter...
Return URL	Fill-in the parameter...
Scopes (Must match with App Registration)	Fill-in the parameter...
API Version	Fill-in the parameter...
Optional Parameters
Default Project Name (Choose after Generating Token)
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Personal Access Token (PAT) [Http]

Steps how to get and use Azure DevOps credentials
To connect to Azure DevOps using a Personal Access Token (PAT), you must first create a valid PAT:

Start by by going to https://aex.dev.azure.com and selecting relevant organization on the left.
Then copy Organization's host name part (e.g. acmeinc, if full host name is acmeinc.visualstudio.com), save it to a file, and click it:
Next, click User settings icon and then click Personal access tokens:
Then click New Token button to create a new personal access token:
Continue by...
- naming your token
- selecting the right Organization
- setting token's Expiration date (it's recommended to use Custom defined option and make it expire after one year or later)
- and setting the Scopes:
NOTE: You may be restricted from creating full-scoped PATs. If so, your Azure DevOps administrator in Azure AD has enabled a policy which limits you to a specific custom defined set of scopes.
Now click Copy button and save the newly created token into a file for quick access later:
Go back to the connector screen, input the token you saved in a previous step into the Personal Access Token (PAT) field.
Then enter the Organization host name part that you noted recorded in previous step into Organization name or Id for url field.
Enter the name or Id of the project you want to connect to by default in the Default Project (Choose after above fields) field.
Select the Security tab.
Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com,https://analytics.dev.azure.com into the Additional Trusted Domains field.
Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
Done!

Configuring authentication parameters

Azure DevOps

Personal Access Token (PAT) [Http]

https://dev.azure.com

Required Parameters
Personal Access Token (PAT)	Fill-in the parameter...
Organization name or Id for url	Fill-in the parameter...
API Version	Fill-in the parameter...
Optional Parameters
AuthScheme	Bearer
AuthHeader	Authorization
UserName
Default Project Name (Choose after Generating Token)
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Select the desired endpoint, change/pass the properties values, and go to the Mappings tab to map the columns.

API Destination - Azure DevOps

Azure DevOps Connector can be used to integrate Azure DevOps data in your App / BI Tools. You can create, read, query, modify, and delete WorkItems, Projects, Teams and more.
Finally, map the desired columns:

API Destination - Azure DevOps

Azure DevOps Connector can be used to integrate Azure DevOps data in your App / BI Tools. You can create, read, query, modify, and delete WorkItems, Projects, Teams and more.
That's it; we successfully configured the POST API Call. In a few clicks we configured the Azure DevOps API call using ZappySys Azure DevOps Connector

Load Azure DevOps data into SQL Server using Upsert Destination (Insert or Update)

Once you configured the data source, you can load Azure DevOps data into SQL Server using Upsert Destination.

Upsert Destination can merge or synchronize source data with the target table. It supports Microsoft SQL Server, PostgreSQL, and Redshift databases as targets. Upsert Destination also supports very fast bulk upsert operation along with bulk delete.

Upsert operation - a database operation which performs INSERT or UPDATE SQL commands based on record's existence condition in the target table. It inserts records that don't have matching records in the target table or updates them, if they do, by matching them by key columns.

Upsert Destination supports INSERT, UPDATE, and DELETE operations, so it is similar to SQL Server's MERGE command, except it can be used directly in SSIS package.

From the SSIS Toolbox drag-and-drop Upsert Destination component onto the Data Flow designer background.
Connect your SSIS source component to Upsert Destination.
Double-click on Upsert Destination component to open configuration window.
Start by selecting the Action from the list.
Next, select the desired target connection or create one by clicking <New [provider] Connection> menu item from the Target Connection dropdown.
Then select a table from the Target Table list or click New button to create a new table based on the source columns.
Continue by checking Insert and Update options according to your scenario (e.g. if Update option is unchecked, no updates will be made).
Finally, click Map All button to map all columns and then select the Key columns to match the columns on:
Click OK to save the configuration.
Run the package and Azure DevOps data will be merged with the target table in SQL Server, PostgreSQL, or Redshift:
Done!

Deploy and schedule SSIS package

After you are done creating SSIS package, most likely, you want to deploy it to SQL Server Catalog and run it periodically. Just follow the instructions in this article:

How to design, debug, deploy, schedule SSIS Package (In SQL Agent and Catalog)

Running SSIS package in Azure Data Factory (ADF)

To use SSIS PowerPack in ADF, you must first prepare Azure-SSIS Integration Runtime. Follow this link for detailed instructions:

Preparing ADF instance to use SSIS PowerPack

Advanced topics

Actions supported by Azure DevOps Connector

Azure DevOps Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Get Query Fileds

Gets query fields for work items. [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Team Id or Name

Id or name of the team associated with the query.

Use time precision

Whether or not to use time precision.

Option	Value
false	false
true	true

Wiql Query

The WIQL query (refer Azure DevOps Help to learn Wiql syntax.

Get Work Items for Specified Query Id

Get work items associated with the specified project, organization and query. (A team can optionally be specified as well.). Read more about this API here https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/wiql/query-by-id?view=azure-devops-rest-7.1 [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Query Id

The Id of the predefined Query.

Team Id or Name

Id or name of the team associated with the query.

Use time precision

Whether or not to use time precision.

Option	Value
false	false
true	true

Query Work Items

Get work items associated with the specified project and organization that are filtered by a Wiql query. (A team can optionally be specified as well.). Read more about this API here https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/wiql/query-by-wiql?view=azure-devops-rest-7.0 and here https://learn.microsoft.com/en-us/azure/devops/boards/queries/query-operators-variables?view=azure-devops [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Team Id or Name

Id or name of the team associated with the query.

Use time precision

Whether or not to use time precision.

Option	Value
false	false
true	true

Wiql Query

The WIQL query (refer Azure DevOps Help to learn Wiql syntax.

Query Work Item Comments

Get work item comments associated with the specified project and organization that are filtered by a Wiql query. (A team can optionally be specified as well.). Read more about this API here https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/wiql/query-by-wiql?view=azure-devops-rest-7.0 and here https://learn.microsoft.com/en-us/azure/devops/boards/queries/query-operators-variables?view=azure-devops [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Team Id or Name

Id or name of the team associated with the query.

Use time precision

Whether or not to use time precision.

Option	Value
false	false
true	true

Wiql Query

The WIQL query (refer Azure DevOps Help to learn Wiql syntax.

Get Work Item Comments (by WorkItem Id)

Get work item comments associated with WorkItem Id [ Read more... ]

Parameter	Description
WorkItemId	WorkItem Id for which you like to get comments
Project Name	The Name of the project.
api-version	For this API you must set 7.0-preview for now

Get Work Item Comment by Comment Id and Work Item Id

Get work item comment by its Comment Id (for specific WorkItem Id) [ Read more... ]

Parameter	Description
Id	Comment Id
WorkItemId	WorkItem Id for which you like to get comments
Project Name	The Name of the project.
api-version	For this API you must set 7.0-preview for now

Create Work Item Comment

Creates work item comment for a specific WorkItem Id [ Read more... ]

Parameter	Description
Id	Comment Id
WorkItemId	WorkItem Id for which you like to get comments
Project Name	The Name of the project.
Comment Text
api-version	For this API you must set 7.0-preview for now

Update Work Item Comment

Update work item comment for a specific Work Item Id and Comment Id [ Read more... ]

Parameter	Description
Id	Comment Id
WorkItemId	WorkItem Id for which you like to get comments
Project Name	The Name of the project.
Comment Text
api-version	For this API you must set 7.0-preview for now

Delete Work Item Comment

Delete work item comment for a specific Work Item Id and Comment Id [ Read more... ]

Parameter	Description
Id	Comment Id
WorkItemId	WorkItem Id for which you like to get comments
Project Name	The Name of the project.
api-version	For this API you must set 7.0-preview for now

Get Work Item Column Fields

Get work item column fields in the default project within the organization. Read more about description on each field here https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/work-item-field?view=azure-devops [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Expand Parameters

The expand parameters for work item attributes. Possible options are 'None', 'Relations', 'Fields', 'Links', and 'All'.

Option	Value
None	None
Relations	Relations
Fields	Fields
Links	Links
All	All

Get Work Items by Ids

Get work items in the default project within the organization by their work item Ids. [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Work Item Id List (comma separated)

The comma-separated list of requested work item ids. (Maximum 200 ids allowed).

As-Of Date

AsOf UTC date time string.

Expand Parameters

The expand parameters for work item attributes. Possible options are 'None', 'Relations', 'Fields', 'Links', and 'All'.

Option	Value
None	None
Relations	Relations
Fields	Fields
Links	Links
All	All

Error Policy

The flag to control error policy in a bulk get work items request. Possible options are 'Fail' and 'Omit'.

Option	Value
Fail	Fail
Omit	Omit

Fields

Comma-separated list of requested fields.

Get Work Item Types

Get work item types in the default project within the organization. [ Read more... ]

Parameter	Description
Project Name	The Name of the project.

Create Work Item

Creates a new work item in the default project within the organization. [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

WorkItemType

ByPassRules

Set this to true to allow setting values for some fields which otherwise wont work due to certain rules

Option	Value
true	true
false	false

Update Work Item

Updates an existing work item in the default project within the organization. [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Work Item Id

Operation

Some operation requires you to supply 'add' rather than 'replace' (e.g. adding new tag)

Option	Value
replace	replace
add	add
remove	remove
copy	copy
move	move
test	test

Delete Work Item

Deletes an existing work item in the default project within the organization. [ Read more... ]

Parameter	Description
Project Name	The Name of the project.
Work Item Id

Get List of Queries

Gets a list of predefined queries within the organization. [ Read more... ]

Parameter	Description
Project Name	The Name of the project.
Max Depth (items inside nested folders)

Get List of Projects

Gets a list of projects within the organization. [ Read more... ]

Get Project Details

Gets the details of the specified project within the organization by its project Id. [ Read more... ]

Parameter	Description
Id

Create Project

Create a new project within the organization. [ Read more... ]

Update Project

Update an existing project within the organization. [ Read more... ]

Parameter	Description
Project Id	The ID of the project to update.

Delete Project

Delete an existing project within the organization. [ Read more... ]

Parameter	Description
Project Id	The ID of the project to delete.

Get List of Teams

Gets a list of teams in the default project within the organization. [ Read more... ]

Parameter	Description
Project Name	The Name of the project.

Get Team Details

Gets the details of the specified team in the default project within the organization by its team Id or team name. [ Read more... ]

Parameter

Description

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Team Id or Name

Project Name

The Name of the project.

Create Team

Creates a new team in the default project within the organization. [ Read more... ]

Update Team

Updates the details of the specified team in the default project within the organization by its team Id. [ Read more... ]

Parameter

Description

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Team Id

Delete Team

Deletes the specified team in the default project within the organization by its team Id. [ Read more... ]

Parameter

Description

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Team Id

The ID of the team to delete.

Search for Work Items by Text

Search for specific text within work items in the default project of the organization. [ Read more... ]

Parameter	Description
Text to Search For

Get Team Members

Lists all members part of a specified Team in the project within the organization (by team Id or team name). [ Read more... ]

Parameter

Description

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Project Name

The Name of the project.

Team Id or Name

Get Team Iterations

Lists Team iterations for a specified project / team. [ Read more... ]

Parameter

Description

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Project Name

The Name of the project.

Team Id or Name

Get Team Iteration Capacities

Lists capacity for all team members in a specified project / team / iteration. [ Read more... ]

Parameter

Description

Project Name

The Name of the project.

Team Id or Name

Itertation Id or Name

API Version

Option	Value
7.0-preview	7.0-preview
7.1-preview.2	7.1-preview.2

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter

Description

Url

API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains

Body

Request Body content goes here

IsMultiPart

Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle

Filter

Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract

Option	Value
No filter
Example1	$.store.books[*]
Example2 (Sections Under Books)	$.store.books[].sections[]
Example3 (Equals)	$.store.books[?(@author=='sam')]
Example4 (Equals - Any Section)	$..[?(@author=='sam')]
Example5 (Not Equals - Any Section)	$..[?(@author!='sam')]
Example6 (Number less than)	$.store.books[?(@.price<10)] Example7 (Regular Expression - Contains Pattern)=$.store.books[?(@author=~ /sam\|bob/ )]
Example8 (Regular Expression - Does Not Contain Pattern)	$.store.books[?(@author=~ /^((?!sam\|bob).)*$/ )]
Example9 (Regular Expression - Exact Pattern Match)	$.store.books[?(@author=~ /^sam\|bob$/ )]
Example10 (Regular Expression - Starts With)	$.store.books[?(@author=~ /^sam/ )]
Example11 (Regular Expression - Ends With)	$.store.books[?(@author=~ /sam$/ )]
Example12 (Between)	$.store.employees[?( @.hiredate>'2015-01-01' && @.hiredate<'2015-01-04' )]

Headers

Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Generic Request (Bulk Write)

This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe (\|\|) or new line after each {header-name}:{value} pair

Conclusion

In this article we showed you how to connect to Azure DevOps in SSIS and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys API Driver allows you to connect not only to Azure DevOps, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Azure DevOps Connector for SSIS and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Azure DevOps Connector for SSIS Documentation

More integrations

Other connectors for SSIS

All

Big Data & NoSQL

Database

CRM & ERP

Marketing

Collaboration

Cloud Storage

Reporting

Commerce

API & Files

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Build your own Custom API Connector

Other application integration scenarios for Azure DevOps

All

Data Integration

Database

BI & Reporting

Productivity

Programming Languages

Automation & Scripting

ODBC applications

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Download Azure DevOps Connector for SSIS Documentation

Common Searches:

How to connect Azure DevOps in SSIS?
How to get Azure DevOps data in SSIS?
How to read Azure DevOps data in SSIS?
How to load Azure DevOps data in SSIS?
How to import Azure DevOps data in SSIS?
How to pull Azure DevOps data in SSIS?
How to push data to Azure DevOps in SSIS?
How to write data to Azure DevOps in SSIS?
How to POST data to Azure DevOps in SSIS?
Call Azure DevOps API in SSIS
Consume Azure DevOps API in SSIS
Azure DevOps SSIS Automate
Azure DevOps SSIS Integration
Integration Azure DevOps in SSIS
Consume real-time Azure DevOps data in SSIS
Consume real-time Azure DevOps API data in SSIS
Azure DevOps ODBC Driver | ODBC Driver for Azure DevOps | ODBC Azure DevOps Driver | SSIS Azure DevOps Source | SSIS Azure DevOps Destination
Connect Azure DevOps in SSIS
Load Azure DevOps in SSIS
Load Azure DevOps data in SSIS
Read Azure DevOps data in SSIS
Azure DevOps API Call in SSIS