SSIS migration assessment rules
APPLIES TO: 
Azure Data Factory
Azure Synapse Analytics
When planning a migration of on-premises SSIS to SSIS in Azure Data Factory (ADF) or Synapse Pipelines, assessment will help identify issues with the source SSIS packages that would prevent a successful migration.
Data Migration Assistant (DMA) for Integration Services can perform assessment of your project, and below are full list of potential issues, known as DMA rules as well.
Impact
Connection that contains host name may fail, typically because the Azure virtual network requires the correct configuration to support DNS name resolution.
Recommendation
You can use below options for SSIS Integration runtime to access these resources:
- Join Azure-SSIS IR to a virtual network that connects to on-premises sources
- Migrate your data to Azure and use Azure resource endpoint.
- Use Managed Identity authentication if moving to Azure resources.
- Use self-hosted IR to connect on-premises sources.
Impact
Connection that contains absolute or UNC path may fail
Recommendation
You can use below options for SSIS Integration runtime to access these resources:
- Change to %TEMP%
- Migrate your files to Azure Files
- Join Azure-SSIS IR to a virtual network that connects to on-premises sources.
- Use self-hosted IR to connect on-premises sources.
Impact
If a connection string uses Windows authentication, it may fail. Windows authentication requires additional configuration steps in Azure.
Recommendation
There are four methods to access data stores Windows authentication in Azure SSIS integration runtime:
- Set up an activity-level execution context
- Set up a catalog-level execution context
- Persist credentials via cmdkey command
- Mount drives at package execution time (non-persistent)
Impact
Azure-SSIS IR only includes built-in providers or drivers by default. Without customization to install the provider or driver, the connection may fail.
Recommendation
Customize Azure-SSIS integration runtime to install non built-in provider or driver.
Impact
If you use SSIS in Azure Data Factory (ADF) and want to connect to Azure Analysis Services (AAS) instance, you cannot use an account with Multi-Factor Authentication (MFA) enabled.
Recommendation
Use an account that doesn't require any interactivity/MFA or a service principal instead.
AdditionalInformation
Configuration of the Analysis Services Connection Manager
Impact
Connection Manager using Windows environment variable is discovered.
Recommendation
You can use below methods to have Windows environment variables working in SSIS Integration runtime:
- Customize SSIS integration runtime setup with Windows environment variables.
- Use Package or Project Parameter.
Recommendation
Use latest Microsoft OLE DB Driver
Impact
The component is only supported in Azure SSIS integration runtime enterprise edition.
Recommendation
Configure Azure SSIS integration runtime to enterprise edition.
Impact
ORC and Parquet file format need JRE, which isn't by default installed in Azure SSIS integration runtime.
Recommendation
Install compatible JRE by customize setup for the Azure-SSIS integration runtime.
Impact
Azure SSIS Integration Runtime isn't by default enabled with third party components. Third party component may fail.
Recommendation
Contact the third party to get an SSIS Integration runtime compatible version.
For in-house or open source component, customize Azure-SSIS integration runtime to install necessary SQL Server 2017 compatible components.
Recommendation
Recommend to use Flexible File source or destination, which has more advanced functions than Azure Blob.
Impact
Azure SSIS integration time is provisioned with built-in log providers by default only, customize log provider may fail.
Recommendation
Customize Azure-SSIS integration runtime to install non built-in provider or driver.
Impact
Azure-SSIS Integration Runtime might not be able to launch your executable(s) with absolute or UNC path.
Recommendation
You can use below options for SSIS Integration runtime to launch your executable(s):
- Migrate your executable(s) to Azure Files.
- Join Azure-SSIS IR to a virtual network that connects to on-premises sources.
- If necessary, customize setup script to install your executable(s) in advance when starting IR.
Impact
Package with absolute or UNC configuration path may fail in Azure SSIS Integration Runtime.
Recommendation
You can use below options for SSIS Integration runtime to access these resources:
- Migrate your files to Azure Files
- Join Azure-SSIS IR to a virtual network that connects to on-premises sources.
- Use self-hosted IR to connect on-premises sources.
Impact
Registry entry in package configuration may fail in Azure SSIS Integration Runtime.
Recommendation
Use other package configuration types. XML configuration file is recommended.
Additional Information
Impact
Package encrypted with user key isn't supported in Azure SSIS Integration Runtime.
Recommendation
You can use below options:
- Change the package protection level to "Encrypt All With Password" or "Encrypt Sensitive With Password".
- Keep or change the package protection level to "Encrypt Sensitive With User Key", override connection manager property during package execution
Additional Information