Announcing custom host names with App Service
Published date: 21 June, 2017
Azure App Service has been supporting custom host names for a while now. App Service has a shared front end, so before you can use a custom host name with your app, you need to verify domain ownership by creating the required DNS records. This is done to prevent a host-name squatting vulnerability. To add a custom host name to your app, you need to create DNS records for ownership verification and routing.
We recently made the following changes in our host-name management model.
One-to-many associations between a host name and an Azure subscription
Earlier, a host name could be used with only one subscription on the App Service platform. With this change, multiple subscriptions can share a host name. Each subscription needs to validate the domain ownership separately by creating the required DNS records.
Allowing a subscription to reclaim a host name by validating domain ownership
The App Service platform consists of multiple scale units. A host name can be associated with only one app on a scale unit. Even two apps in the same subscription cannot share the same host name on a scale unit. This is by design, because an App Service runtime should be able to resolve a custom host name to an app uniquely.
In the past, a customer sometimes had a custom host name in an old subscription that they could not access anymore and wanted to use the same host name with another app on the scale unit. This was not allowed, even though the customer could revalidate domain ownership. With this change, App Service customers can do this themselves.