Cloud Services (extended support) will be retired on 31 March 2027

Question

Cloud Services (extended support) will be retired on 31 March 2027

Nischay 125

Got this notification from Azure:-

Cloud Services (extended support) will be retired on 31 March 2027

You're receiving this notification because you're associated with one or more Azure subscriptions that use Cloud Services (extended support). Cloud Services (extended support) will be retired on 31 March 2027, please transition to Service Fabric managed cluster by that date. Migrating from Cloud Services (Extended Support) to Service Fabric managed cluster enhances the scalability, flexibility, and reliability of your Azure deployments. From now to 31 March 2027, you can continue to use Cloud Services (extended support) without disruption. To avoid service disruption, migrate workloads running Cloud Services (extended support) to Service Fabric managed clusters by 31 March 2027.

Migration to Fabric seems to be complex as a lot of changes will be required and majority of our backend will have to be redone. We were looking to migrate to App Service or VM.

Here is some additional information about our Cloud Service (Extended Support):-

Legacy enterprise backend built on the classic Microsoft stack.

Core type: Monolithic backend solution for content, licensing, and campaign/submission workflows.
Tech stack: C# / .NET Framework 4.8, ASP.NET MVC 5 + Web API 2, Entity Framework 6, 1 Web role, 0 Worker role
Data layer: SQL Server via old Entity Framework (EDMX/EF CaDb context and related entities).
Platform integrations: Azure Blob Storage, Notification Hubs/Service Bus-era libraries, Cloud Services (extended support) deployment model.

Please share any recommended steps/solutions to migrate to App Service & VM?

Nischay 125 Reputation points

2026-04-01T22:23:32.7766667+00:00

Hi Manish,

Could we please get some guidance on our original question? The details shared so far don’t seem to be related to what we were asking.

We had provided information about our current tech stack running on Cloud Service (Extended Support), and we are looking for recommended steps & solutions to migrate to either App Service or Virtual Machines. As mentioned earlier, migrating to Service Fabric appears to be quite complex for our setup and would likely require significant changes and a large portion of our backend to be redeveloped.

We would really appreciate it if you or one of your colleagues could guide us on the best approach for this type of migration.

Best regards,

Nischay
Manish Deshpande 5,255 Reputation points Microsoft External Staff Moderator

2026-04-06T12:13:37.9133333+00:00
Hello Nischay

There isn’t a one-size-fits-all migration path—it really depends on your app’s setup, dependencies, and what you need operationally.

To get started, check out the official Microsoft documentation:

https://dotnet.territoriali.olinfo.it/fr-fr/azure/service-fabric/cloud-services-migration-decision-matrix#dec…

It gives a really helpful side-by-side look at different Azure platforms, including pros, cons, and how tough each migration might be.

Since you want to minimize refactoring, I’d suggest focusing on platforms with low to moderate migration complexity. Usually, folks look at:

Azure App Service (great for WebForms ASP.NET apps with minimal code changes)

Azure Virtual Machine Scale Sets (if you need more control over OS and IIS)

All these options support app updates and versioned deployments, but how easy they are to manage can vary. The decision matrix breaks down the operational workload for each, which should help you find a good fit for your team.

Autoscaling is available on several Azure services and should cover your CPU-based scaling needs. Azure App Service and VM Scale Sets have simple, built-in autoscaling, and are popular for lift-and-shift. You could also look at Azure Kubernetes Service, Functions, or Service Fabric, but they might be more complex depending on your app.

Next up, I recommend running a proof of concept—deploy a part of your app to your top platform picks to test compatibility and scaling before going all in. With support ending March 31, 2027, it’s a good idea to start planning a phased migration so everything goes smoothly.

Reference: https://dotnet.territoriali.olinfo.it/fr-fr/dotnet/azure/migration/app-service

Hope this helps! Let me know if you have any other questions please comment into the comment section i will be happy to assist you.

1 answer

Your answer

Nischay 125 Reputation points

2026-04-01T22:23:32.7766667+00:00

Hi Manish,

Could we please get some guidance on our original question? The details shared so far don’t seem to be related to what we were asking.

We had provided information about our current tech stack running on Cloud Service (Extended Support), and we are looking for recommended steps & solutions to migrate to either App Service or Virtual Machines. As mentioned earlier, migrating to Service Fabric appears to be quite complex for our setup and would likely require significant changes and a large portion of our backend to be redeveloped.

