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
1. Type the fully qualified domain name that you added a CNAME record for, such as `www.contoso.com`.
152
148
153
-
Make sure that **Hostname record type** is set to **CNAME (www\.example.com or any subdomain)**.
149
+
1. Select **Validate**. The **Add custom domain** page is shown.
154
150
155
-
Select **Add custom domain**.
151
+
1. Make sure that **Hostname record type** is set to **CNAME (www\.example.com or any subdomain)**. Select **Add custom domain**.
156
152
157
-

153
+

158
154
159
-
It might take some time for the new custom domain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
155
+
It might take some time for the new custom domain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
160
156
161
-

157
+

162
158
163
-
> [!NOTE]
164
-
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
159
+
> [!NOTE]
160
+
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
165
161
166
-
If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.
162
+
If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.
Make sure that **Hostname record type** is set to **A record (example.com)**.
222
+
1. Type the fully qualified domain name that you configured the A record for, such as `contoso.com`.
233
223
234
-
Select **Add custom domain**.
224
+
1.Select **Validate**. The **Add custom domain** page is shown.
235
225
236
-

226
+
1. Make sure that **Hostname record type** is set to **A record (example.com)**. Select **Add customdomain**.
237
227
238
-
It might take some time for the new custom domain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
228
+

239
229
240
-

230
+
It might take some time for the new customdomain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
241
231
242
-
> [!NOTE]
243
-
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
244
-
245
-
If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.

248
233
234
+
> [!NOTE]
235
+
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
236
+
237
+
If you missed a step or made a typo somewhere earlier, you see a verification error at the bottom of the page.
@@ -275,33 +267,31 @@ When the CNAME is added, the DNS records page looks like the following example:
275
267
276
268
You can now add any subdomain that matches the wildcard name to the app (for example, `sub1.contoso.com`, `sub2.contoso.com` and `*.contoso.com` both match `*.contoso.com`).
277
269
278
-
In the left navigation of the app page in the Azure portal, select **Custom domains**.
Make sure that **Hostname record type** is set to **CNAME record (www\.example.com or any subdomain)**.
278
+
1. Type a fully qualified domain name that matches the wildcard domain (for example, `sub1.contoso.com`), and then select **Validate**.
291
279
292
-
Select **Add custom domain**.
280
+
The **Add custom domain** button is activated.
293
281
294
-

282
+
1. Make sure that **Hostname record type** is set to **CNAME record (www\.example.com or any subdomain)**. Select **Add customdomain**.
295
283
296
-
It might take some time for the new custom domain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
284
+

297
285
298
-
Select the **+** icon again to add another custom domain that matches the wildcard domain. For example, add `sub2.contoso.com`.
286
+
It might take some time for the new custom domain to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
299
287
300
-

288
+
1. Select the **+** icon again to add another customdomain that matches the wildcard domain. For example, add `sub2.contoso.com`.
301
289
302
-
> [!NOTE]
303
-
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
290
+

304
291
292
+
> [!NOTE]
293
+
> A warning label for your custom domain means that it's not yet bound to a TLS/SSL certificate, and any HTTPS request from a browser to your custom domain will receive and error or warning, depending on the browser. To add a TLS binding, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
294
+
305
295
## Test in browser
306
296
307
297
Browse to the DNS name(s) that you configured earlier (for example, `contoso.com`, `www.contoso.com`, `sub1.contoso.com`, and `sub2.contoso.com`).
Type the fully qualified domain name you want to migrate, that corresponds to the TXT record you create, such as `contoso.com`, `www.contoso.com`, or `*.contoso.com`.
67
+
1.Type the fully qualified domain name you want to migrate, that corresponds to the TXT record you create, such as `contoso.com`, `www.contoso.com`, or `*.contoso.com`. Select **Validate**.
68
68
69
-
Select **Validate**.
69
+
The **Add custom domain** button is activated.
70
70
71
-
The **Add custom domain**button is activated.
71
+
1. Make sure that **Hostname record type** is set to the DNS record type you want to migrate. Select **Add hostname**.
72
72
73
-
Make sure that **Hostname record type** is set to the DNS record type you want to migrate.
73
+

74
74
75
-
Select **Add hostname**.
75
+
It might take some time for the new hostname to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
76
76
77
-

77
+

78
78
79
-
It might take some time for the new hostname to be reflected in the app's **Custom domains** page. Try refreshing the browser to update the data.
80
-
81
-

82
-
83
-
Your custom DNS name is now enabled in your Azure app.
79
+
Your custom DNS name is now enabled in your Azure app.
0 commit comments