You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/custom-domains-certificates.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: craigshoemaker
6
6
ms.service: azure-container-apps
7
7
ms.custom: build-2023, ignite-2024
8
8
ms.topic: how-to
9
-
ms.date: 12/18/2024
9
+
ms.date: 1/14/2025
10
10
ms.author: cshoe
11
11
zone_pivot_groups: azure-cli-or-portal
12
12
---
@@ -21,14 +21,14 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
21
21
- Ingress must be enabled for the container app.
22
22
23
23
> [!NOTE]
24
-
> If you configure a [custom environment DNS (Domain Name System) suffix](environment-custom-dns-suffix.md), you cannot add a custom domain that contains this suffix to your Container App.
24
+
> If you configure a [custom environment DNS (Domain Name System) suffix](environment-custom-dns-suffix.md), you can't add a custom domain that contains this suffix to your Container App.
25
25
26
26
## Add a custom domain and certificate
27
27
28
28
::: zone pivot="azure-portal"
29
29
30
30
> [!IMPORTANT]
31
-
> If you are using a new certificate, you must have an existing [SNI domain certificate](https://wikipedia.org/wiki/Server_Name_Indication) file available to upload to Azure.
31
+
> If you're using a new certificate, you must have an existing [SNI domain certificate](https://wikipedia.org/wiki/Server_Name_Indication) file available to upload to Azure.
32
32
33
33
1. Navigate to your container app in the [Azure portal](https://portal.azure.com)
34
34
@@ -66,7 +66,7 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
66
66
| Apex domain | A record | An apex domain is a domain at the root level of your domain. For example, if your DNS (Domain Name System) zone is `contoso.com`, then `contoso.com` is the apex domain. |
67
67
| Subdomain | CNAME | A subdomain is a domain that is part of another domain. For example, if your DNS zone is `contoso.com`, then `www.contoso.com` is an example of a subdomain that can be configured in the zone. |
68
68
69
-
1. Using the DNS provider that is hosting your domain, create DNS records based on the *Hostname record type* you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you are using custom domains with the private endpoint (preview) feature:
69
+
1. Using the DNS provider that is hosting your domain, create DNS records based on the *Hostname record type* you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you're using custom domains with the private endpoint (preview) feature:
70
70
71
71
# [General](#tab/general)
72
72
@@ -92,7 +92,7 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
92
92
|--|--|--|
93
93
| A |`@`| The Private IP of your private endpoint on your container apps environment. |
94
94
95
-
In addition, you will need to add the following record to your public DNS zone.
95
+
In addition, you'll need to add the following record to your public DNS zone.
96
96
97
97
| Record type | Host | Value |
98
98
|--|--|--|
@@ -114,7 +114,7 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
114
114
1. Once the operation is complete, you see your domain name in the list of custom domains with a status of *Secured*. Navigate to your domain to verify that it's accessible.
115
115
116
116
> [!NOTE]
117
-
> For container apps in internal Container Apps environments, [additional configuration](./networking.md#dns) is required to use custom domains with VNET-scope ingress.
117
+
> For container apps in internal Container Apps environments, [extra configuration](./networking.md#dns) is required to use custom domains with VNET-scope ingress.
118
118
119
119
::: zone-end
120
120
@@ -127,7 +127,7 @@ Container Apps supports apex domains and subdomains. Each domain type requires a
127
127
| Apex domain | A record | HTTP | An apex domain is a domain at the root level of your domain. For example, if your DNS zone is `contoso.com`, then `contoso.com` is the apex domain. |
128
128
| Subdomain | CNAME | CNAME | A subdomain is a domain that is part of another domain. For example, if your DNS zone is `contoso.com`, then `www.contoso.com` is an example of a subdomain that can be configured in the zone. |
129
129
130
-
1. Log in to Azure with the Azure CLI.
130
+
1. Log in to Azure with the Azure CLI.
131
131
132
132
```azurecli
133
133
az login
@@ -205,7 +205,7 @@ Container Apps supports apex domains and subdomains. Each domain type requires a
205
205
--query "properties.customDomainVerificationId"
206
206
```
207
207
208
-
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you are using custom domains with the private endpoint (preview) feature:
208
+
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you're using custom domains with the private endpoint (preview) feature:
@@ -18,7 +18,7 @@ Azure Container Apps allows you to bind one or more custom domains to a containe
18
18
If you want to set up a custom domain using your own certificate, see [Custom domain names and certificates in Azure Container Apps](custom-domains-certificates.md).
19
19
20
20
> [!NOTE]
21
-
> If you configure a [custom environment DNS suffix](environment-custom-dns-suffix.md), you cannot add a custom domain that contains this suffix to your Container App.
21
+
> If you configure a [custom environment DNS suffix](environment-custom-dns-suffix.md), you can't add a custom domain that contains this suffix to your Container App.
22
22
23
23
## Free certificate requirements
24
24
@@ -30,10 +30,11 @@ The requirements are:
30
30
31
31
- Must have an A record for apex domains that points to your Container Apps environment's IP address.
32
32
33
-
- Establish a CNAME record for subdomains that maps directly to the container app's automatically generated domain name. Mapping to an intermediate CNAME value blocks certificate issuance and renewal. Examples of CNAME values are traffic managers, Cloudflare, and similar services.
33
+
- Establish a CNAME record for subdomains that maps directly to the container app's generated domain name. Mapping to an intermediate CNAME value blocks certificate issuance and renewal. Examples of CNAME values are traffic managers, Cloudflare, and similar services.
34
34
35
35
> [!NOTE]
36
36
> To ensure the certificate issuance and subsequent renewals proceed successfully, all requirements must be met at all times when the managed certificate is assigned.
37
+
37
38
## Add a custom domain and managed certificate
38
39
39
40
::: zone pivot="azure-portal"
@@ -176,7 +177,7 @@ Container Apps supports apex domains and subdomains. Each domain type requires a
176
177
--query "properties.customDomainVerificationId"
177
178
```
178
179
179
-
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you are using custom domains with the private endpoint (preview) feature:
180
+
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you're using custom domains with the private endpoint (preview) feature:
0 commit comments