Merge pull request #103216 from j-martens/master

PRMerger20 · web-flow · commit 06ce7b40392a · 2020-02-03T16:59:18.000-08:00
compute context update regions
diff --git a/articles/machine-learning/concept-azure-machine-learning-architecture.md b/articles/machine-learning/concept-azure-machine-learning-architecture.md
@@ -82,7 +82,7 @@ Activities can provide notifications through the SDK or the web UI so that you c
 ### <a name="compute-instance"></a>Compute instance (preview)
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead. 
 
 An **Azure Machine Learning compute instance** (formerly Notebook VM) is a fully managed cloud-based workstation that includes multiple tools and environments installed for machine learning. Compute instances can be used as a compute target for training and inferencing jobs. For large tasks, [Azure Machine Learning compute clusters](how-to-set-up-training-targets.md#amlcompute) with multi-node scaling capabilities is a better compute target choice.
diff --git a/articles/machine-learning/concept-compute-instance.md b/articles/machine-learning/concept-compute-instance.md
@@ -23,7 +23,7 @@ Use a compute instance as your fully configured and managed development environm
 Compute instances are typically used as development environments.  They can also be used as a compute target for training and inferencing for development and testing.  For large tasks, an [Azure Machine Learning compute cluster](how-to-set-up-training-targets.md#amlcompute) with multi-node scaling capabilities is a better compute target choice.
 
 > [!NOTE]
-> Compute instances are currently available only for workspaces with a region of **North Central US** or **UK South**, with support for other regions coming soon.
+> Compute instances are currently available only for workspaces with a region of **North Central US**, **East US 2**, **North Europe** or **UK South**, with support for other regions coming soon.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead. 
 
 ## Why use a compute instance?
diff --git a/articles/machine-learning/concept-compute-target.md b/articles/machine-learning/concept-compute-target.md
@@ -54,7 +54,7 @@ You can create Azure Machine Learning compute instances (preview) or compute clu
 When created these compute resources are automatically part of your workspace unlike other kinds of compute targets.
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead. 
 
 ### Compute clusters
diff --git a/articles/machine-learning/concept-workspace.md b/articles/machine-learning/concept-workspace.md
@@ -76,7 +76,7 @@ You can also perform the following workspace management tasks:
 | Create a Notebook VM |   | **&check;** | |     |
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead.
 
 ## <a name='create-workspace'></a> Create a workspace
diff --git a/articles/machine-learning/how-to-configure-environment.md b/articles/machine-learning/how-to-configure-environment.md
@@ -54,7 +54,7 @@ To install the SDK environment for your [local computer](#local), [Jupyter Noteb
 The Azure Machine Learning [compute instance (preview)](concept-compute-instance.md) is a secure, cloud-based Azure workstation that provides data scientists with a Jupyter notebook server, JupyterLab, and a fully prepared ML environment.
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead.
 
 There is nothing to install or configure for a compute instance.  Create one anytime from within your Azure Machine Learning workspace. Provide just a name and specify an Azure VM type. Try it now with this [Tutorial: Setup environment and workspace](tutorial-1st-experiment-sdk-setup.md).
diff --git a/articles/machine-learning/how-to-create-your-first-pipeline.md b/articles/machine-learning/how-to-create-your-first-pipeline.md
@@ -36,7 +36,7 @@ If you don’t have an Azure subscription, create a free account before you begi
 * [Configure your development environment](how-to-configure-environment.md) to install the Azure Machine Learning SDK, or use an [Azure Machine Learning compute instance (preview)](concept-compute-instance.md) with the SDK already installed.
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead. 
 
 Start by attaching your workspace:
diff --git a/articles/machine-learning/how-to-set-up-vs-code-remote.md b/articles/machine-learning/how-to-set-up-vs-code-remote.md
@@ -17,7 +17,7 @@ ms.date: 12/09/2019
 In this article, you'll learn how to set up Visual Studio Code Remote on an Azure Machine Learning Compute Instance so you can **interactively debug your code** from VS Code. 
 
 > [!NOTE]
-> Compute instances are available only for workspaces with a **North Central US**, ** East US 2**, **North Europe** or **UK South**.
+> Compute instances are available only for workspaces with a **North Central US**, **East US 2**, **North Europe** or **UK South**.
 
 + An [Azure Machine Learning Compute Instance](concept-compute-instance.md) is a fully managed cloud-based workstation for data scientists and provides management and enterprise readiness capabilities for IT administrators. 
 
diff --git a/articles/machine-learning/tutorial-1st-experiment-sdk-setup.md b/articles/machine-learning/tutorial-1st-experiment-sdk-setup.md
@@ -96,7 +96,7 @@ You complete the following experiment set-up and run steps in Azure Machine Lear
 If you have custom widgets or prefer using Jupyter/JupyterLab select the **Jupyter** drop down on the far right, then select **Jupyter** or **JupyterLab**. The new browser window will be opened.
 
 > [!NOTE]
-> Compute instances (preview) are currently available only for workspaces with a region of **North Central US** or **UK South**, with support for other regions coming soon.
+> Compute instances (preview) are currently available only for workspaces with a region of **North Central US**, **East US 2**, **North Europe** or **UK South**, with support for other regions coming soon.
 >If your workspace is in any other region, you can continue to create and use a [Notebook VM](concept-compute-instance.md#notebookvm) instead.  You can use either a Notebook VM or a compute instance to run your notebook. A VM will continue running and incurring cost unless you stop it. You can stop it manually from the **Compute** tab in the Studio, or see the [blog post](https://techcommunity.microsoft.com/t5/educator-developer-blog/azure-virtual-machine-auto-shutdown/ba-p/379342) on enabling scheduled automatic shutdown for Azure VMs.
 
 ## Next steps
