You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> This uses Bash syntax for setting variables -- adjust as needed for your shell. You can also replace the values in commands below inline rather than using variables.
81
+
> This uses Bash syntax for setting variables. Adjust as needed for your shell. You can also replace the values in commands in the following examples inline rather than using variables.
81
82
82
83
If it doesn't already exist, you can create the Azure resource group:
83
84
@@ -105,20 +106,20 @@ You can show your current defaults using `--list-defaults/-l`:
105
106
106
107
The `ml` CLI extension (sometimes called 'CLI v2') for Azure Machine Learning sends operational data (YAML parameters and metadata) over the public internet. All the `ml` CLI extension commands communicate with the Azure Resource Manager. This communication is secured using HTTPS/TLS 1.2.
107
108
108
-
Data in a data store that is secured in a virtual network is _not_ sent over the public internet. For example, if your training data is located in the default storage account for the workspace, and the storage account is in a virtual network.
109
+
Data in a data store that is secured in a virtual network isn't_ sent over the public internet. For example, if your training data is located in the default storage account for the workspace, and the storage account is in a virtual network.
109
110
110
111
> [!NOTE]
111
112
> With the previous extension (`azure-cli-ml`, sometimes called 'CLI v1'), only some of the commands communicate with the Azure Resource Manager. Specifically, commands that create, update, delete, list, or show Azure resources. Operations such as submitting a training job communicate directly with the Azure Machine Learning workspace. If your workspace is [secured with a private endpoint](how-to-configure-private-link.md), that is enough to secure commands provided by the `azure-cli-ml` extension.
112
113
113
114
# [Public workspace](#tab/public)
114
115
115
-
If your Azure Machine Learning workspace is public (that is, not behind a virtual network), then there is no additional configuration required. Communications are secured using HTTPS/TLS 1.2
116
+
If your Azure Machine Learning workspace is public (that is, not behind a virtual network), then there's no extra configuration required. Communications are secured using HTTPS/TLS 1.2
116
117
117
118
# [Private workspace](#tab/private)
118
119
119
120
If your Azure Machine Learning workspace uses a private endpoint and virtual network, choose one of the following configurations to use:
120
121
121
-
* If you are__OK__ with the CLI v2 communication over the public internet, use the following `--public-network-access` parameter for the `az ml workspace update` command to enable public network access. For example, the following command updates a workspace for public network access:
122
+
* If you're__OK__ with the CLI v2 communication over the public internet, use the following `--public-network-access` parameter for the `az ml workspace update` command to enable public network access. For example, the following command updates a workspace for public network access:
122
123
123
124
```azurecli
124
125
az ml workspace update --name myworkspace --public-network-access enabled
0 commit comments