Does anybody know if there's a EOL date or something like that for Cloud Service (Extended Support)? Classic is going to be retired now but "Extended Support" doesn't look like it's gonna be there for a very long period.

Hello @Aubrey Lin , Thanks for posting your query on Microsoft QnA. There is no end of life date for Cloud Services (extended support) yet. You can consider this as a long term offering as it is a ARM based deployment model. Hope this helps. Please feel free to reach back if you have any additional queries. --------------------------------------------- Please don't forget to " Accept as Answer " and " Upvote " if you think my response was helpful, so that it can help others in the community looking for help on similar queries.

Cloud Service (Extended Support)

Accepted answer

srbhatta-MSFT 8,551 Reputation points Microsoft Employee

2022-02-24T11:09:14.56+00:00

Hello @Aubrey Lin ,
Thanks for posting your query on Microsoft QnA.
There is no end of life date for Cloud Services (extended support) yet. You can consider this as a long term offering as it is a ARM based deployment model.

Hope this helps. Please feel free to reach back if you have any additional queries.

---------------------------------------------

Please don't forget to "Accept as Answer" and "Upvote" if you think my response was helpful, so that it can help others in the community looking for help on similar queries.
Please sign in to rate this answer.
Ramon de Klein | Cross Point 0 Reputation points

2024-02-08T08:39:27.9433333+00:00

Basic SKU public IP address will be retired on September 30, 2025 and Cloud Services Extended Support requires such an IP address, so Cloud Services extended support should also support Standard SKU public IP addresses.

Deployment of Cloud Services (extended support) will already cease on March 31, 2025, because it won't be possible to create new basic load balancers from this date. This is only one year away, so please give us a migration path on how to deal with this.

This page suggests that existing Cloud Services (extended support) instances are not affected by this, but how can you deploy new Cloud Services (extended support) instances?

In some regions the production/staging swapping doesn't work, because the new deployment cannot be placed in the same "slot". For the West US region, we almost always need to destroy our production slot, before we can deploy a new version. Not ideal, because it introduces down-time, but if we cannot create new public IP/load balancer then we effectively cannot deploy a bugfix anymore.

Our product is at the end of it's lifecycle, but we still offer it to existing customers and cannot terminate the product within a year. Also a major rewrite to fit Microsoft Service Fabric isn't possible, because the used technology requires IIS (which is hard in Service Fabric). There is also no budget, because the product is almost EOL.
Sign in to comment

Share via

Cloud Service (Extended Support)

0 additional answers