Removing "cloudapp.net" as it is no longer exploitable.

[227Abdulrahuman]

"cloudapp.net" is no longer exploitable.

Microsoft replaced "cloud service (classic)" with "cloud service (extended support)" which has another DNS zone cloudapp.azure.com.

Microsoft no longer allows register new cloud services under cloudapp.net

Reference:
https://learn.microsoft.com/en-us/answers/questions/867628/using-a-cloudapp-net-domain-with-cloud-services-(e

[Akokonunes]

Hello @227Abdulrahuman ,

Thank you so much for sharing this template with the community and contributing to the project. We'll be reviewing this PR shortly.

You're welcome to join our discord server, it's a great place to connect with fellow contributors and stay updated on the latest developments.

[Akokonunes]

Hi @227Abdulrahuman ,

Thanks for submitting this PR. After reviewed the reference link provided, but we couldn't find anywhere that mentions "cloudapp.net" is no longer exploitable or unsupported.

Could you provide a more specific reference that confirms this change?
Thanks!

[227Abdulrahuman]

In order to register a domain that ends with cloudapp.net you need to navigate to cloud services portal through this link:

https://portal.azure.com/#create/Microsoft.CloudService

It says "Cloud Services (classic) was retired on August 31st, 2024 for all customers. For similar requirements, please utilize Cloud Services (extended support) with Azure Resource Manager. Create a Cloud Service (extended support)

And if you attempt to deploy any cloud service it will fail to deploy.

In short you will not be able to deploy new cloud services that points to *.cloudapp.net

This use case is pointed here https://learn.microsoft.com/en-us/answers/questions/867628/using-a-cloudapp-net-domain-with-cloud-services-(e

[Akokonunes]

Thank you @227Abdulrahuman for this pull request and the detailed explanation.

You are correct. The cloudapp.net domain was tied to the "Azure Cloud Services (classic)" model, which Microsoft officially retired on August 31, 2024.

Since it's no longer possible to create new deployments on this service, the vulnerability is no longer exploitable. This change is valid.