Skip to content

Commit 7ae86e9

Browse files
authored
Merge pull request #178135 from likebupt/master
update limitation of designer sample pipeline in vnet env
2 parents da59593 + fde9af4 commit 7ae86e9

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

articles/machine-learning/how-to-enable-studio-virtual-network.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
99
ms.reviewer: larryfr
1010
ms.author: jhirono
1111
author: jhirono
12-
ms.date: 07/13/2021
12+
ms.date: 11/01/2021
1313
ms.custom: contperf-fy20q4, tracking-python, security
1414

1515
---
@@ -72,6 +72,13 @@ There's a known issue where the default file store does not automatically create
7272
To avoid this issue, you have two options: 1) Use the default filestore which is automatically created for you doing workspace creation. 2) To bring your own filestore, make sure the filestore is outside of the VNet during workspace creation. After the workspace is created, add the storage account to the virtual network.
7373

7474
To resolve this issue, remove the filestore account from the virtual network then add it back to the virtual network.
75+
76+
### Designer sample pipeline
77+
78+
There's a known issue where user cannot run sample pipeline in Designer homepage. This is the sample dataset used in the sample pipeline is Azure Gloabal dataset, and it cannot satisfy all virtual network environment.
79+
80+
To resolve this issue, you can use a public workspace to run sample pipeline to get to know how to use the designer and then replace the sample dataset with your own dataset in the workspace whithin virtual network.
81+
7582
## Datastore: Azure Storage Account
7683

7784
Use the following steps to enable access to data stored in Azure Blob and File storage:

0 commit comments

Comments
 (0)