BestPaid guides · Azure · .NET

Azure Cloud Services (extended support) retires on March 31, 2027: where to move your web and worker roles

If your app still runs as web roles and worker roles with a .csdef and a .cscfg, it has about four months left. Microsoft retires the Cloud Services (extended support) deployment model on March 31, 2027 and doesn't grant extensions. Here is how to choose the target and what has to change in the code.

Sources: Microsoft's Azure Updates notice Cloud Services (extended support) to be retired on March 31, 2027, Microsoft's Cloud Services (extended support) documentation and its certificates and Key Vault article, the Service Fabric migration FAQ and Microsoft's Service Bus SDK retirement notice. Checked on November 21, 2026. This page is our own summary; follow Microsoft's documentation for every detail.

What Microsoft says

Pick the target per role

What you haveUsually the shortest way out
Web role: ASP.NET on .NET Framework, no special startup tasksApp Service on Windows runs ASP.NET 4.8 as is. Move config and certificates, then deploy; modernize later.
Web role with startup tasks that install software, change the registry or need admin rightsA Windows container (App Service custom container or AKS Windows nodes) or Virtual Machine Scale Sets, where you control the image.
Worker role: a Run() loop that reads queues or runs schedulesA WebJob on App Service, Azure Functions for queue-triggered work, or a .NET Worker Service in Azure Container Apps.
Many roles talking over internal endpoints, stateful servicesService Fabric managed cluster, Microsoft's suggested path, or AKS if the team already runs Kubernetes.

Moving to .NET 10 is not required to leave Cloud Services, but it's often the cheaper long-term choice: Container Apps and App Service on Linux run only modern .NET, not .NET Framework. Do it in the same project only if the code base is small or well tested.

What has to change in the code

A four-month plan

  1. Weeks 1–2: inventory every role, startup task, certificate, endpoint and setting; choose the target per role.
  2. Weeks 3–8: replace RoleEnvironment and RoleEntryPoint code, write the infrastructure as code, set up the new environment next to the old one.
  3. Weeks 9–12: run both side by side, compare logs and queue throughput, then move DNS and traffic.
  4. By March 31, 2027: delete the Cloud Services deployment, but only after a full business cycle on the new platform.
No time or no one left who knows the roles? We move Cloud Services web and worker roles to App Service, Container Apps or Service Fabric at a fixed price, with or without the step to .NET 10. It starts with a $490 audit: every role, startup task and setting mapped to its new home, the risks and a fixed quote.
See the .NET upgrade offer
Using WindowsAzure.ServiceBus? The old Service Bus libraries lost support on September 30, 2026, and Microsoft's notice says SBMP can't be used after that date: the quick AMQP switch and the move to Azure.Messaging.ServiceBus.