Skip to content

Commit efe70a7

Browse files
authored
Update how-to-authenticate-batch-endpoint.md
1 parent 144b61c commit efe70a7

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

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

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The following examples show different ways to start batch deployment jobs using
4646
4747
### Running jobs using user's credentials
4848

49-
In this case, we want to execute a batch endpoint using the identity of the user currenly logged in. Follow these steps:
49+
In this case, we want to execute a batch endpoint using the identity of the user currently logged in. Follow these steps:
5050

5151
> [!NOTE]
5252
> When working on Azure ML studio, batch endpoints/deployments are always executed using the identity of the current user logged in.
@@ -91,13 +91,13 @@ In this case, we want to execute a batch endpoint using the identity of the user
9191
9292
# [REST](#tab/rest)
9393
94-
When working with REST APIs, we recommend to use either a service principal or a managed identity to interact with the API.
94+
When working with REST APIs, we recommend to using either a service principal or a managed identity to interact with the API.
9595
9696
---
9797
9898
### Running jobs using a service principal
9999
100-
In this case, we want to execute a batch endpoint using a service princpal already created in Azure Active Directory. To complete the authentication, you will have to create a secret to perform the authentication. Follow these steps:
100+
In this case, we want to execute a batch endpoint using a service principal already created in Azure Active Directory. To complete the authentication, you will have to create a secret to perform the authentication. Follow these steps:
101101
102102
# [Azure ML CLI](#tab/cli)
103103
@@ -226,14 +226,18 @@ job = ml_client.batch_endpoints.invoke(
226226

227227
# [REST](#tab/rest)
228228

229-
You can use the REST API of Azure Machine Learning to start a batch endpoints job using a managed identity. The steps vary depending on the underlying service being used. Some examples include (but are not limitted to):
229+
You can use the REST API of Azure Machine Learning to start a batch endpoints job using a managed identity. The steps vary depending on the underlying service being used. Some examples include (but are not limited to):
230230

231231
* [Managed identity for Azure Data Factory](../../data-factory/data-factory-service-identity.md)
232232
* [How to use managed identities for App Service and Azure Functions](../../app-service/overview-managed-identity.md).
233233
* [How to use managed identities for Azure resources on an Azure VM to acquire an access token](../../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md).
234234

235+
You can also use the Azure CLI to get an authentication token for the managed identity and the pass it to the batch endpoints URI.
236+
235237
---
236238

237239
## Next steps
238240

239241
* [Network isolation in batch endpoints](how-to-secure-batch-endpoint.md)
242+
* [Invoking batch endpoints from Event Grid events in storage](how-to-use-event-grid-batch.md).
243+
* [Invoking batch endpoints from Azure Data Factory](how-to-use-batch-azure-data-factory.md).

0 commit comments

Comments
 (0)