Application hosting
CoreApp Service custom domains and TLS
DNS ownership, custom hostnames, certificates, and TLS bindings.
Key points
- Custom domains require DNS records and ownership verification.
- HTTPS requires a valid certificate that covers the hostname plus a TLS binding.
- DNS routing and certificate lifecycle remain separate responsibilities.
Best-known use cases
- Serve an application on an organization-owned hostname.
- Renew and bind a certificate for encrypted web traffic.
What candidates often confuse it with
- Custom DNS vs TLS: resolve a hostname to the app vs authenticate and encrypt that hostname.
- Certificate upload vs binding: make a certificate available vs associate it with a hostname.
Key takeaway
Configure both DNS ownership and the correct certificate binding for a custom HTTPS App Service hostname.
Related services
- App Service networking
- App Service deployment slots and backup
Relevant exam tasks
- D3.4.S4 — Configure certificates and Transport Layer Security (TLS) for an App Service
- D3.4.S5 — Map an existing custom DNS name to an App Service
- D3.4.S6 — Configure backup for an App Service
- D3.4.S7 — Configure networking settings for an App Service
- D3.4.S8 — Configure deployment slots for an App Service