Is there a way to keep control of my *.cloudapp.net url after August 31, 2024?

Pierre Aubeuf 25

On August 31, 2024, our Azure CloudServices (classic) will disappear.

We have done what is necessary to migrate them to Azure CloudServices (extended support).

But, obviously, one of them is hardcoded and accessed from old applications left in the wild under its url foo.cloudapp.net without a custom domain configured.

Is there a way to preserve only the foo.cloudapp.net url?

To configure it to redirect to the new one in .cloudapp.azure.com?

or at the very least, host a static page on this specific legacy URL foo.cloudapp.net?

Deepanshukatara-6769 9,195 Reputation points

2024-07-10T10:14:49.5+00:00

Hi, Welcome to MS Q&A

Yes, you can configure a custom domain name for a Cloud Service in Azure. This allows you to use your own domain name, such as foo.cloudapp.net, instead of the default cloudapp.net domain. You can then configure the custom domain to redirect to the new domain in .cloudapp.azure.com or host a static page on it.

For detailed instructions on how to configure a custom domain name for a Cloud Service, you can refer to the Azure Cloud Services (classic) documentation: Configuring a custom domain name for an Azure cloud service (classic).

Please let me know if any further questions

Kindly accept answer if it helps

Thanks

Deepanshu
KapilAnanth-MSFT 45,111 Reputation points Microsoft Employee

2024-07-10T11:09:36.4466667+00:00
@Pierre Aubeuf ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

Once the Azure Cloud Services (classic) resource gets retired, I don't think there will be any resource associated with it that can hold the domain "foo.cloudapp.net".

This component will also be deprecated/retired along with the service.

In this specific case, you will not be able to add a custom domain of "xxx**.cloudapp.azure.com**" either.

This is because, you have to own the domain ".cloudapp.azure.com" which is not the case.

Even if you were to own this, as mentioned earlier, the resource with the domain "foo.cloudapp.net" itself will no longer exist and hence, this cannot do any sort of redirection.

You have to update your applications to access the new URL of ".cloudapp.azure.com".

Hope this clarifies.

Cheers,

Kapil
Pierre Aubeuf 25 Reputation points

2024-07-10T12:01:32.4166667+00:00

@Deepanshukatara-6769 read the question again. You didn't understand it.

@KapilAnanth-MSFT , thank you for your answer.

But we have no way to update the application.

It's a shame that Microsoft Azure doesn't offer a solution in this specific case (even if not having configured a custom domain 8 years ago is our fault).
KapilAnanth-MSFT 45,111 Reputation points Microsoft Employee

2024-07-10T12:40:54.1733333+00:00

@Pierre Aubeuf ,

I understand your concern but I am afraid the architecture is not built like this.

You must note that the service as a whole was given the domain "foo.cloudapp.net".

And now the service is retiring and the domain is not a standalone or independent component that can still be available once the service is deprecated.

Users are suggested to migrate to a different service altogether which of course would have a different domain of it's own.

Cheers,

Kapil

Accepted answer

Sean Mahan 105 Reputation points

2024-07-10T13:25:07.5066667+00:00

@Pierre Aubeuf @KapilAnanth-MSFT

I have migrated (using the portal "Migrate to ARM" functionality) Classic Cloud Services, and those seem to have transitioned to Cloud Services (Extended Support) along with their [custom].cloudapp.net domain names. I haven't seen any documentation suggesting that cloudapp.net domain names like that will be removed after August 31st—in fact, this page simply says, "The DNS name and domain (cloudapp.net) for the migrated cloud service remains the same." If it's true that my already-migrated cloud services will no longer have their current "cloudapp.net" domain names after August 31st, that is also a big deal for us, so I want to make sure I understand what's happening.

Is Pierre's issue simply that a newly created Cloud Service (extended support) deployment cannot be assigned a cloudapp.net domain name? Could Pierre use the provided migration functionality to preserve his current cloudapp.net domain names?
Please sign in to rate this answer.

1 person found this answer helpful.
Sean Mahan 105 Reputation points

2024-07-10T13:39:34.3066667+00:00

Sorry, first time using this site, maybe this should have been a "Comment" rather than an "Answer". Apologies.

Pierre Aubeuf 25 Reputation points

2024-07-10T16:50:12.05+00:00

KUDOS to you @Sean Mahan !

That is the way I am searching. In place migration is keeping the url.

That sounds simple but the path I follow for my initial migration strongly suggest to "redeploy" and that is a bad idea in my case.

Thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Is there a way to keep control of my *.cloudapp.net url after August 31, 2024?

0 additional answers

Your answer