Merge pull request #284055 from alfpark/alpark/batch

Remove outdated info and update sec best practices

Author: prmerger-automator[bot]

articles/batch/nodes-and-pools.md

@@ -2,7 +2,7 @@
 title: Nodes and pools in Azure Batch
 description: Learn about compute nodes and pools and how they are used in an Azure Batch workflow from a development standpoint.
 ms.topic: conceptual
-ms.date: 06/25/2024
+ms.date: 08/08/2024
 ---
 # Nodes and pools in Azure Batch
 
@@ -72,9 +72,6 @@ When you create a Batch pool, you specify the Azure virtual machine configuratio
 
 The **Virtual Machine Configuration** specifies that the pool is composed of Azure virtual machines. These VMs may be created from either Linux or Windows images.
 
-> [!IMPORTANT]
-> Currently, Batch does not support [Trusted Launch VMs](../virtual-machines/trusted-launch.md). 
-
 The [Batch node agent](https://github.com/Azure/Batch/blob/master/changelogs/nodeagent/CHANGELOG.md) is a program that runs on each node in the pool and provides the command-and-control interface between the node and the Batch service. There are different implementations of the node agent, known as SKUs, for different operating systems. When you create a pool based on the Virtual Machine Configuration, you must specify not only the size of the nodes and the source of the images used to create them, but also the **virtual machine image reference** and the Batch **node agent SKU** to be installed on the nodes. For more information about specifying these pool properties, see [Provision Linux compute nodes in Azure Batch pools](batch-linux-nodes.md). You can optionally attach one or more empty data disks to pool VMs created from Marketplace images, or include data disks in custom images used to create the VMs. When including data disks, you need to mount and format the disks from within a VM to use them.
 
 ### Node Agent SKUs

articles/batch/security-best-practices.md

@@ -1,7 +1,7 @@
 ---
 title: Batch security and compliance best practices
 description: Learn best practices and useful tips for enhancing security with your Azure Batch solutions.
-ms.date: 06/27/2024
+ms.date: 08/08/2024
 ms.topic: conceptual
 ---
 
@@ -32,6 +32,10 @@ outbound access for baseline operation, the recommendation is to use the simplif
 node communication model will be
 [retired on March 31, 2026](batch-pools-to-simplified-compute-node-communication-model-migration-guide.md).
 
+Pools should also be configured with enhanced security settings, including
+[Trusted Launch](../virtual-machines/trusted-launch.md) (requires Gen2 VM images and a compatible VM size),
+enabling secure boot, vTPM, and encryption at host (requires a compatible VM size).
+
 ### Batch account authentication
 
 Batch account access supports two methods of authentication: Shared Key and [Microsoft Entra ID](batch-aad-auth.md).