Skip to content

Commit 987e449

Browse files
authored
Update how-to-administrate-data-authentication.md
1 parent 99e0138 commit 987e449

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: How to administrate data authentication
33
titleSuffix: Azure Machine Learning
4-
description: Learn how to manage data access and how to authenticate in Azure Machine Learning
4+
description: Learn how to manage data access and how to authenticate in Azure Machine Learning.
55
services: machine-learning
66
ms.service: machine-learning
77
ms.subservice: enterprise-readiness
@@ -18,14 +18,14 @@ ms.custom: engagement-fy23
1818
# Data administration
1919

2020
Learn how to manage data access and how to authenticate in Azure Machine Learning
21-
[!INCLUDE [sdk/cli v2](includes/machine-learning-dev-v2.md)]
21+
[!INCLUDE [sdk/cli v2](includes/machine-learning-dev-v2.md)].
2222

2323
> [!IMPORTANT]
2424
> This article is intended for Azure administrators who want to create the required infrastructure for an Azure Machine Learning solution.
2525
2626
## Credential-based data authentication
2727
In general, credential-based data authentication involves these checks:
28-
* Does the user who is accessing data from the credential-based datastore have been assigned a RBAC role containing `Microsoft.MachineLearningServices/workspaces/datastores/listsecrets/action`?
28+
* Does the user who is accessing data from the credential-based datastore have been assigned an RBAC role containing `Microsoft.MachineLearningServices/workspaces/datastores/listsecrets/action`?
2929
- This permission is required to retrieve credentials from the datastore on behalf of the user.
3030
* Does the stored credential (service principal, account key, or sas token) have access to the data resource?
3131

@@ -34,7 +34,7 @@ In general, credential-based data authentication involves these checks:
3434
In general, identity-based data authentication involves these checks:
3535

3636
* Which user wants to access the resources?
37-
- Depending on the conext the data is being accessed, different types of authentication are available, for example
37+
- Depending on the conext when the data is being accessed, different types of authentication are available, for example
3838
- user identity
3939
- compute managed identity
4040
- workspace managed identity
@@ -52,7 +52,7 @@ In general, identity-based data authentication involves these checks:
5252
- Please find more [Azure built-in roles for storage here](../role-based-access-control/built-in-roles/storage.md).
5353

5454

55-
## Other general checks for authetication
55+
## Other general checks for authentication
5656
* Where does the access come from?
5757
- User: Is the client IP address in the VNet/subnet range?
5858
- Workspace: Is the workspace public, or does it have a private endpoint in a VNet/subnet?
@@ -108,7 +108,7 @@ To secure communication between Azure Machine Learning and Azure Storage Account
108108

109109
### Azure Storage firewall
110110

111-
When an Azure Storage account is located behind a virtual network, the storage firewall can normally be used to allow your client to directly connect over the internet. However, when using studio, your client doesn't connect to the storage account. The Azure Machine Learning service that makes the request connects to the storage account. The IP address of the service isn't documented, and it changes frequently. __Enabling the storage firewall will not allow studio to access the storage account in a VNet configuration__.
111+
When an Azure Storage account is located behind a virtual network, the storage firewall can normally be used to allow your client to directly connect over the internet. However, when using studio, your client doesn't connect to the storage account. The Azure Machine Learning service that makes the request connect to the storage account. The IP address of the service isn't documented, and it changes frequently. __Enabling the storage firewall will not allow studio to access the storage account in a VNet configuration__.
112112

113113
### Azure Storage endpoint type
114114

0 commit comments

Comments
 (0)