# Deploy CData SSIS Components on Azure Data Factory **URL:** \ **Category:** Getting started\ **Tags:** article, ssis, azure\ **Created:** [March 21, 2023, 9:56pm UTC](https://community.cdata.com/t/deploy-cdata-ssis-components-on-azure-data-factory/78 "2023-03-21T21:56:15Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jerodj-cdata](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/jerodj-cdata/32/7_2.png) [@jerodj-cdata](https://community.cdata.com/u/jerodj-cdata)\ **Post date:** [March 21, 2023, 9:56pm UTC](https://community.cdata.com/t/deploy-cdata-ssis-components-on-azure-data-factory/78/1 "2023-03-21T21:56:15Z")
Azure Data Factory is a scalable, trusted, cloud-based solution for building automated data integration solutions with a visual, drag-and-drop UI. Moving on-premises SSIS workloads to Azure can reduce the operational costs of managing infrastructure, increase availability with the ability to specify multiple nodes per cluster and deliver rapid scalability. With the release of Azure Data Factory V2 Integration Runtimes (ADFv2 IR), deployment to the Azure cloud is now possible for SSIS projects that use CData Components. In this article, we walk through the steps for deploying CData SSIS Components to Azure. ## Deployment Prerequisites * * * The deployment of CData Components requires the following: - **CData SSIS Component License and RTK** To deploy to the Azure cloud, you will need a license (full or trial) and a Runtime Key ( **RTK** ) for each of the CData components being deployed. For more information on obtaining this license (or a trial), [contact our sales team](https://www.cdata.com/company/contact.aspx). - **Azure Subscription** This can be managed in the Azure Portal. More information on Azure Subscriptions is available from [the Microsoft website](https://azure.microsoft.com/en-us/pricing/purchase-options/?v=18.19). - **AzureRM PowerShell 6.2.0 or higher** With PowerShellGet you may install using Install-Module -Name AzureRM -AllowClobber, or by using a .msi installer from [Microsoft Releases](https://github.com/Azure/azure-powershell/releases). You can find other detailed instructions on obtaining the supported Azure PowerShell from [Microsoft’s Web Documentation](https://docs.microsoft.com/en-us/powershell/azure/install-azurerm-ps). - **SSMS 2012 or higher** We recommend using the [latest version](https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms) available from Microsoft. ## Deployment Guide * * * ### Overview - Create an Azure Resource Group - Create an Azure SQL Server (logical server) - Run CData PowerShell Script AzureDeploy.ps1 to set up and create an Integration Runtime - Deploy SSIS Project From Visual Studio to Azure - Use SSMS to manage and execute a deployed project ### Step-by-Step Guide 1. Create an Azure SQL Server (logical server) and Resource Group or reuse an existing one. If the existing SQL Server already has an Integration Runtime (and SSISDB), then you may overwrite it by specifying its name with the -InterationRuntimeName parameter. Each SQL Server may only have one Integration Runtime. 2. Allow IP addresses on the SQL Server Firewall as necessary. 3. Run the AzureDeploy.ps1 PowerShell script, and provide the required parameters. The default location (example Salesforce 2018) is C:\Program Files\CData\CData SSIS Components for Salesforce 2018\lib You may use powershell –ExecutionPolicy Bypass to bypass execution policy restrictions for the current session. 4. Log into Azure in the generated pop-up. 5. After logging into Azure, the script creates the resources necessary for deployment and starts the Integration Runtime. 6. You are now ready to deploy your SSIS Package. In Visual Studio, right-click the project → Deploy. ### Managing the Project in SSMS By default, connection settings with sensitive information (passwords, security tokens, etc.) are redacted when deploying to Azure. You may provide this information again through SSMS. 1. Connect to the Azure SQL Server In Options → Connection Properties, set the ‘Connect to Database’ field to  **SSISDB**. 2. Configure the SSIS project in the _Integration Services Catalog_ (right-click the project → Configure). _(Note: If you do not see Integration Services Catalogs, you may need to upgrade your SSMS version or set ‘SSISDB’ in step 1.)_ 3. Execute the project (right-click the project → Execute). From here, the project is executed in the configured Azure Data Factory, and the results of executions can be viewed by right-clicking the project → Reports → All Executions. ---
**Author:** ![Hartless](https://avatars.discourse-cdn.com/v4/letter/h/7feea3/32.png) [@Hartless](https://community.cdata.com/u/Hartless)\ **Post date:** [May 10, 2024, 10:54pm UTC](https://community.cdata.com/t/deploy-cdata-ssis-components-on-azure-data-factory/78/2 "2024-05-10T22:54:39Z")
I followed the instructions and everything seems to be set up correctly. However, when I execute the SSIS package via the data factory pipeline, I am receiving a message that there are errors during validation because the classes from the CData components are not registered. The output from the install log states that the DEPLOY succeeded. **Copying files to “C:\Program Files\Microsoft SQL Server\140\DTS\Connections\” C:CData.SSIS2017.D365BusinessCentral.dll 1 File(s) copied Copying files to “C:\Program Files\Microsoft SQL Server\140\DTS\PipelineComponents\” C:CData.SSIS2017.D365BusinessCentral.dll 1 File(s) copied Copying files to “C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Connections\” C:CData.SSIS2017.D365BusinessCentral.dll 1 File(s) copied Copying files to “C:\Program Files (x86)\Microsoft SQL Server\140\DTS\PipelineComponents\” C:CData.SSIS2017.D365BusinessCentral.dll 1 File(s) copied DEPLOY succeeded.** I have recreated the Integration Runtime multiple times and it always succeeds and starts only to have the component fail during validation. The project runs perfect from Visual Studio. Is there something else I can do to debug this issue? I am not sure what else to do Thanks, --Steve