DNS name for Cloud Services

Question

Hello,

I have a Cloud Service (extended support) with a some IoT devices connected to it via URL (name.cloudapp.net:12345). I noticed that in March 2027 it will be replaced by Service Fabric.

How can I transfer the DNS name (name.cloudapp.net) to Service Fabric so that my devices continue to work without updating the URL in the configuration?

Thank you.

Best regards,

Radu

Answer 1

Hello Radu,

Thank you for reaching out to Microsoft Q&A.

You are correct that Azure Cloud Services (Extended Support) is scheduled for retirement on March 31, 2027. Microsoft recommends migrating workloads hosted on this platform to alternative services, such as Service Fabric Managed Clusters, before the retirement date to avoid any potential service disruption.

We understand that your IoT devices are currently connecting to your Azure Cloud Service (Extended Support) using the default Azure-provided endpoint name.cloudapp.net, and that you would like to preserve this DNS name when migrating to another platform such as Azure Service Fabric, in order to avoid updating the device configurations.

Please note that the default *.cloudapp.net DNS name is tied to the specific Cloud Service resource and cannot be transferred or reassigned to a different Azure service type, including Azure Service Fabric.

To minimize impact during migration, the recommended approach is to use a custom DNS name instead of the Azure-provided cloudapp.net address. The custom DNS record can initially point to the existing Cloud Service and later be updated to the new Service Fabric environment without requiring changes on the IoT devices.

If maintaining the exact same name.cloudapp.net hostname is a strict requirement, unfortunately this scenario is not currently supported across different Azure resource types.

For additional reference, please review the following documentation:

Azure Cloud Services (extended support)

Cloud Services (extended support) and Service Fabric before migrating applications.

Use Azure DNS to provide custom domain settings for an Azure service

Hope this helps! Please let me know if you have any queries.

Answer 2

Cloud Services (extended support) and Service Fabric managed clusters are different resource types and use different public endpoints, so the existing name.cloudapp.net DNS name of a Cloud Service cannot be directly “moved” or reassigned to a Service Fabric cluster.

From the provided information:

• For Cloud Services (extended support), the DNS label is an optional property of the Public IP associated with the cloud service. Its format is:

    <userlabel>.<region>.cloudapp.azure.com
  

• DNS labels are tied to the specific Public IP resource used by that Cloud Service. Service Fabric managed clusters use their own public endpoints and IPs, so the same name.cloudapp.net label cannot simply be transferred.

To keep IoT devices working without changing their configured URL, a migration path must preserve the external hostname at a higher level (for example, by using a custom domain and CNAME/Traffic Manager/Front Door) rather than reusing the exact cloudapp.net label. The context does not provide a supported mechanism to reassign or port the existing cloudapp.net DNS label from Cloud Services (extended support) to a Service Fabric cluster.

---

References:

• Frequently asked questions for Azure Cloud Services (extended support)
• About Azure Cloud Services (extended support)
• Frequently asked questions (FAQ)