Skip to content

Commit 4d371aa

Browse files
authored
Incorporated review pass comments
1 parent c08b8ea commit 4d371aa

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/batch/batch-account-create-portal.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ To create a Batch account in user subscription mode:
138138
1. After you select the key vault, select the checkbox next to **I agree to grant Azure Batch access to this key vault**.
139139
1. Select **Review + create**, and then select **Create** to create the Batch account.
140140

141-
### Create a Batch account with authentication mode
141+
### Create a Batch account with designated authentication mode
142142

143143
To create a Batch account with authentication mode settings:
144144

@@ -150,7 +150,10 @@ To create a Batch account with authentication mode settings:
150150
1. Leave the remaining settings at default values, select **Review + create**, and then select **Create**.
151151

152152
> [!TIP]
153-
> Batch support multiple authentication modes, and offers the built-in policies wherein users can enforce Microoft Entra ID authentication for Batch accounts when being created or update **Authentication mode** property after a Batch account is created.
153+
> For enhanced security, it is advised to confine the authentication mode of the Batch account solely to Microsoft Entra ID. This measure mitigates the risk of shared key exposure and introduces additional RBAC controls. For more details, see [Batch security best practices](./security-best-practices.md#batch-account-authentication).
154+
155+
> [!WARNING]
156+
> The Task Authentication Token will retire on September 30, 2024. Should you require this feature, it is recommended to use [User-assigned managed identity](./managed-identity-pools.md) in the Batch pool as an alternative.
154157
155158
### Grant access to the key vault manually
156159

0 commit comments

Comments
 (0)