You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "Validate SSIS packages deployed to Azure | Microsoft Docs"
2
+
title: "Validate SSIS packages deployed to Azure"
3
3
description: Learn how the SSIS Package Deployment Wizard checks packages for known issues that may prevent the packages from running as expected in Azure.
4
-
ms.date: "11/27/2017"
5
-
ms.topic: conceptual
6
-
ms.prod: sql
7
-
ms.prod_service: "integration-services"
8
-
ms.custom: ""
9
-
ms.technology: integration-services
10
4
author: swinarko
11
5
ms.author: sawinark
12
-
ms.reviewer: maghan
6
+
ms.reviewer: maghan, randolphwest
7
+
ms.date: 11/03/2022
8
+
ms.prod: sql
9
+
ms.technology: integration-services
10
+
ms.topic: conceptual
13
11
---
14
12
# Validate SQL Server Integration Services (SSIS) packages deployed to Azure
When you deploy a SQL Server Integration Services (SSIS) project to the SSIS Catalog (SSISDB) on an Azure server, the Package Deployment Wizard adds an additional validation step after the **Review** page. This validation step checks the packages in the project for known issues that may prevent the packages from running as expected in the Azure SSIS Integration Runtime. Then the wizard displays any applicable warnings on the **Validate** page.
21
17
22
-
> [!IMPORTANT]
18
+
> [!IMPORTANT]
23
19
> The validation described in this article occurs when you deploy a project with SQL Server Data Tools (SSDT) version 17.4 or later. To get the latest version of SSDT, see [Download SQL Server Data Tools (SSDT)](../../ssdt/download-sql-server-data-tools-ssdt.md).
24
20
25
21
For more info about the Package Deployment Wizard, see [Deploy Integration Services (SSIS) Projects and Packages](../packages/deploy-integration-services-ssis-projects-and-packages.md).
26
22
27
23
## Validate connection managers
28
24
29
25
The wizard checks certain connection managers for the following issues, which may cause the connection to fail:
26
+
30
27
-**Windows authentication**. If a connection string uses Windows authentication, validation raises a warning. Windows authentication requires additional configuration steps. For more info, see [Connect to data and file shares with Windows Authentication](/azure/data-factory/ssis-azure-connect-with-windows-auth).
31
28
-**File path**. If a connection string contains a hard-coded local file path like `C:\\...`, validation raises a warning. Packages that contain an absolute path may fail.
32
29
-**UNC path**. If a connection string contains a UNC path, validation raises a warning. Packages that contain a UNC path may fail, typically because a UNC path requires Windows authentication to access.
33
30
-**Host name**. If a server property contains host name instead of IP address, validation raises a warning. Packages that contain host name may fail, typically because the Azure virtual network requires the correct DNS configuration to support DNS name resolution.
34
-
-**Provider or driver**. If a provider or driver is not supported, validation raises a warning. Only a small number of built-in providers and drivers are supported at this time.
31
+
-**Provider or driver**. If a provider or driver isn't supported, validation raises a warning. Only a few built-in providers and drivers are supported at this time.
35
32
36
33
The wizard does the following validation checks for the connection managers in the list.
37
34
38
-
| Connection Manager| Windows authentication | File path | UNC path | Host name | Provider or driver |
0 commit comments