Skip to content

Commit d22210b

Browse files
committed
note about curated environment names
1 parent e563e4b commit d22210b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/machine-learning/how-to-manage-environments-v2.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: how-to
88
author: ositanachi
99
ms.author: osiotugo
1010
ms.reviewer: larryfr
11-
ms.date: 01/03/2024
11+
ms.date: 04/19/2024
1212
ms.custom: devx-track-azurecli, devplatv2, devx-track-python
1313
---
1414

@@ -77,6 +77,9 @@ You can use these curated environments out of the box for training or deployment
7777

7878
You can see the set of available curated environments in the Azure Machine Learning studio UI, or by using the CLI (v2) via `az ml environment list`.
7979

80+
> [!TIP]
81+
> When working with curated environments in the CLI or SDK, the environment name begins with `AzureML-` followed by the name of the curated environment. When using the Azure Machine Learning studio, they do not have this prefix. The reason for this difference is that the studio UI displays curated and custom environments on separate tabs, so the prefix is not necessary. The CLI and SDK do not have this separation, so the prefix is used to differentiate between curated and custom environments.
82+
8083
## Create a custom environment
8184

8285
You can define an environment from a Docker image, a Docker build context, and a conda specification with Docker image.

0 commit comments

Comments
 (0)