Skip to content

Commit 491e11c

Browse files
authored
Update how-to-secure-batch-endpoint.md
1 parent 282c903 commit 491e11c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ When deploying a machine learning model to a batch endpoint, you can secure thei
2525

2626
## Securing batch endpoints
2727

28-
All the batch endpoints created inside of secure workspace are deployed as private batch endpoints by default. Not further configuration is required.
28+
All the batch endpoints created inside of secure workspace are deployed as private batch endpoints by default. No further configuration is required.
2929

3030
> [!IMPORTANT]
3131
> When working on a private link-enabled workspaces, batch endpoints can be created and managed using Azure Machine Learning studio. However, they can't be invoked from the UI in studio. Please use the Azure ML CLI v2 instead for job creation. For more details about how to use it see [Invoke the batch endpoint to start a batch scoring job](how-to-use-batch-endpoint.md#invoke-the-batch-endpoint-to-start-a-batch-scoring-job).
@@ -34,7 +34,7 @@ The following diagram shows how the networking looks like for batch endpoints wh
3434

3535
:::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.":::
3636

37-
In order to enable the jump host VM (or self-hosted agent VMs if using [Azure Bastion](../../bastion/bastion-overview.md)) access to the resources in Azure Machine Learning VNET, the previous architecture uses virtual network peering to seamlessly connect these two virtual networks. Thus the two virtual networks appear as one for connectivity purposes. The traffic between VMs and Azure Machine Learning resources in peered virtual networks uses the Microsoft backbone infrastructure. Like traffic between them in the same network, traffic is routed through Microsoft's private network only.
37+
In order to enable the jump host VM (or self-hosted agent VMs if using [Azure Bastion](../../bastion/bastion-overview.md)) access to the resources in Azure Machine Learning VNET, the previous architecture uses virtual network peering to seamlessly connect these two virtual networks. Thus the two virtual networks appear as one for connectivity purposes. The traffic between VMs and Azure Machine Learning resources in peered virtual networks uses the Microsoft backbone infrastructure. Like traffic between them in the same network, traffic is routed through Microsoft's private network only.
3838

3939
## Securing batch deployment jobs
4040

0 commit comments

Comments
 (0)