What would be the Impact of Azure Batch 'CloudServiceConfiguration' pools retirement on our service

Question

We received an email regarding Azure Batch 'CloudServiceConfiguration' pools being retired on 29 February 2024 and that we need to start using 'VirtualMachineConfiguration' before 29 February 2024 to avoid disruption to your applications. After 29 February 2024, we will not be able to create new 'CloudServiceConfiguration' pools or add new nodes to existing pools.

We are in the process of upgrading the OSFamily for our services from “6” to “7” as a part of Azure FedRAMP requirement which is done through the CloudService Configuration files.
We want to make sure that the retirement of 'CloudServiceConfiguration' pools will not impact our current Microsoft Stream Classic service flow, which includes upgrading the osFamily or any other configurations that currently exist.

Can anyone please help us out here and resolve our query that this migration will not affect the current service flow and OS upgrade?
Link to one of our .cscfg files for reference: ServiceConfiguration.cscfg - Repos (visualstudio.com)

Answer 1

Hello Aarushi Hans

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

This retirement is only applied to Azure Batch service. If you are not using Azure Batch service, there will be no impact. 

However, if you are using classic Cloud Service, requesting you to check this retirement announcement once.

Ref: https://azure.microsoft.com/en-us/updates/cloud-services-retirement-announcement/

Hope this helps.