Forum Discussion
Azure App Service secure hostname
Short answer to your actual question: no, it isn't mandatory — but the portal has stopped asking you, which is why it feels that way.
What changed is the default. New web apps created in the portal now get the secure unique default hostname automatically — the app name, a 16-character hash and the region, so contoso becomes something like contoso-a6gqaeashthkhkeu.eastus-01.azurewebsites.net — and the toggle to pick the classic appname.azurewebsites.net format isn't offered in the portal any more. The classic format still exists, and if you create through the CLI or a template you choose it by simply not setting a hostname scope, since the scope is opt-in there: you add --domain-name-scope when you want the secure hostname, with TenantReuse, SubscriptionReuse, ResourceGroupReuse or NoReuse depending on how stable you want the hash to be.
That scope choice is the bit worth getting right if you deploy across environments. TenantReuse keeps the same hash for the same app name across every subscription in your tenant, which is what you want if you promote from test to production and expect the hostname to stay predictable. NoReuse gives a fresh hash every time, which is the most isolated but also the least predictable.
And on the announcement you couldn't find — you're not missing one. The closest thing to a formal statement is the App Service documentation on subdomain takeover prevention, which was updated on 23 July 2026 to describe this portal default. For apps that already exist, the hostname can't be switched on afterwards; the documented way to move one is to clone it or restore from a backup into a new app with the secure hostname enabled.