Skip to content

Commit b55e28d

Browse files
authored
Merge pull request #4095 from douglaslMS/ssis-everest-winauth
Restructured per email discussion with PM.
2 parents 773fa9d + c3998c6 commit b55e28d

1 file changed

Lines changed: 42 additions & 41 deletions

File tree

docs/integration-services/lift-shift/ssis-azure-connect-with-windows-auth.md

Lines changed: 42 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Connect to on-premises data sources and Azure file shares with Windows Authentication | Microsoft Docs"
3-
ms.date: "09/25/2017"
3+
ms.date: "11/27/2017"
44
ms.topic: "article"
55
ms.prod: "sql-non-specified"
66
ms.prod_service: "integration-services"
@@ -16,43 +16,11 @@ manager: "craigg"
1616
ms.workload: "Inactive"
1717
---
1818
# Connect to on-premises data sources and Azure file shares with Windows Authentication
19-
This article describes how to configure the SSIS Catalog on Azure SQL Database to run packages that use Windows Authentication to connect to on-premises data sources and Azure file shares.
19+
This article describes how to configure the SSIS Catalog on Azure SQL Database to run packages that use Windows Authentication to connect to on-premises data sources and Azure file shares. You can use Windows authentication to connect to data sources in the same virtual network as the Azure SSIS Integration Runtime, both on premises and on Azure virtual machines and in Azure Files.
2020

2121
The domain credentials that you provide when you follow the steps in this article apply to all package executions on the SQL Database instance until you change or remove the credentials.
2222

23-
## Connect to on-premises data sources
24-
25-
### Prerequisite
26-
Before you set up domain credentials for Windows Authentication, check whether a non-domain-joined computer can connect to your on-premises data source in `runas` mode.
27-
28-
#### Connecting to SQL Server
29-
To check whether you can connect to an on-premises SQL Server, do the following things:
30-
31-
1. To run this test, find a non-domain-joined computer.
32-
33-
2. On the non-domain-joined computer, run the following command to start SQL Server Management Studio (SSMS) with the domain credentials that you want to use:
34-
35-
```cmd
36-
runas.exe /netonly /user:<domain>\<username> SSMS.exe
37-
```
38-
39-
3. From SSMS, check whether you can connect to the on-premises SQL Server that you want to use.
40-
41-
#### Connecting to a file share
42-
To check whether you can connect to an on-premises file share, do the following things:
43-
44-
1. To run this test, find a non-domain-joined computer.
45-
46-
2. On the non-domain-joined computer, run the following command. This command opens a command prompt window with the domain credentials that you want to use, and then tests connectivity to the file share by getting a directory listing.
47-
48-
```cmd
49-
runas.exe /netonly /user:<domain>\<username> cmd.exe
50-
dir \\fileshare
51-
```
52-
53-
3. Check whether the directory listing is returned for the on-premises file share that you want to use.
54-
55-
### Provide domain credentials
23+
## Provide domain credentials for Windows Authentication
5624
To provide domain credentials that let packages use Windows Authentication to connect to on-premises data sources, do the following things:
5725

5826
1. With SQL Server Management Studio (SSMS) or another tool, connect to the SQL Database that hosts the SSIS Catalog database (SSISDB). For more info, see [Connect to the SSISDB Catalog database on Azure](ssis-azure-connect-to-catalog-database.md).
@@ -64,6 +32,7 @@ To provide domain credentials that let packages use Windows Authentication to co
6432
```sql
6533
catalog.set_execution_credential @user='<your user name>', @domain='<your domain name>', @password='<your password>'
6634
```
35+
6736
4. Run your SSIS packages. The packages use the credentials that you provided to connect to on-premises data sources with Windows Authentication.
6837

6938
### View domain credentials
@@ -94,24 +63,56 @@ To clear and remove the credentials that you provided as described in this artic
9463
catalog.set_execution_credential @user='', @domain='', @password=''
9564
```
9665

97-
## Connect to file shares
98-
You can use Windows authentication to connect to file shares in the same virtual network as the Azure SSIS Integration Runtime, both on premises and on Azure virtual machines and in Azure Files. For more info about Azure Files, see [Azure Files](https://azure.microsoft.com/services/storage/files/).
66+
## Connect to an on-premises SQL Server
67+
To check whether you can connect to an on-premises SQL Server, do the following things:
68+
69+
1. To run this test, find a non-domain-joined computer.
70+
71+
2. On the non-domain-joined computer, run the following command to start SQL Server Management Studio (SSMS) with the domain credentials that you want to use:
72+
73+
```cmd
74+
runas.exe /netonly /user:<domain>\<username> SSMS.exe
75+
```
76+
77+
3. From SSMS, check whether you can connect to the on-premises SQL Server that you want to use.
78+
79+
## Connect to an on-premises file share
80+
To check whether you can connect to an on-premises file share, do the following things:
81+
82+
1. To run this test, find a non-domain-joined computer.
83+
84+
2. On the non-domain-joined computer, run the following command. This command opens a command prompt window with the domain credentials that you want to use, and then tests connectivity to the file share by getting a directory listing.
85+
86+
```cmd
87+
runas.exe /netonly /user:<domain>\<username> cmd.exe
88+
dir \\fileshare
89+
```
90+
91+
3. Check whether the directory listing is returned for the on-premises file share that you want to use.
9992

100-
To connect to a file share on an Azure virtual machine or Azure file share, do the following things:
93+
## Connect to a file share on an Azure VM
94+
To connect to a file share on an Azure virtual machine, do the following things:
10195

10296
1. With SQL Server Management Studio (SSMS) or another tool, connect to the SQL Database that hosts the SSIS Catalog database (SSISDB).
10397

10498
2. With SSISDB as the current database, open a query window.
10599

106100
3. Run the `catalog.set_execution_credential` stored procedure as described in the following options:
107101

108-
a. To connect to a file share on an Azure virtual machine, run the following stored procedure:
109-
110102
```sql
111103
catalog.set_execution_credential @domain = N'.', @user = N'username of local account on Azure virtual machine', @password = N'password'
112104
```
113105

114-
b. To connect to an Azure file share (that is, in Azure Files), run the following stored procedure:
106+
## Connect to a file share in Azure Files
107+
For more info about Azure Files, see [Azure Files](https://azure.microsoft.com/services/storage/files/).
108+
109+
To connect to a file share on an Azure file share, do the following things:
110+
111+
1. With SQL Server Management Studio (SSMS) or another tool, connect to the SQL Database that hosts the SSIS Catalog database (SSISDB).
112+
113+
2. With SSISDB as the current database, open a query window.
114+
115+
3. Run the `catalog.set_execution_credential` stored procedure as described in the following options:
115116

116117
```sql
117118
catalog.set_execution_credential @domain = N'Azure', @user = N'<storage-account-name>', @password = N'<storage-account-key>'

0 commit comments

Comments
 (0)