Skip to content

Commit 670163e

Browse files
committed
edit pass: machine-learning-data-administration
1 parent 3c083b3 commit 670163e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/machine-learning/how-to-administrate-data-authentication.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,9 @@ In general, identity-based data authentication involves these checks:
5858
## Other general checks for authentication
5959

6060
* Where does the access come from?
61-
- User: Is the client IP address in the virtual network/subnet range?
62-
- Workspace: Is the workspace public, or does it have a private endpoint in a virtual network/subnet?
63-
- Storage: Does the storage allow public access, or does it restrict access through a service endpoint or a private endpoint?
61+
- **User**: Is the client IP address in the virtual network/subnet range?
62+
- **Workspace**: Is the workspace public, or does it have a private endpoint in a virtual network/subnet?
63+
- **Storage**: Does the storage allow public access, or does it restrict access through a service endpoint or a private endpoint?
6464
* What operation will be performed?
6565
- Azure Machine Learning handles create, read, update, and delete (CRUD) operations on a data store/dataset.
6666
- Archive operations on data assets in Azure Machine Learning studio require this RBAC operation: `Microsoft.MachineLearningServices/workspaces/datasets/registered/delete`
@@ -127,8 +127,8 @@ When you use Azure Data Lake Storage Gen1 as a datastore, you can only use POSIX
127127

128128
When you use Azure Data Lake Storage Gen2 as a datastore, you can use both Azure RBAC and POSIX-style access control lists (ACLs) to control data access inside a virtual network.
129129

130-
**To use Azure RBAC**: Follow the steps described in this [Datastore: Azure Storage account](how-to-enable-studio-virtual-network.md#datastore-azure-storage-account) article section. Data Lake Storage Gen2 is based on Azure Storage, so the same steps apply when you use Azure RBAC.
131-
**To use ACLs**: The managed identity of the workspace can be assigned access like any other security principal. For more information, see [Access control lists on files and directories](../storage/blobs/data-lake-storage-access-control.md#access-control-lists-on-files-and-directories).
130+
- **To use Azure RBAC**: Follow the steps described in this [Datastore: Azure Storage account](how-to-enable-studio-virtual-network.md#datastore-azure-storage-account) article section. Data Lake Storage Gen2 is based on Azure Storage, so the same steps apply when you use Azure RBAC.
131+
- **To use ACLs**: The managed identity of the workspace can be assigned access like any other security principal. For more information, see [Access control lists on files and directories](../storage/blobs/data-lake-storage-access-control.md#access-control-lists-on-files-and-directories).
132132

133133
## Next steps
134134

0 commit comments

Comments
 (0)