Skip to content

Commit 3b2d943

Browse files
committed
modify pictures and text
1 parent 2cde149 commit 3b2d943

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed
-565 Bytes
Loading
-2.39 KB
Loading
1.82 KB
Loading

articles/data-factory/tutorial-deploy-ssis-packages-azure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ On the **Add package store** pane, complete the following steps.
172172
1. For **Package store linked service**, select your existing linked service that stores the access information for file system/Azure Files/Azure SQL Managed Instance where your packages are deployed or create a new one by selecting **New**. On the **New linked service** pane, complete the following steps.
173173

174174
> [!NOTE]
175-
> You can use either **Azure File Storage** or **File System** linked services to access Azure Files. If you use **Azure File Storage** linked service, Azure-SSIS IR package store supports only **Basic** (not **Account key** nor **SAS URI**) authentication method for now. To use **Basic** authentication on **Azure File Storage** linked service, you can append `?feature.upgradeAzureFileStorage=false` to the ADF portal URL in your browser. Alternatively, you can use **File System** linked service to access Azure Files instead.
175+
> You can use either **Azure File Storage** or **File System** linked services to access Azure Files. If you use **Azure File Storage** linked service, Azure-SSIS IR package store supports only **Basic** (not **Account key** nor **SAS URI**) authentication method for now.
176176
177177
![Deployment settings for linked services](./media/tutorial-create-azure-ssis-runtime-portal/deployment-settings-linked-service.png)
178178

@@ -183,8 +183,8 @@ On the **Add package store** pane, complete the following steps.
183183
1. For **Type**, select **Azure File Storage**, **Azure SQL Managed Instance**, or **File System**.
184184

185185
1. You can ignore **Connect via integration runtime**, since we always use your Azure-SSIS IR to fetch the access information for package stores.
186-
187-
1. If you select **Azure File Storage**, you can choose **Connection string** or **Azure Key Vault** where it's stored as a secret. If you choose **Connection string**, complete the following steps.
186+
187+
1. If you select **Azure File Storage**, for **Authentication method**, select **Basic**, and then complete the following steps.
188188

189189
1. For **Account selection method**, select **From Azure subscription** or **Enter manually**.
190190

@@ -197,7 +197,7 @@ On the **Add package store** pane, complete the following steps.
197197
1. Select **Connection string** or your **Azure Key Vault** where it's stored as a secret.
198198

199199
1. If you select **Connection string**, complete the following steps.
200-
1. For **Account selection method**, if you choose **From Azure subscription**, select the relevant **Azure subscription**, **Server name**, and **Database name**. If you choose Enter manually, complete the following steps.
200+
1. For **Account selection method**, if you choose **From Azure subscription**, select the relevant **Azure subscription**, **Server name**, **Endpoint type** and **Database name**. If you choose **Enter manually**, complete the following steps.
201201
1. For **Fully qualified domain name**, enter `<server name>.<dns prefix>.database.windows.net` or `<server name>.public.<dns prefix>.database.windows.net,3342` as the private or public endpoint of your Azure SQL Managed Instance, respectively. If you enter the private endpoint, **Test connection** isn't applicable, since ADF UI can't reach it.
202202

203203
1. For **Database name**, enter `msdb`.

0 commit comments

Comments
 (0)