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: articles/machine-learning/how-to-identity-based-service-authentication.md
+30-48Lines changed: 30 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -276,6 +276,36 @@ During cluster creation or when editing compute cluster details, in the **Advanc
276
276
277
277
---
278
278
279
+
### Kubernetes Compute Cluster
280
+
281
+
> [!NOTE]
282
+
> Azure Machine Learning kubernetes clusters support only **one system-assigned identity** or **one multiple user-assigned identities**, not both concurrently.
283
+
284
+
The **default managed identity** is the system-assigned managed identity or the first user-assigned managed identity.
285
+
286
+
287
+
During a run there are two applications of an identity:
288
+
289
+
1. The system uses an identity to set up the user's storage mounts, container registry, and datastores.
290
+
291
+
* In this case, the system will use the default-managed identity.
292
+
293
+
1. You apply an identity to access resources from within the code for a submitted job:
294
+
295
+
* In the case of kubernetes compute clusters, the ManagedIdentityCredential object should be passed **without any client_id**.
296
+
297
+
For example, to retrieve a token for a datastore with the default-managed identity:
To configure a kubernetes compute cluster, make sure that it has the [necessary AML extension deployed in it](https://learn.microsoft.com/azure/machine-learning/how-to-deploy-kubernetes-extension?view=azureml-api-2&tabs=deploy-extension-with-cli) and follow the documentation on [how to attach the kubernetes compute cluster to your AML workspace](https://learn.microsoft.com/azure/machine-learning/how-to-attach-kubernetes-to-workspace?view=azureml-api-2&tabs=cli).
306
+
307
+
---
308
+
279
309
### Data storage
280
310
281
311
When you create a datastore that uses **identity-based data access**, your Azure account ([Microsoft Entra token](/azure/active-directory/fundamentals/active-directory-whatis)) 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.
@@ -413,54 +443,6 @@ The following steps outline how to set up data access with user identity for tra
413
443
> [!IMPORTANT]
414
444
> During job submission with authentication with user identity enabled, the code snapshots are protected against tampering by checksum validation. If you have existing pipeline components and intend to use them with authentication with user identity enabled, you might need to re-upload them. Otherwise the job may fail during checksum validation.
415
445
416
-
### Access data for training jobs on AKS clusters using user identity
417
-
When training on Azure Kubernetes Service (AKS) clusters, the authentication to dependent azure resources works differently.
418
-
The following steps outline how to set up data access with a given managed identity for training jobs on AKS clusters:
419
-
420
-
1. Firstly, create and attach the [Azure Kubernetes Cluster to your Azure Machine Learning Workspace](https://learn.microsoft.com/azure/machine-learning/how-to-attach-kubernetes-to-workspace?view=azureml-api-2&tabs=sdk#how-to-attach-a-kubernetes-cluster-to-azure-machine-learning-workspace).
421
-
422
-
1. Ensure that the kubernetes cluster has an [assigned managed identity](https://learn.microsoft.com/azure/machine-learning/how-to-attach-kubernetes-to-workspace?view=azureml-api-2&tabs=sdk#assign-managed-identity) and that the identity has the necessary [azure roles assigned to it](https://learn.microsoft.com/azure/machine-learning/how-to-attach-kubernetes-to-workspace?view=azureml-api-2&tabs=sdk#assign-azure-roles-to-managed-identity).
423
-
424
-
1. When submitting the job, make sure to provide the managed identity of the compute **without specifying the client_id** in the parameters:
0 commit comments