Skip to content

Commit 5f6fee1

Browse files
authored
Update how-to-secure-batch-endpoint.md
1 parent 5fe4870 commit 5f6fee1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/machine-learning/how-to-secure-batch-endpoint.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ When deploying a machine learning model to a batch endpoint, you can secure thei
1919

2020
## Securing batch endpoints
2121

22-
All the batch endpoints created inside of secure workspace are deployed as private batch endpoints by default. In order to have fully operational batch endpoints working with private networking, follow the following steps:
22+
Batch endpoints inherent the networking configuration from the workspace where they are deployed. All the batch endpoints created inside of secure workspace are deployed as private batch endpoints by default. In order to have fully operational batch endpoints working with private networking, follow the following steps:
2323

2424
1. You have configured your Azure Machine Learning workspace for private networking. For more details about how to achieve it read [Create a secure workspace](tutorial-create-secure-workspace.md).
2525

@@ -30,6 +30,8 @@ All the batch endpoints created inside of secure workspace are deployed as priva
3030
3131
3. Ensure blob, file, queue, and table private endpoints are configured for the storage accounts as explained at [Secure Azure storage accounts](how-to-secure-workspace-vnet.md#secure-azure-storage-accounts). Batch deployments require all the 4 to properly work.
3232

33+
4. Create the batch endpoint as regularly done.
34+
3335
The following diagram shows how the networking looks like for batch endpoints when deployed in a private workspace:
3436

3537
:::image type="content" source="./media/how-to-secure-batch-endpoint/batch-vnet-peering.png" alt-text="Diagram that shows the high level architecture of a secure Azure Machine Learning workspace deployment.":::

0 commit comments

Comments
 (0)