This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 66%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Hi,
In one of our subscription we have Cloud services (extended support) with production version of code of our services and deploying it working just fine (updating from Azure Dev Ops pipelines/Azure portal/Visual Studio). Now we've tried to create similar one, but for the dev/stage environment, so in the other subscription (with all dev/stage/test resources). However all our tries of creating/deploying it, both from Azure portal as well as from ADO pipelines was failed. Everytime we've got result code:
"BadRequest: Cloud Services (extended support) will be retired on 31 March 2027, instead consider using Service Fabric managed cluster." Is it possible that creating it already is disabled/blocked? It should be still possible, as there is plenty of time till full retiring and we need this to create a full copy of production env as the test/stage environment.
Hi @Durga Reshma Malthi , thx for your comment.
Yes, I saw that information, but is it mean that now I cannot create new instance of cloud service? It is really long time till the retirement, so IMO it shouldn't be blocked yet. Best regards,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 64%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
Hi @Durga Reshma Malthi ,
I know that slots are not available in the Cloud services (extended support), that's why we've try to deploy it to spearate, new cloud service, on separate subscription (dedicated for stage/test env). And creating/deploying it to that new service doesn't work (with error described in first post).
As per this document - https://docs.azure.cn/en-us/cloud-services-extended-support/deploy-prerequisite - As of March 31, 2025, cloud Services (extended support) is deprecated and will be fully retired on March 31, 2027.
Hope this helps!
Please Let me know if you have any queries.
Which Cloud Service you are trying to deploy
Cloud Services (extended support) doesn't support the logical concept of a hosted service, which included two slots (Production & Staging). Each deployment is an independent Cloud Service (extended support) deployment. To test and stage a new release of a cloud service, deploy a cloud service (extended support) and tag it as VIP swappable with another cloud service (extended support).
Refer to this frequently asked questions documents - https://docs.azure.cn/en-us/cloud-services-extended-support/faq
Hope this helps!
Please Let me know if you have any queries. If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.