I thought this stuff went away along with components of ASM at the beginning of Jan 2018. Replace with Application Service Environment. If that is the case shouldn't this document say it is deprecated technology?
Please correct me if I am wrong.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@DMoonesinghe Thanks for the feedback. We are actively investigating and will get back to you soon.
@DMoonesinghe You are correct. I have assigned the issue to the content author to evaluate and update as appropriate. In most cases, the documents will be replaced with newer content or simply removed. This is up to the content owner's discretion.
There is still a "Cloud services (classic)" menu with options to create new ones in my menu.
I believe it is correct to say that Web Apps are recommended now, but Cloud Services are not obsolete.
See also this page for a comparison.
https://docs.microsoft.com/en-us/azure/app-service/choose-web-site-cloud-service-vm
Thanks Appreciate your response. Yes, eventually I found that doc. But
since it was dated 2016 I wasn't sure if it was still relevant.
Thanks for you answer Mike.
On Fri, Aug 3, 2018 at 1:07 AM, dcbrown16 notifications@github.com wrote:
There is still a "Cloud services (classic)" menu with options to create
new ones in my menu.
I believe it is correct to say that Web Apps are recommended now, but
Cloud Services are not obsolete.
See also this page for a comparison.
https://docs.microsoft.com/en-us/azure/app-service/choose-
web-site-cloud-service-vm—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/11861#issuecomment-410145736,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlFSpih7wGM__eZnLDhFNNPjvaiyhMtLks5uM9p9gaJpZM4VTXl7
.
--
Deepal Moonesinghe
(408) 568 1669
deepal.[email protected]
"We must accept finite disappointment, but we must never lose infinite
hope."
~ Martin Luther King, Jr. ~
@DMoonesinghe We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
Re-opening the thread... the original point still stands, which is that this article should clearly point out that cloud services is deprecated. The referenced link states "Cloud Services is similar to Service Fabric in degree of control versus ease of use, but it’s now a legacy service and Service Fabric is recommended for new development." but that's not mentioned in this article or anywhere else in the Cloud Services documentation. We need to make it more clear for our customers that by sticking with/choosing Cloud Services they are committing to a legacy platform which will not receive significant feature updates going forward.
Agree 100% with @tescales. You would be making a very bad decision to start a project with Cloud Services right now.
Most helpful comment
Re-opening the thread... the original point still stands, which is that this article should clearly point out that cloud services is deprecated. The referenced link states "Cloud Services is similar to Service Fabric in degree of control versus ease of use, but it’s now a legacy service and Service Fabric is recommended for new development." but that's not mentioned in this article or anywhere else in the Cloud Services documentation. We need to make it more clear for our customers that by sticking with/choosing Cloud Services they are committing to a legacy platform which will not receive significant feature updates going forward.