Skip to content

Commit 65bdbd0

Browse files
authored
Merge pull request #297093 from msangapu-msft/toclinks
updates
2 parents 6831fd6 + c4196b0 commit 65bdbd0

File tree

3 files changed

+133
-14
lines changed

3 files changed

+133
-14
lines changed
Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
---
2+
title: Overview of using custom domain names
3+
description: Learn how to configure and manage custom domain names in Azure App Service, including mapping, buying, migrating, securing, and traffic routing.
4+
author: msangapu-msft
5+
ms.author: msangapu
6+
ms.date: 03/10/2025
7+
ms.topic: overview
8+
ms.service: azure-app-service
9+
---
10+
# Overview: Use custom domain names with Azure App Service
11+
12+
Azure App Service enables you to host web apps on a fully managed platform. By default, apps hosted on Azure App Service are assigned a domain name like `myapp-00000.westus.azurewebsites.net`. However, for most production applications, you’ll want to use your own **domain name** (e.g., `www.contoso.com`) to create a professional, branded web presence. This is referred to as adding a **custom domain** to your app.
13+
14+
In this article, you'll get an overview of how to configure and manage custom domain names in Azure App Service—whether you're buying a new domain, migrating an existing one, managing DNS, or securing your domain with SSL/TLS certificates.
15+
16+
## What is a custom domain?
17+
18+
A **domain name** is the address people type into a web browser to reach your website. A **custom domain** is a domain name that you own and configure to point to your Azure-hosted app, replacing the default Azure domain.
19+
20+
For example:
21+
22+
- **Default Azure domain**: `myapp-00000.westus.azurewebsites.net`
23+
- **Custom domain**: `www.contoso.com`
24+
25+
Using a custom domain allows you to:
26+
27+
- Establish a branded, user-friendly web address.
28+
- Improve trust and credibility with customers.
29+
- Manage and secure traffic to your application.
30+
31+
## Common scenarios for custom domains in Azure App Service
32+
33+
Azure App Service supports various scenarios for working with domain names:
34+
35+
- **Point a custom domain name to your App Service app.**
36+
- **Purchase a domain name directly through Azure**, simplifying DNS management.
37+
- **Migrate an existing domain name** from another registrar to be managed via Azure.
38+
- **Distribute global traffic** using Azure Traffic Manager with your domain.
39+
- **Secure your custom domain** with SSL/TLS certificates for HTTPS.
40+
41+
## Key steps to set up and manage custom domain names
42+
43+
### Map a custom domain name to your app
44+
45+
To associate a domain name with your App Service app, you need to create DNS records with your domain registrar that point to Azure. This typically involves:
46+
47+
- Adding an **A record** (using the app's IP address) or a **CNAME record** (aliasing the Azure default domain).
48+
- Verifying ownership of the domain.
49+
- Binding the domain name to your app in the Azure portal or via CLI.
50+
51+
> [!div class="nextstep"]
52+
> [Tutorial: Map a custom domain to your Azure app](app-service-web-tutorial-custom-domain.md)
53+
### Buy a domain name from Azure
54+
55+
Azure lets you **search for and purchase domain names directly** through the Azure portal. Domains purchased via Azure are automatically linked to Azure DNS for easier setup.
56+
57+
**Benefits of buying a domain name through Azure**:
58+
59+
- Simplified DNS management.
60+
- Seamless integration with App Service.
61+
- Easier SSL certificate setup.
62+
63+
> [!div class="nextstep"]
64+
> [Buy and configure a custom domain name in Azure](manage-custom-dns-buy-domain.md)
65+
### Migrate an existing domain name to Azure DNS
66+
67+
If your web app is currently hosted elsewhere and actively serving traffic, you can migrate your custom domain to Azure App Service without downtime by carefully managing DNS updates. The migration process allows you to transition your domain while minimizing disruption to users.
68+
69+
Azure provides options to:
70+
71+
Verify domain ownership before switching traffic to avoid interruptions.
72+
Preconfigure domain settings in App Service to ensure seamless redirection.
73+
Manage DNS changes strategically to reduce propagation delays.
74+
75+
> [!div class="nextstep"]
76+
> [Migrate an existing domain name to Azure App Service](manage-custom-dns-migrate-domain.md)
77+
### Configure Traffic Manager with your custom domain
78+
79+
To improve global performance and availability, you can use **Azure Traffic Manager** to route traffic for your custom domain based on geographic location, latency, or availability. Traffic Manager works with your App Service app to ensure users are directed to the best-performing instance.
80+
81+
> [!div class="nextstep"]
82+
> [Use Traffic Manager with a custom domain name](configure-domain-traffic-manager.md)
83+
### Secure your custom domain name with SSL certificates
84+
85+
Securing your custom domain with an **SSL/TLS certificate** enables HTTPS, which is essential for protecting user data and building trust. Azure App Service supports:
86+
87+
- **Free App Service Managed Certificates** for custom domains.
88+
- **Bring Your Own Certificate (BYOC)** for more advanced configurations.
89+
90+
Certificates can be easily created, uploaded, and managed within Azure.
91+
92+
> [!div class="nextstep"]
93+
> [Secure a custom domain with an SSL certificate](tutorial-secure-domain-certificate.md)
94+
## Summary
95+
96+
Adding a **custom domain name** to your Azure App Service app helps you create a branded, secure, and professional online experience. Whether you're purchasing a new domain, migrating an existing one, optimizing traffic flow, or securing your app, Azure provides a complete set of tools to manage domain names efficiently.
97+
98+
## Next steps
99+
100+
- [Get started: Map a custom domain name](app-service-web-tutorial-custom-domain.md)
101+
- [Purchase a domain name through Azure](manage-custom-dns-buy-domain.md)
102+
- [Set up Traffic Manager with your domain](configure-domain-traffic-manager.md)
103+
- [Add SSL to secure your domain](tutorial-secure-domain-certificate.md)

articles/app-service/overview-tls.md

Lines changed: 28 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.topic: overview
66
ms.date: 03/10/2025
77
ms.author: msangapu
88
author: msangapu-msft
9+
ms.service: azure-app-service
910
ms.custom: UpdateFrequency3
1011
ms.collection: ce-skilling-ai-copilot
1112
---
@@ -19,9 +20,9 @@ Transport Layer Security (TLS) is a widely adopted security protocol that is des
1920

2021
App Service supports TLS to help ensure:
2122

22-
- **Encryption** of data in transit.
23-
- **Authentication** of web apps by using trusted certificates.
24-
- **Integrity** to prevent tampering of data during transmission.
23+
- Encryption of data in transit.
24+
- Authentication of web apps by using trusted certificates.
25+
- Integrity to prevent tampering of data during transmission.
2526

2627
> [!TIP]
2728
>
@@ -37,9 +38,9 @@ App Service supports TLS to help ensure:
3738

3839
Azure App Service supports the following TLS versions for incoming requests to your web app:
3940

40-
- **TLS 1.3**: The latest and most secure version, now fully supported.
41-
- **TLS 1.2**: The default minimum TLS version for new web apps.
42-
- **TLS 1.1 and TLS 1.0**: Versions supported for backward compatibility, but not recommended.
41+
- TLS 1.3: The latest and most secure version, now fully supported.
42+
- TLS 1.2: The default minimum TLS version for new web apps.
43+
- TLS 1.1 and TLS 1.0: Versions supported for backward compatibility, but not recommended.
4344

4445
You can configure the *minimum TLS version* for incoming requests to your web app and its Source Control Manager (SCM) site. By default, the minimum is set to **TLS 1.2**.
4546

@@ -49,9 +50,9 @@ You can use Azure Policy to help audit your resources and minimum TLS version. G
4950

5051
TLS 1.3 is fully supported on App Service and introduces several improvements over TLS 1.2:
5152

52-
- **Stronger security**, with simplified cipher suites and forward secrecy.
53-
- **Faster handshakes** for reduced latency.
54-
- **Encrypted handshake** messages for enhanced privacy.
53+
- Stronger security, with simplified cipher suites and forward secrecy.
54+
- Faster handshakes for reduced latency.
55+
- Encrypted handshake messages for enhanced privacy.
5556

5657
To require TLS 1.3 for all inbound requests, set **Minimum Inbound TLS Version** to **TLS 1.3** in the Azure portal, the Azure CLI, or your Azure Resource Manager template (ARM template).
5758

@@ -126,20 +127,33 @@ After you enable E2E TLS encryption, all intra-cluster communications for your w
126127

127128
## TLS/SSL certificates on App Service
128129

129-
To serve HTTPS traffic, App Service requires a TLS/SSL certificate that is bound to your custom domain.
130+
To serve HTTPS traffic, App Service requires a TLS/SSL certificate that is bound to your custom domain. App Service offers multiple certificate options, ranging from fully managed free certificates to customer-managed certificates.
130131

131132
### Types of certificates
132133

133-
- **App Service certificates (ASC)**. Fully managed certificates issued and renewed automatically by Azure, stored securely in Azure Key Vault.
134+
- **App Service managed certificates** (Free)
135+
- Provided at no cost.
136+
- Fully managed by Azure App Service, including automatic renewal.
137+
- Customers cannot access, export, or use these certificates outside of App Service.
138+
- Doesn't support wildcard or custom root CAs.
134139

135-
- **Bring your own certificate (BYOC)**. Upload and manage certificates (in PFX format) issued by third-party Certificate Authorities (CAs).
140+
- **App Service certificates (ASC)**
141+
- Paid certificates issued by GoDaddy.
142+
- Customer owns and manages the certificate.
143+
- Stored in the customer’s Key Vault (KV) and can be exported and used outside of App Service.
144+
145+
- **Bring your own certificate (BYOC)**
146+
- Upload and manage your own TLS/SSL certificates (**PFX format**).
147+
- Fully customer-managed.
148+
149+
Each of these options provides flexibility based on your security and management needs.
136150

137151
### Bind certificates to custom domains
138152

139153
After you upload or create a certificate, you bind it to a custom domain on your web app by using:
140154

141-
- **SNI (Server Name Indication) SSL bindings** for multitenant hosting
142-
- **IP SSL bindings** for dedicated IP addresses
155+
- SNI (Server Name Indication) SSL bindings for multitenant hosting
156+
- IP SSL bindings for dedicated IP addresses
143157

144158
> [!NOTE]
145159
> Azure-managed domains (such as `*.azurewebsites.net`) are automatically secured with default certificates, so no extra configuration is required.

articles/app-service/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -224,6 +224,8 @@ items:
224224
href: tutorial-secure-domain-certificate.md
225225
- name: Domain names
226226
items:
227+
- name: Overview of custom domains
228+
href: overview-custom-domains.md
227229
- name: Connect a domain name
228230
href: app-service-web-tutorial-custom-domain.md
229231
displayName: Map a custom domain, connect a custom domain, custom domain

0 commit comments

Comments
 (0)