Merge pull request #230268 from Blackmist/workspace-clarity

positioning workspace as a per-project entity.

Author: Court72

articles/machine-learning/concept-workspace.md

@@ -10,16 +10,32 @@ ms.topic: conceptual
 ms.author: deeikele
 author: deeikele
 ms.reviewer: sgilley
-ms.date: 08/26/2022
+ms.date: 03/13/2023
 #Customer intent: As a data scientist, I want to understand the purpose of a workspace for Azure Machine Learning.
 ---
 
 
 # What is an Azure Machine Learning workspace?
 
-The workspace is the top-level resource for Azure Machine Learning, providing a centralized place to work with all the artifacts you create when you use Azure Machine Learning.  The workspace keeps a history of all training runs, including logs, metrics, output, and a snapshot of your scripts. You use this information to determine which training run produces the best model.  
+Workspaces are places to collaborate with colleagues and group related work. For example, experiments, jobs, datasets, components, and inference endpoints. 
 
-Once you have a model you like, you register it with the workspace. You then use the registered model and scoring scripts to deploy to an [online endpoint](concept-endpoints.md) as a REST-based HTTP endpoint.
+:::image type="content" source="./media/concept-workspace/workspace.png" alt-text="Screenshot of the Azure Machine Learning workspace.":::
+
+We recommend creating 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.
+
+
+## Working with a workspace
+
+Machine learning tasks read and/or write artifacts to your workspace.
+
++ Run an experiment to train a model - writes job run results to the workspace.
++ Use automated ML to train a model - writes training results to the workspace.
++ Register a model in the workspace.
++ Deploy a model - uses the registered model to create a deployment.
++ Create and run reusable workflows.
++ View machine learning artifacts such as jobs, pipelines, models, deployments.
++ Track and monitor models.
++ You can share assets between workspaces using [Azure Machine Learning registries (preview)](how-to-share-models-pipelines-across-workspaces-with-registries.md).
 
 ## Taxonomy 
 
@@ -45,18 +61,6 @@ You can interact with your workspace in the following ways:
 + On the command line using the Azure Machine Learning [CLI extension](how-to-configure-cli.md)
 + [Azure Machine Learning VS Code Extension](how-to-manage-resources-vscode.md#workspaces)
 
-## Machine learning with a workspace
-
-Machine learning tasks read and/or write artifacts to your workspace.
-
-+ Run an experiment to train a model - writes job run results to the workspace.
-+ Use automated ML to train a model - writes training results to the workspace.
-+ Register a model in the workspace.
-+ Deploy a model - uses the registered model to create a deployment.
-+ Create and run reusable workflows.
-+ View machine learning artifacts such as jobs, pipelines, models, deployments.
-+ Track and monitor models.
-
 ## Workspace management
 
 You can also perform the following workspace management tasks:
@@ -103,7 +107,7 @@ When you create a new workspace, it automatically creates several Azure resource
   > By default, the storage account is a general-purpose v1 account. You can [upgrade this to general-purpose v2](../storage/common/storage-account-upgrade.md) after the workspace has been created. 
   > Do not enable hierarchical namespace on the storage account after upgrading to general-purpose v2.
 
-  To use an existing Azure Storage account, it cannot be of type BlobStorage or a premium account (Premium_LRS and Premium_GRS). It also cannot have a hierarchical namespace (used with Azure Data Lake Storage Gen2). Neither premium storage nor hierarchical namespaces are supported with the _default_ storage account of the workspace. You can use premium storage or hierarchical namespace with _non-default_ storage accounts.
+  To use an existing Azure Storage account, it can't be of type BlobStorage or a premium account (Premium_LRS and Premium_GRS). It also can't have a hierarchical namespace (used with Azure Data Lake Storage Gen2). Neither premium storage nor hierarchical namespaces are supported with the _default_ storage account of the workspace. You can use premium storage or hierarchical namespace with _non-default_ storage accounts.
 
 + [Azure Container Registry](https://azure.microsoft.com/services/container-registry/): Registers docker containers that are used for the following components:
     * [Azure Machine Learning environments](concept-environments.md) when training and deploying models