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

Prerequisites

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

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

Read data from Azure DevOps in SSIS (Export data)

1. Begin with opening Visual Studio and Create a New Project.

2. Select Integration Service Project and in new project window set the appropriate name and location for project. And click OK.

3. 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.

4. Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.

   

5. From the SSIS toolbox drag and API Source (Predefined Templates) on the data flow designer surface, and double click on it to edit it:
   

6. Select New Connection to create a new connection:
   

7. 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

   

8. 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:

   1. Go to https://app.vsaex.visualstudio.com/app/register to register your app.
   2. 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).

   3. Select Create Application and then the Application Settings page will be displayed.
   4. Record the App ID for us to use later:
   5. And do the same with Client Secret:
   6. Then go to https://aex.dev.azure.com and select relevant organization on the left.
   7. 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:
   8. Back at the connector screen, enter the App ID into the Client Id (App ID) field that was recorded in the previous step.
   9. 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.
   10. Enter the organization that was recorded in step 5 into the Organization name or Id for url field.
   11. 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.
   12. Select the project you want to connect to by default from the Default Project (Choose after Generating Token) field.
   13. Select the Security tab.
   14. Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com into the Additional Trusted Domains field.
   15. Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
   16. If the connection test succeeds, select OK.
   17. 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:

   1. Start by by going to https://aex.dev.azure.com and selecting relevant organization on the left.
   2. 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:
   3. Next, click User settings icon and then click Personal access tokens:
   4. Then click New Token button to create a new personal access token:
   5. 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.

   6. Now click Copy button and save the newly created token into a file for quick access later:
   7. Go back to the connector screen, input the token you saved in a previous step into the Personal Access Token (PAT) field.
   8. Then enter the Organization host name part that you noted recorded in previous step into Organization name or Id for url field.
   9. Enter the name or Id of the project you want to connect to by default in the Default Project (Choose after above fields) field.
   10. Select the Security tab.
   11. Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com,https://analytics.dev.azure.com into the Additional Trusted Domains field.
   12. Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
   13. 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

   

9. 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.

   

10. 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)

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.

1. Read the data from the source, being any desired source component. In example we will use ZappySys Dummy Data Source component.

2. 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.
   

3. 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.

   

4. 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

   

5. 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:

   1. Go to https://app.vsaex.visualstudio.com/app/register to register your app.
   2. 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).

   3. Select Create Application and then the Application Settings page will be displayed.
   4. Record the App ID for us to use later:
   5. And do the same with Client Secret:
   6. Then go to https://aex.dev.azure.com and select relevant organization on the left.
   7. 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:
   8. Back at the connector screen, enter the App ID into the Client Id (App ID) field that was recorded in the previous step.
   9. 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.
   10. Enter the organization that was recorded in step 5 into the Organization name or Id for url field.
   11. 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.
   12. Select the project you want to connect to by default from the Default Project (Choose after Generating Token) field.
   13. Select the Security tab.
   14. Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com into the Additional Trusted Domains field.
   15. Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
   16. If the connection test succeeds, select OK.
   17. 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:

   1. Start by by going to https://aex.dev.azure.com and selecting relevant organization on the left.
   2. 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:
   3. Next, click User settings icon and then click Personal access tokens:
   4. Then click New Token button to create a new personal access token:
   5. 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.

   6. Now click Copy button and save the newly created token into a file for quick access later:
   7. Go back to the connector screen, input the token you saved in a previous step into the Personal Access Token (PAT) field.
   8. Then enter the Organization host name part that you noted recorded in previous step into Organization name or Id for url field.
   9. Enter the name or Id of the project you want to connect to by default in the Default Project (Choose after above fields) field.
   10. Select the Security tab.
   11. Enter https://auditservice.dev.azure.com,https://almsearch.dev.azure.com,https://analytics.dev.azure.com into the Additional Trusted Domains field.
   12. Select the Test Connection button at the bottom of the window to verify proper connectivity with your Azure DevOps account.
   13. 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

   

6. 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.

   

7. 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.

   

8. 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.

1. From the SSIS Toolbox drag-and-drop Upsert Destination component onto the Data Flow designer background.

2. Connect your SSIS source component to Upsert Destination.

3. Double-click on Upsert Destination component to open configuration window.

4. Start by selecting the Action from the list.

5. Next, select the desired target connection or create one by clicking <New [provider] Connection> menu item from the Target Connection dropdown.

6. Then select a table from the Target Table list or click New button to create a new table based on the source columns.

7. Continue by checking Insert and Update options according to your scenario (e.g. if Update option is unchecked, no updates will be made).

8. Finally, click Map All button to map all columns and then select the Key columns to match the columns on:

   

9. Click OK to save the configuration.

10. Run the package and Azure DevOps data will be merged with the target table in SQL Server, PostgreSQL, or Redshift:

    

11. 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

Actions supported by Azure DevOps Connector

Azure DevOps Connector supports following actions for REST API integration:

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.

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

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Cosmos DB

DropBox

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

Trino

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Google Analytics

HTML Table

Build your own Custom API Connector

Other application integration scenarios for Azure DevOps

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

C#

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC