Skip to content

Commit c9428dc

Browse files
Merge pull request #216164 from santiagxf/santiagxf/aml-batch-bastion
Update how-to-secure-batch-endpoint.md
2 parents b6cd89d + a4b9277 commit c9428dc

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ job = ml_client.batch_endpoints.invoke(
8181
)
8282
```
8383

84-
# [Azure ML studio](#tab/studio)
84+
# [studio](#tab/studio)
8585

8686
Jobs are always started using the identity of the user in the portal in studio.
8787

@@ -131,7 +131,7 @@ job = ml_client.batch_endpoints.invoke(
131131
)
132132
```
133133

134-
# [Azure ML studio](#tab/studio)
134+
# [studio](#tab/studio)
135135

136136
You can't run jobs using a service principal from studio.
137137

@@ -174,7 +174,7 @@ job = ml_client.batch_endpoints.invoke(
174174
)
175175
```
176176

177-
# [Azure ML studio](#tab/studio)
177+
# [studio](#tab/studio)
178178

179179
You can't run jobs using a managed identity from studio.
180180

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -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 (BASTION) 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)