Azure Batch classic compute node communication model will be retired on 31 March 2026

To improve security, simplify the user experience, and enable key future improvements, we’ll be retiring the Classic compute node communication model on **31 March 2026**. The simplified compute node communication model will replace the classic compute node communication model after 31 March 2026\. The change will be introduced in two phases. From now until 30 September 2024, the default node communication mode for newly created [Batch pools with virtual networks](https://learn.microsoft.com/azure/batch/batch-virtual-network) will remain classic. After 30 September 2024, the default node communication mode for newly created Batch pools with virtual networks will switch to simplified. After 31 March 2026, the option to use classic compute node communication mode will no longer be honoured. Batch pools without user-specified virtual networks are generally unaffected by this change and the default communication mode will be controlled by the Batch service. **Required action** Follow these [steps](https://aka.ms/ccncmmigration) to transition using the Simplified compute node communication model before 31 March 2026\. **Help and support** If you have any questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/batchmicrosoftqna). If you have a support plan and you need technical help, please create a [support request](https://ms.portal.azure.com/#view/Microsoft%5FAzure%5FSupport/HelpAndSupportBlade/~/overview). * Batch * Retirements * [ Batch](https://azure.microsoft.com/en-gb/services/batch/)