You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Use certificates to enable authentication of applications
4
+
services: batch
5
+
documentationcenter: .net
6
+
author: LauraBrenner
7
+
manager: evansma
8
+
editor: ''
9
+
10
+
ms.assetid: 63d9d4f1-8521-4bbb-b95a-c4cad73692d3
11
+
ms.service: batch
12
+
ms.topic: article
13
+
ms.tgt_pltfrm:
14
+
ms.workload: big-compute
15
+
ms.date: 02/17/2020
16
+
ms.author: labrenne
17
+
ms.custom: seodec18
18
+
19
+
---
20
+
# Using certificates with Batch
21
+
22
+
Currently the main reason to use certificates with Batch is if you have applications running in Pools that need to authenticate with an endpoint.
23
+
24
+
If you don't already have a certificate, you can create a self-signed certificate using the
25
+
`makecert` command-line tool.
26
+
27
+
## Upload certificates manually through the Azure portal
28
+
29
+
1. From the Batch account you want to upload a certificate to, select **Certificates** and then select **Add**.
30
+
31
+
2. Upload the certificate with a .pfx or .cer extension.
32
+
33
+
Once uploaded, the certificate is added to a list of certificates, and you can verify the thumbprint.
34
+
35
+
Now when you create a Batch pool, you can navigate to Certificates within the pool and assign the certificate you uploaded to that pool.
36
+
37
+
## Next steps
38
+
39
+
Batch has a certificate API, [AZ batch certificate create](https://docs.microsoft.com/cli/azure/batch/certificate?view=azure-cli-latest#az-batch-certificate-create)
40
+
41
+
For information on using Key Vault, see [Securely access Key Vault with Batch](credential-access-key-vault.md).
0 commit comments