We would really appreciate it if you or one of your colleagues could guide us on the best approach for this type of migration.

Best regards,

Nischay
Manish Deshpande 5,255 Reputation points Microsoft External Staff Moderator

2026-04-06T12:13:37.9133333+00:00

Hello Nischay

There isn’t a one-size-fits-all migration path—it really depends on your app’s setup, dependencies, and what you need operationally.

To get started, check out the official Microsoft documentation:

https://dotnet.territoriali.olinfo.it/fr-fr/azure/service-fabric/cloud-services-migration-decision-matrix#dec…

It gives a really helpful side-by-side look at different Azure platforms, including pros, cons, and how tough each migration might be.

Since you want to minimize refactoring, I’d suggest focusing on platforms with low to moderate migration complexity. Usually, folks look at:

Azure App Service (great for WebForms ASP.NET apps with minimal code changes)

Azure Virtual Machine Scale Sets (if you need more control over OS and IIS)

All these options support app updates and versioned deployments, but how easy they are to manage can vary. The decision matrix breaks down the operational workload for each, which should help you find a good fit for your team.

Autoscaling is available on several Azure services and should cover your CPU-based scaling needs. Azure App Service and VM Scale Sets have simple, built-in autoscaling, and are popular for lift-and-shift. You could also look at Azure Kubernetes Service, Functions, or Service Fabric, but they might be more complex depending on your app.

Next up, I recommend running a proof of concept—deploy a part of your app to your top platform picks to test compatibility and scaling before going all in. With support ending March 31, 2027, it’s a good idea to start planning a phased migration so everything goes smoothly.

Reference: https://dotnet.territoriali.olinfo.it/fr-fr/dotnet/azure/migration/app-service

Hope this helps! Let me know if you have any other questions please comment into the comment section i will be happy to assist you.

Answer 1

Hello Nischay

Thank you for reaching out Q/A. Hello Nischay

There isn’t a one-size-fits-all migration path—it really depends on your app’s setup, dependencies, and what you need operationally.

To get started, check out the official Microsoft documentation:

https://dotnet.territoriali.olinfo.it/fr-fr/azure/service-fabric/cloud-services-migration-decision-matrix#dec…

It gives a really helpful side-by-side look at different Azure platforms, including pros, cons, and how tough each migration might be.

Since you want to minimize refactoring, I’d suggest focusing on platforms with low to moderate migration complexity. Usually, folks look at:

Azure App Service (great for WebForms ASP.NET apps with minimal code changes)

Azure Virtual Machine Scale Sets (if you need more control over OS and IIS)

All these options support app updates and versioned deployments, but how easy they are to manage can vary. The decision matrix breaks down the operational workload for each, which should help you find a good fit for your team.

Autoscaling is available on several Azure services and should cover your CPU-based scaling needs. Azure App Service and VM Scale Sets have simple, built-in autoscaling, and are popular for lift-and-shift. You could also look at Azure Kubernetes Service, Functions, or Service Fabric, but they might be more complex depending on your app.

Next up, I recommend running a proof of concept—deploy a part of your app to your top platform picks to test compatibility and scaling before going all in. With support ending March 31, 2027, it’s a good idea to start planning a phased migration so everything goes smoothly.

Reference: https://dotnet.territoriali.olinfo.it/fr-fr/dotnet/azure/migration/app-service

Hope this helps! Let me know if you have any other questions please comment into the comment section i will be happy to assist you.

References:

Retirement Accountment

Frequently asked questions for Azure Cloud Services (extended support)

Migrating from Azure Cloud Services to Service Fabric

Technical details of migrating to Azure Cloud Services (extended support)

Manish Deshpande 5,255 Reputation points Microsoft External Staff Moderator

2026-04-08T09:58:21.5566667+00:00

Hello Nishchay

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.
Manish Deshpande 5,255 Reputation points Microsoft External Staff Moderator

2026-04-09T07:24:10.14+00:00

Hello Nishchay

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

Share via

Cloud Services (extended support) will be retired on 31 March 2027

Cloud Services (extended support) will be retired on 31 March 2027

1 answer

Your answer