Skip to content

Commit 4d37bad

Browse files
authored
Update how-to-administrate-data-authentication.md
1 parent 8f31b45 commit 4d37bad

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,9 @@ Learn how to manage data access and how to authenticate in Azure Machine Learnin
2727
In general, credential-based data authentication involves these checks:
2828
* 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.
30+
- Built in roles that contain this permission already is the [Contributor](../role-based-access-control/built-in-roles/general.md#contributor), the Azure AI Developer or the [AML Data Scientist](../role-based-access-control/built-in-roles/ai-machine-learning.md#azureml-data-scientist) roles. Alternatively, if a custom role is being applied then we need to ensure that this permission is added to that custom role.
31+
- You must know *which* specific user is trying to access the data. It can be a real user with user identity or a compute with compute MSI etc., you can check the section [Scenarios and authentication options](#scenarios-and-authentication-options) to identify what is the identity that you need to add permission for.
32+
3033
* Does the stored credential (service principal, account key, or sas token) have access to the data resource?
3134

3235

0 commit comments

Comments
 (0)