Using a cloudapp.net domain with cloud services (extended support)?

Question

We had a cloud service (classic) running on a cloudapp.net domain. Someone accidentally deleted the cloud service, but we still had the data, so I went to recreate it.

I tried creating a new cloud service (classic) and was able to do so, but I was unable to deploy to the cloud service, because I received an error saying, "Please use cloud services (extended support) instead of cloud services (classic)."

So I tried to make a cloud service (extended support), but when I make an extended support cloud service, it only lets me use a cloudapp.azure.com address, not a cloudapp.net address. This won't do because our applications are hardcoded to use the cloudapp.net address.

I tried migrating the empty cloud service I had created to extended support, so that I could have an extended support cloud service but be able to keep the cloudapp.net domain. It wouldn't let me do that without a deployment, and it wouldn't let me make a deployment because I received the error message above.

So I seem to be stuck in a catch 22; I can't migrate to extended support without making a deployment, and I can't make a deployment without being on extended support. And I can't start on extended support, because then I can't have a cloudapp.net address.

I should also mention that 2 weeks ago, I made a classic cloud service for testing purposes and I was able to deploy to it. So this is something that has changed in the last 2 weeks.

I understand that classic cloud service is deprecated, and I'm fine with being on cloud services extended support. But can someone figure out how to get out of this catch 22? All I want is to have a cloud service on a cloudapp.net domain. So it seems to me that either Azure should allow users to make extended support cloud services on cloudapp.net domains, or let us deploy to classic cloud services until they are fully retired. so that they can be migrated to extended support.

The ideal solution would be to let me deploy to the classic cloud service, so that I could then migrate it to extended support (I don't have any desire to stay on classic).

Answer 1

@James Morton

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Firstly, apologies for the delay in responding here.

Are you looking for that same specific xxx.cloudapp.net? It is not very clear why cloudapp.azure.net is not ok unless you are looking for a specific dns address which you already had. Updating the app hardcording would be ideal approach for your case and is future proof.

I checked with internal team on this and below is the suggestion:

I would recommend you to file a support ticket to enable classic access with relevant classic usage history. Support will whitelist the sub-id for classic usage and the deprecated error will go away. Now deploy classic and then migrate to Cloud Services Extended support.

Hope that helps.
If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.