Skip to content

Commit a9f481f

Browse files
author
Larry Franks
committed
acrolinx
1 parent e080738 commit a9f481f

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/machine-learning/how-to-prevent-data-loss-exfiltration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure Machine Learning has several inbound and outbound dependencies. Some of th
2525

2626
* __Storage Outbound__: This requirement comes from compute instance and compute cluster. A malicious agent can use this outbound rule to exfiltrate data by provisioning and saving data in their own storage account. You can remove data exfiltration risk by using an Azure Service Endpoint Policy and Azure Batch's simplified node communication architecture.
2727

28-
* __AzureFrontDoor.frontend outbound__: Azure Front Door is used by the Azure Machine Learning studio UI and AutoML. Instead of allowing outbound to the service tag (AzureFrontDoor.frontend), switch to the following fully qulified domain names (FQDN). Switching to these FQDNs removes unnecessary outbound traffic included in the service tag and allows only what is needed for Azure Machine Learning studio UI and AutoML.
28+
* __AzureFrontDoor.frontend outbound__: Azure Front Door is used by the Azure Machine Learning studio UI and AutoML. Instead of allowing outbound to the service tag (AzureFrontDoor.frontend), switch to the following fully qualified domain names (FQDN). Switching to these FQDNs removes unnecessary outbound traffic included in the service tag and allows only what is needed for Azure Machine Learning studio UI and AutoML.
2929

3030
- `ml.azure.com`
3131
- `automlresources-prod.azureedge.net`

articles/machine-learning/how-to-setup-customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In the [customer-managed keys concepts article](concept-customer-managed-keys.md
4141
* Resources managed by Microsoft in your subscription can’t transfer ownership to you.
4242
* You can't delete Microsoft-managed resources used for customer-managed keys without also deleting your workspace.
4343
* The key vault that contains your customer-managed key must be in the same Azure subscription as the Azure Machine Learning workspace.
44-
* Workspace with customer-managed key does not currently support v2 online endpoint and batch endpoint.
44+
* Workspace with customer-managed key doesn't currently support v2 online endpoint and batch endpoint.
4545

4646
> [!IMPORTANT]
4747
> When using a customer-managed key, the costs for your subscription will be higher because of the additional resources in your subscription. To estimate the cost, use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).

0 commit comments

Comments
 (0)