You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/advocates/intro-azure-machine-learning-auth/includes/1-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ Azure Machine Learning (ML) is a cloud service for managing machine learning pro
2
2
3
3
An Azure Machine Learning workspace is a centralized environment for managing machine learning projects, allowing collaboration and organization of experiments, datasets, models, and deployments. The workspace provides tools for creating, training, and deploying models, along with managing compute resources and data assets. As a cloud operations professional, you need to manage Azure Machine Learning workspace authentication and authorization.
Copy file name to clipboardExpand all lines: learn-pr/advocates/intro-azure-machine-learning-auth/includes/3-manage-access-azure-machine-learning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ Azure role-based access control (Azure RBAC) is used to scope the level of acces
2
2
3
3
Azure Machine Learning applies the same principle for authorization as other Azure resources. You use Azure role-based access control (Azure RBAC) to manage access giving users the ability to create new resources or use existing ones. Users in your Microsoft Entra ID are assigned specific roles, which grant access to resources. Azure provides both built-in roles and the ability to create custom roles for Azure Machine Learning.
4
4
5
-
Default Roles
5
+
## Default Roles ##
6
6
7
7
The roles related to Azure Machine Learning workspaces are as follows.
Copy file name to clipboardExpand all lines: learn-pr/advocates/intro-azure-machine-learning-auth/includes/4-authentication-between-azure-machine-learning-other-azure-services.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,20 +14,18 @@ Just like when users access the Azure Machine Learning workspace, Azure services
14
14
15
15
Once a workspace is created with SAI identity type, it can be updated to SAI+UAI, but not back from SAI+UAI to SAI. You may assign multiple user-assigned identities to the same workspace, or even assign additional user-assigned identities in addition to a system-assigned identity.
16
16
17
-
**System-assigned versus User-assigned identities**
17
+
### System-assigned versus User-assigned identities ###
18
18
19
19
Choosing between system-assigned and user-assigned identities depends on your specific needs and how your company manages Azure resources:
20
20
21
21
**System-assigned identities** are created and managed by Azure for a specific resource. When a resource is deleted, its associated system-assigned identity is also deleted, ensuring that the identity lifecycle is tightly coupled with the resource it belongs to. This type of identity is ideal for scenarios where the identity only needs to be used by a single resource, providing simplicity and reducing the administrative overhead since Azure manages the identity's credentials.
22
22
23
23
**User-assigned identities** are created independently of any specific resource and can be shared across multiple resources. This makes them highly versatile for applications that require a consistent identity across different resources, enabling easier management of permissions and access controls. User-assigned identities persist even after the resources using them are deleted, allowing for greater flexibility in redeploying and reusing identities.
24
24
25
-
**User-assigned managed identity specific configuration**
25
+
### User-assigned managed identity specific configuration ###
26
26
27
27
When you create an Azure Machine Learning workspace with the default settings (Azure Storage, Azure Container Registry, and Azure Key Vault are created for you), the system-assigned managed identity is configured with appropriate permissions. If instead you change to a user-assigned identity (or if you use existing resources for Storage, Key Vault, etc.) you need to set up the following access to that account:
@@ -56,7 +54,7 @@ To assign the Azure Machine Learning workspace permissions to an Azure resource,
56
54
57
55
1. Click Review + assign twice to confirm the assignment.
58
56
59
-
Compute-related identities
57
+
### Compute-related identities ###
60
58
61
59
Compute-related identities are used in the following scenarios:
62
60
@@ -65,7 +63,7 @@ Compute-related identities are used in the following scenarios:
65
63
66
64
In both cases, the default managed identity is the system-assigned managed identity or the first user-assigned managed identity for that resource. Also, both Azure Machine Learning compute clusters and Kubernetes cluster support only one system-assigned identity or multiple user-assigned identities, not both concurrently. Finally, the scenarios in this unit don't consider if you apply an identity to access resources from within the code for a submitted job. In that case, the identity from within the code is used for access.
67
65
68
-
Data Storage
66
+
### Data Storage ###
69
67
70
68
When you create a datastore that uses identity-based data access, your Azure account is used to confirm you have permission to access the storage service. In the identity-based data access scenario, no authentication credentials are saved. Only the storage account information is stored in the datastore.
Copy file name to clipboardExpand all lines: learn-pr/advocates/intro-azure-machine-learning-auth/includes/6-summary.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
This module provides an overview of authentication and authorization for Azure Machine Learning. You learned that Microsoft Entra ID is used for most scenarios, how to provide access to workspaces to users, and how to plan for authentication between Azure Machine Learning and other Azure resources.
2
2
3
-
# Further reading/learning #
3
+
##Further reading/learning##
4
4
5
5
-[Set up authentication for Azure Machine Learning resources and workflows](/azure/machine-learning/how-to-setup-authentication)
6
6
-[Manage access to Azure Machine Learning workspaces](/azure/machine-learning/how-to-assign-roles)
0 commit comments