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
@@ -161,15 +161,15 @@ When you [view your usage and quota in the Azure portal](how-to-manage-quotas.md
161
161
162
162
# [Azure CLI](#tab/cli)
163
163
164
-
```bash
164
+
```Azure CLI
165
165
az ml workspace show --name <wsname>--resource-group <rgname>
166
166
```
167
167
168
168
---
169
169
170
-
Look for the userassigned identities in the output. If it's missing, create a new workspace with a userassigned managed identity by following the instructions here: Set up service authentication - Azure Machine Learning | Microsoft Learn
170
+
Look for the user-assigned identities in the output. If it's missing, create a new workspace with a user-assigned managed identity by following the instructions in [Set up authentication between Azure Machine Learning and other services](how-to-identity-based-service-authentication.md).
171
171
172
-
1. Use user assigned managed identity in your job.
172
+
1. Use your user-assigned managed identity in your job.
173
173
174
174
# [Python SDK](#tab/python)
175
175
@@ -199,7 +199,7 @@ When you [view your usage and quota in the Azure portal](how-to-manage-quotas.md
@@ -428,7 +428,7 @@ For a pipeline job, specify `azureml:serverless` as your default compute type to
428
428
You can also set serverless compute as the default compute in Designer.
429
429
430
430
### Configure Serverless Pipeline Jobs with User-Assigned Managed Identity
431
-
When using serverless compute in pipeline jobs, we recommend setting user identity at the individual step level that will be executed on a compute, rather than at the root pipeline level. (While identity setting is supported at both root pipeline and step levels, the steplevel setting takes precedence if both are set. However, for pipelines containing pipeline components, identity must be set on individual steps that will be executed. Identity set at the root pipeline or pipeline component level won't function. Therefore, we suggest setting identity at the individual step level for simplicity.)
431
+
When using serverless compute in pipeline jobs, we recommend setting user identity at the individual step level that will be executed on a compute, rather than at the root pipeline level. (While the identity setting is supported at both root pipeline and step levels, the step-level setting takes precedence if both are set. However, for pipelines containing pipeline components, identity must be set on individual steps that will be executed. Identity set at the root pipeline or pipeline component level won't function. Therefore, we suggest setting identity at the individual step level for simplicity.)
0 commit comments