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
Copy file name to clipboardExpand all lines: articles/machine-learning/concept-enterprise-security.md
+2-22Lines changed: 2 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,30 +100,10 @@ Azure Machine Learning creates an additional application (the name starts with `
100
100
101
101
Azure Machine Learning relies on other Azure services for compute resources. Compute resources (compute targets) are used to train and deploy models. You can create these compute targets in a virtual network. For example, you can use Azure Data Science Virtual Machine to train a model and then deploy the model to AKS.
102
102
103
-
For more information, see [How to run experiments and inference in a virtual network](how-to-enable-virtual-network.md).
103
+
For more information, see [How to securely run experiments and inference in an isolated virtual network](how-to-enable-virtual-network.md).
104
104
105
105
You can also enable Azure Private Link for your workspace. Private Link allows you to restrict communications to your workspace from an Azure Virtual Network. For more information, see [How to configure Private Link](how-to-configure-private-link.md).
106
106
107
-
> [!TIP]
108
-
> You can combine virtual network and Private Link together to protect communication between your workspace and other Azure resources. However, some combinations require an Enterprise edition workspace. Use the following table to understand what scenarios require Enterprise edition:
> | Workspace without Private Link. Other resources (except Azure Container Registry) in a virtual network | ✔ | ✔ |
114
-
> | Workspace without Private Link. Other resources with Private Link | ✔ ||
115
-
> | Workspace with Private Link. Other resources (except Azure Container Registry) in a virtual network | ✔ | ✔ |
116
-
> | Workspace and any other resource with Private Link | ✔ ||
117
-
> | Workspace with Private Link. Other resources without Private Link or virtual network | ✔ | ✔ |
118
-
> | Azure Container Registry in a virtual network | ✔ ||
119
-
> | Customer Managed Keys for workspace | ✔ ||
120
-
>
121
-
122
-
> [!WARNING]
123
-
> Azure Machine Learning compute instances preview is not supported in a workspace where Private Link is enabled.
124
-
>
125
-
> Azure Machine Learning does not support using an Azure Kubernetes Service that has private link enabled. Instead, you can use Azure Kubernetes Service in a virtual network. For more information, see [Secure Azure ML experimentation and inference jobs within an Azure Virtual Network](how-to-enable-virtual-network.md).
126
-
127
107
## Data encryption
128
108
129
109
### Encryption at rest
@@ -260,7 +240,7 @@ Each workspace has an associated system-assigned managed identity that has the s
260
240
261
241
Microsoft may collect non-user identifying information like resource names (for example the dataset name, or the machine learning experiment name), or job environment variables for diagnostic purposes. All such data is stored using Microsoft-managed keys in storage hosted in Microsoft owned subscriptions and follows [Microsoft's standard Privacy policy and data handling standards](https://privacy.microsoft.com/privacystatement).
262
242
263
-
Microsoft also recommends not storing sensitive information (such as account key secrets) in environment variables. Environment variables are logged, encrypted, and stored by us. Similarly when naming [runid](https://docs.microsoft.com/python/api/azureml-core/azureml.core.run%28class%29?view=azure-ml-py), avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.
243
+
Microsoft also recommends not storing sensitive information (such as account key secrets) in environment variables. Environment variables are logged, encrypted, and stored by us. Similarly when naming [run_id](https://docs.microsoft.com/python/api/azureml-core/azureml.core.run%28class%29?view=azure-ml-py), avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.
264
244
265
245
You may opt out from diagnostic data being collected by setting the `hbi_workspace` parameter to `TRUE` while provisioning the workspace. This functionality is supported when using the AzureML Python SDK, CLI, REST APIs, or Azure Resource Manager templates.
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-configure-private-link.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ For information on putting the storage account in the virtual network, see [Use
113
113
114
114
To secure the Azure Key Vault used by your workspace, you can either put it inside the virtual network or enable Private Link for it.
115
115
116
-
For information on putting the key vault in the virtual network, see [Use a key vault instance with your workspace](how-to-enable-virtual-network.md#use-a-key-vault-instance-with-your-workspace).
116
+
For information on putting the key vault in the virtual network, see [Use a key vault instance with your workspace](how-to-enable-virtual-network.md#key-vault-instance).
117
117
118
118
For information on enabling Private Link for the key vault, see [Integrate Key Vault with Azure Private Link](/azure/key-vault/private-link-service).
119
119
@@ -126,7 +126,7 @@ To secure the Azure Kubernetes services used by your workspace, put it inside a
126
126
127
127
## Azure Container Registry
128
128
129
-
For information on securing Azure Container Registry inside the virtual network, see [Use Azure Container Registry](how-to-enable-virtual-network.md#use-azure-container-registry).
129
+
For information on securing Azure Container Registry inside the virtual network, see [Use Azure Container Registry](how-to-enable-virtual-network.md#azure-container-registry).
130
130
131
131
> [!IMPORTANT]
132
132
> If you are using Private Link for your Azure Machine Learning workspace, and put the Azure Container Registry for your workspace in a virtual network, you must also apply the following Azure Resource Manager template. This template enables your workspace to communicate with ACR over the Private Link.
0 commit comments