Open and save files on premises and in Azure with SSIS packages deployed in Azure

APPLIES TO: Azure Data Factory Azure Synapse Analytics

This article describes how to open and save files on premises and in Azure when you lift and shift SSIS packages that use local file systems into SSIS in Azure.

Save temporary files

If you need to store and process temporary files during a single package execution, packages can use the current working directory (.) or temporary folder (%TEMP%) of your Azure-SSIS Integration Runtime nodes.

Use on-premises file shares

To continue to use on-premises file shares when you lift and shift packages that use local file systems into SSIS in Azure, do the following things:

  1. Transfer files from local file systems to on-premises file shares.

  2. Join the on-premises file shares to an Azure virtual network.

  3. Join your Azure-SSIS IR to the same virtual network. For more info, see Join an Azure-SSIS integration runtime to a virtual network.

  4. Connect your Azure-SSIS IR to the on-premises file shares inside the same virtual network by setting up access credentials that use Windows authentication. For more info, see Connect to data and file shares with Windows Authentication.

  5. Update local file paths in your packages to UNC paths pointing to on-premises file shares. For example, update C:\abc.txt to \\<on-prem-server-name>\<share-name>\abc.txt.

Use Azure file shares

To use Azure Files when you lift and shift packages that use local file systems into SSIS in Azure, do the following things:

  1. Transfer files from local file systems to Azure Files. For more info, see Azure Files.

  2. Connect your Azure-SSIS IR to Azure Files by setting up access credentials that use Windows authentication. For more info, see Connect to data and file shares with Windows Authentication.

  3. Update local file paths in your packages to UNC paths pointing to Azure Files. For example, update C:\abc.txt to \\<storage-account-name>.file.core.windows.net\<share-name>\abc.txt.

Next steps