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
Copy file name to clipboardExpand all lines: articles/batch/managed-identity-pools.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Configure managed identities in Batch pools
3
3
description: Learn how to enable user-assigned managed identities on Batch pools and how to use managed identities within the nodes.
4
4
ms.topic: conceptual
5
-
ms.date: 08/12/2024
5
+
ms.date: 12/23/2024
6
6
ms.devlang: csharp
7
7
ms.custom:
8
8
---
@@ -13,6 +13,10 @@ complicated identity and credential management by providing an identity for the
13
13
(Azure AD ID). This identity is used to obtain Microsoft Entra tokens to authenticate with target
14
14
resources in Azure.
15
15
16
+
When adding a User-Assigned Managed Identity to a Batch Pool, it is crucial to set the *Identity* property in your configuration. This property links the managed identity to the pool, enabling it to access Azure resources securely. Incorrect setting of the *Identity* property can result in common errors, such as access issues or upload errors.
17
+
18
+
For more information on configuring managed identities in Azure Batch, please refer to the [Azure Batch Managed Identities documentation](https://learn.microsoft.com/en-us/troubleshoot/azure/hpc/batch/use-managed-identities-azure-batch-account-pool).
19
+
16
20
This topic explains how to enable user-assigned managed identities on Batch pools and how to use managed identities within the nodes.
0 commit comments