Skip to content

Commit 469e0cc

Browse files
committed
Fixed code labels
1 parent daddefa commit 469e0cc

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/machine-learning/how-to-use-serverless-compute.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ When you [view your usage and quota in the Azure portal](how-to-manage-quotas.md
113113

114114
Create a file named hello.yaml with the following content:
115115

116-
```bash
116+
```YAML
117117
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
118118
command: echo "hello world"
119119
environment:
@@ -161,15 +161,15 @@ When you [view your usage and quota in the Azure portal](how-to-manage-quotas.md
161161

162162
# [Azure CLI](#tab/cli)
163163

164-
```bash
164+
```Azure CLI
165165
az ml workspace show --name <wsname> --resource-group <rgname>
166166
```
167167

168168
---
169169

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 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).
171171

172-
1. Use user assigned managed identity in your job.
172+
1. Use your user-assigned managed identity in your job.
173173

174174
# [Python SDK](#tab/python)
175175

@@ -199,7 +199,7 @@ When you [view your usage and quota in the Azure portal](how-to-manage-quotas.md
199199

200200
# [Azure CLI](#tab/cli)
201201

202-
```yaml
202+
```YAML
203203
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
204204
command: echo "hello world"
205205
environment:
@@ -241,7 +241,7 @@ ml_client.create_or_update(job)
241241

242242
# [Azure CLI](#tab/cli)
243243

244-
```yaml
244+
```YAML
245245
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
246246
command: echo "hello world"
247247
environment:
@@ -288,7 +288,7 @@ You can override these defaults. If you want to specify the VM type or number of
288288

289289
# [Azure CLI](#tab/cli)
290290

291-
```bash
291+
```YAML
292292
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
293293
command: echo "hello world"
294294
environment:
@@ -328,7 +328,7 @@ You can override these defaults. If you want to specify the VM type or number of
328328
```
329329

330330
# [Azure CLI](#tab/cli)
331-
```bash
331+
```YAML
332332
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
333333
component: ./train.yml
334334
queue_settings:
@@ -371,7 +371,7 @@ ml_client.create_or_update(job)
371371
```
372372

373373
# [Azure CLI](#tab/cli)
374-
```bash
374+
```YAML
375375
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
376376
command: echo "hello world"
377377
environment:
@@ -428,7 +428,7 @@ For a pipeline job, specify `azureml:serverless` as your default compute type to
428428
You can also set serverless compute as the default compute in Designer.
429429

430430
### 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 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.)
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.)
432432

433433
# [Python SDK](#tab/python)
434434

@@ -446,7 +446,7 @@ pipeline_job = my_pipeline()
446446
pipeline_job.settings.default_compute = "serverless"
447447
```
448448
# [Azure CLI](#tab/cli)
449-
```bash
449+
```YAML
450450
$schema: https://azuremlschemas.azureedge.net/latest/pipelineJob.schema.json
451451
type: pipeline
452452
description: E2E dummy train-score-eval pipeline with registered components

0 commit comments

Comments
 (0)