Skip to content

Commit ce4cc6a

Browse files
Merge pull request #272611 from sdgilley/sdg-freshness
freshness update what is a workspace
2 parents 078b5b4 + e16b524 commit ce4cc6a

File tree

1 file changed

+24
-16
lines changed

1 file changed

+24
-16
lines changed

articles/machine-learning/concept-workspace.md

Lines changed: 24 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
ms.author: deeikele
1111
author: deeikele
1212
ms.reviewer: sgilley
13-
ms.date: 03/13/2023
13+
ms.date: 04/18/2024
1414
monikerRange: 'azureml-api-2 || azureml-api-1'
1515
#Customer intent: As a data scientist, I want to understand the purpose of a workspace for Azure Machine Learning.
1616
---
@@ -24,7 +24,7 @@ Ready to get started? [Create a workspace](#create-a-workspace).
2424

2525
## Tasks performed within a workspace
2626

27-
For machine learning teams, the workspace is a place to organize their work. Below are some of the tasks you can start from a workspace:
27+
For machine learning teams, the workspace is a place to organize their work. Here are some of the tasks you can start from a workspace:
2828

2929
+ [Create jobs](how-to-train-model.md) - Jobs are training runs you use to build your models. You can group jobs into [experiments](how-to-log-view-metrics.md) to compare metrics.
3030
+ [Author pipelines](concept-ml-pipelines.md) - Pipelines are reusable workflows for training and retraining your model.
@@ -45,13 +45,13 @@ Besides grouping your machine learning results, workspaces also host resource co
4545

4646
## Organizing workspaces
4747

48-
For machine learning team leads and administrators, workspaces serve as containers for access management, cost management and data isolation. Below are some tips for organizing workspaces:
48+
For machine learning team leads and administrators, workspaces serve as containers for access management, cost management, and data isolation. Here are some tips for organizing workspaces:
4949

5050
+ **Use [user roles](how-to-assign-roles.md)** for permission management in the workspace between users. For example a data scientist, a machine learning engineer or an admin.
5151
+ **Assign access to user groups**: By using Microsoft Entra user groups, you don't have to add individual users to each workspace, and to other resources the same group of users requires access to.
5252
+ **Create a workspace per project**: While a workspace can be used for multiple projects, limiting it to one project per workspace allows for cost reporting accrued to a project level. It also allows you to manage configurations like datastores in the scope of each project.
5353
+ **Share Azure resources**: Workspaces require you to create several [associated resources](#associated-resources). Share these resources between workspaces to save repetitive setup steps.
54-
+ **Enable self-serve**: Pre-create and secure [associated resources](#associated-resources) as an IT admin, and use [user roles](how-to-assign-roles.md) to let data scientists create workspaces on their own.
54+
+ **Enable self-serve**: Precreate and secure [associated resources](#associated-resources) as an IT admin, and use [user roles](how-to-assign-roles.md) to let data scientists create workspaces on their own.
5555
+ **Share assets**: You can share assets between workspaces using [Azure Machine Learning registries](how-to-share-models-pipelines-across-workspaces-with-registries.md).
5656

5757
## How is my content stored in a workspace?
@@ -60,33 +60,41 @@ Your workspace keeps a history of all training runs, with logs, metrics, output,
6060

6161
## Associated resources
6262

63-
When you create a new workspace, you're required to bring other Azure resources to store your data. If not provided by you, these resources will automatically be created by Azure Machine Learning.
63+
When you create a new workspace, you're required to bring other Azure resources to store your data. If not provided by you, these resources are automatically be created by Azure Machine Learning.
6464

6565
+ [Azure Storage account](https://azure.microsoft.com/services/storage/). Stores machine learning artifacts such as job logs. By default, this storage account is used when you upload data to the workspace. Jupyter notebooks that are used with your Azure Machine Learning compute instances are stored here as well.
6666

6767
> [!IMPORTANT]
68-
> To use an existing Azure Storage account, it can't be of type BlobStorage, a premium account (Premium_LRS and Premium_GRS) and cannot have a hierarchical namespace (used with Azure Data Lake Storage Gen2). You can use premium storage or hierarchical namespace as additional storage by [creating a datastore](how-to-datastore.md).
68+
> You *can't* use an existing Azure Storage account if it is:
69+
> * An account of type BlobStorage
70+
> * A premium account (Premium_LRS and Premium_GRS)
71+
> * An account with hierarchical namespace (used with Azure Data Lake Storage Gen2).
72+
>
73+
> You can use premium storage or hierarchical namespace as additional storage by [creating a datastore](how-to-datastore.md).
74+
>
6975
> Do not enable hierarchical namespace on the storage account after upgrading to general-purpose v2.
76+
>
7077
> If you bring an existing general-purpose v1 storage account, you may [upgrade this to general-purpose v2](../storage/common/storage-account-upgrade.md) after the workspace has been created.
7178
72-
+ [Azure Container Registry](https://azure.microsoft.com/services/container-registry/). Stores created docker containers, when you build custom environments via Azure Machine Learning. Scenarios that trigger creation of custom environments include AutoML when deploying models and data profiling.
79+
+ [Azure Container Registry (ACR)](https://azure.microsoft.com/services/container-registry/). Stores created docker containers, when you build custom environments via Azure Machine Learning. Deploying AutoML models and data profile will also trigger creation of custom environments.
7380

74-
> [!NOTE]
75-
> Workspaces can be created without Azure Container Registry as a dependency if you do not have a need to build custom docker containers. To read container images, Azure Machine Learning also works with external container registries. Azure Container Registry is automatically provisioned when you build custom docker images. Use Azure RBAC to prevent customer docker containers from being built.
81+
Workspaces *can* be created without ACR as a dependency if you do not have a need to build custom docker containers. Azure Machine Learning can read from external container registries.
7682

77-
> [!NOTE]
78-
> If your subscription setting requires adding tags to resources under it, Azure Container Registry (ACR) created by Azure Machine Learning will fail, since we cannot set tags to ACR.
83+
ACR will automatically be provisioned when you build custom docker images. Use [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md) to prevent customer docker containers from being built.
7984

80-
+ [Azure Application Insights](https://azure.microsoft.com/services/application-insights/). Helps you monitor and collect diagnostic information from your inference endpoints.
85+
> [!IMPORTANT]
86+
> If your subscription setting requires adding tags to resources under it, ACR created by Azure Machine Learning will fail, since we cannot set tags to ACR.
87+
88+
+ [Azure Application Insights](https://azure.microsoft.com/services/application-insights/). Helps you monitor and collect diagnostic information from your inference endpoints.
8189
:::moniker range="azureml-api-2"
8290
For more information, see [Monitor online endpoints](how-to-monitor-online-endpoints.md).
8391
:::moniker-end
8492

85-
+ [Azure Key Vault](https://azure.microsoft.com/services/key-vault/). Stores secrets that are used by compute targets and other sensitive information that's needed by the workspace.
93+
+ [Azure Key Vault](https://azure.microsoft.com/services/key-vault/). Stores secrets that are used by compute targets and other sensitive information that the workspace needs.
8694

8795
## Create a workspace
8896

89-
There are multiple ways to create a workspace. To get started use one of the following options:
97+
There are multiple ways to create a workspace. To get started, use one of the following options:
9098

9199
* The [Azure Machine Learning studio](quickstart-create-resources.md) lets you quickly create a workspace with default settings.
92100
* Use [Azure portal](how-to-manage-workspace.md?tabs=azure-portal#create-a-workspace) for a point-and-click interface with more security options.
@@ -111,11 +119,11 @@ Once your workspace is set up, you can interact with it in the following ways:
111119
+ [Azure Machine Learning designer](concept-designer.md)
112120
:::moniker range="azureml-api-2"
113121
+ In any Python environment with the [Azure Machine Learning SDK](https://aka.ms/sdk-v2-install).
114-
+ On the command line using the Azure Machine Learning [CLI extension v2](how-to-configure-cli.md)
122+
+ On the command line, using the Azure Machine Learning [CLI extension v2](how-to-configure-cli.md)
115123
:::moniker-end
116124
:::moniker range="azureml-api-1"
117125
+ In any Python environment with the [Azure Machine Learning SDK](/python/api/overview/azure/ml/)
118-
+ On the command line using the Azure Machine Learning [CLI extension v1](./v1/reference-azure-machine-learning-cli.md)
126+
+ On the command line, using the Azure Machine Learning [CLI extension v1](./v1/reference-azure-machine-learning-cli.md)
119127
:::moniker-end
120128
+ [Azure Machine Learning VS Code Extension](how-to-manage-resources-vscode.md#workspaces)
121129

0 commit comments

Comments
 (0)