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
[Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service. This guide shows you how to map an existing custom Domain Name System (DNS) name to App Service. To migrate a live site and its DNS domain name to App Service with no downtime, see [Migrate an active DNS name to Azure App Service](manage-custom-dns-migrate-domain.md).
21
+
[Azure App Service](overview.md) provides a highly scalable, self-patching web hosting service. This guide shows you how to map an existing custom Domain Name System (DNS) name to App Service. To migrate a live site and its DNS domain name to App Service with no downtime, see [Migrate an existing domain to Azure App Service](manage-custom-dns-migrate-domain.md).
22
22
23
-
The DNS record type you need to add with your domain provider depends on the domain you want to add to App Service.
23
+
The DNS record type you need to use depends on the domain you want to add to App Service.
24
24
25
25
| Scenario | Example | Recommended DNS record |
26
26
| - | - | - |
27
-
| Root domain | contoso.com |[A record](https://en.wikipedia.org/wiki/List_of_DNS_record_types#A). Don't use the CNAME record for the root record. (For information, see [RFC 1912, section 2.4](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4).) |
28
-
| Subdomain |www.contoso.com, my.contoso.com |[CNAME record](https://en.wikipedia.org/wiki/CNAME_record). You can map a subdomain to the app's IP address directly with an A record, but it's possible for [the IP address to change](overview-inbound-outbound-ips.md#when-inbound-ip-changes). The CNAME maps to the app's default hostname instead, which is less susceptible to change. |
| Root domain |`contoso.com`|[A record](https://en.wikipedia.org/wiki/List_of_DNS_record_types#A). Don't use the CNAME record for the root domain. (For information, see [RFC 1912, section 2.4](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4).) |
28
+
| Subdomain |`www.contoso.com`, `my.contoso.com`|[CNAME record](https://en.wikipedia.org/wiki/CNAME_record). You can map a subdomain to the app's IP address directly with an A record, but it's possible for [the IP address to change](overview-inbound-outbound-ips.md#when-inbound-ip-changes). The CNAME maps to the app's default hostname instead, which is less susceptible to change. |
> For an end-to-end tutorial that shows you how to configure a `www` subdomain and a managed certificate, see [Tutorial: Secure your Azure App Service app with a custom domain and a managed certificate](tutorial-secure-domain-certificate.md).
32
+
> For an end-to-end tutorial that shows you how to configure a `www` subdomain and a managed certificate, see [Tutorial: Use a custom domain and a managed certificate to secure your app](tutorial-secure-domain-certificate.md).
33
33
34
34
## Prerequisites
35
35
36
-
*[Create an App Service app](./index.yml), or use an app that you created for another tutorial. The web app's [App Service plan](overview-hosting-plans.md) must be a paid tier, not the Free (F1) tier. See [Scale up an app](manage-scale-up.md#scale-up-your-pricing-tier) to update the tier.
37
-
* Make sure you can edit the DNS records for your custom domain. To edit DNS records, you need access to the DNS registry for your domain provider, such as GoDaddy. For example, to add DNS entries for `contoso.com` and `www.contoso.com`, you must be able to configure the DNS settings for the `contoso.com` root domain. Your custom domains must be in a public DNS zone; private DNS zones are not supported.
36
+
* Create an [App Service app](./index.yml), or use an app that you created for another tutorial. The web app's [App Service plan](overview-hosting-plans.md) must be a paid tier, not the Free (F1) tier. To update the tier, see [Scale up your pricing tier](manage-scale-up.md#scale-up-your-pricing-tier).
37
+
* Make sure you can edit the DNS records for your custom domain. To edit DNS records, you need access to the DNS registry for your domain provider, such as GoDaddy. For example, to add DNS entries for `contoso.com` and `www.contoso.com`, you must be able to configure the DNS settings for the `contoso.com` root domain. Your custom domains must be in a public DNS zone; private DNS zones aren't supported.
38
38
* If you don't have a custom domain yet, you can [purchase an App Service domain](manage-custom-dns-buy-domain.md) instead.
39
39
40
40
## Configure a custom domain
41
41
42
42
1. In the [Azure portal](https://portal.azure.com), navigate to your app's management page.
43
-
1. In the left menu for your app, select **Custom domains**.
43
+
44
+
1. In the sidebar menu for your app, under **Settings**, select **Custom domains**.
45
+
44
46
1. Select **Add custom domain**.
45
47
46
48
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain.png" alt-text="A screenshot showing how to open the Add custom domain dialog." border="true":::
47
49
48
-
1. For **Domain provider**, select **All other domain services** to configure a third-party domain.
50
+
1. For **Domain provider**, select **All other domain services** to configure a non-Microsoft domain.
49
51
50
52
> [!NOTE]
51
-
> To configure an App Service domain, see [Buy a custom domain name for Azure App Service](manage-custom-dns-buy-domain.md).
53
+
> To configure an App Service domain, see [Buy and manage an App Service domain](manage-custom-dns-buy-domain.md).
52
54
53
55
1. For **TLS/SSL certificate**, select **App Service Managed Certificate** if your app is in the Basic tier or higher. If you want to remain in the Shared tier, or if you want to use your own certificate, select **Add certificate later**.
54
56
@@ -92,7 +94,7 @@ Create two records, as described in the following table:
92
94
| A |`@`| The app's IP address shown in the **Add custom domain** dialog. | The domain mapping itself. (`@` typically represents the root domain.) |
93
95
| TXT |`asuid`| The domain verification ID shown in the **Add custom domain** dialog. | For the root domain, App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
94
96
95
-
97
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/a-record.png" alt-text="Screenshot that shows a DNS records page.":::
96
98
97
99
### [Subdomain (for example, www.contoso.com)](#tab/subdomain)
98
100
@@ -105,7 +107,7 @@ Create two records, as described in the following table:
105
107
|A|`<subdomain>` (for example, `www`)|IP address shown in the **Add custom domain** dialog.| The domain mapping itself. |
106
108
|TXT|`asuid.<subdomain>` (for example, `asuid.www`)|The domain verification ID shown in the **Add custom domain** dialog.| App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
107
109
108
-
110
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/a-record-subdomain.png" alt-text="Screenshot that shows a DNS records subdomain page.":::
109
111
110
112
#### With a CNAME record
111
113
@@ -116,7 +118,7 @@ Create two records, as described in the following table:
116
118
| CNAME |`<subdomain>` (for example, `www`) | (See the value in the Azure portal **Overview** page for your app.) | The domain mapping itself. |
117
119
| TXT |`asuid.<subdomain>` (for example, `asuid.www`) | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid.<subdomain>` TXT record to verify your ownership of the custom domain. |
118
120
119
-
121
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/cname-record.png" alt-text="Screenshot that shows the portal navigation to an Azure app.":::
120
122
121
123
### [Wildcard (CNAME)](#tab/wildcard)
122
124
@@ -127,7 +129,7 @@ For a wildcard name, like `*` in `*.contoso.com`, create two records, as describ
127
129
| CNAME |`*`| (See the value in the Azure portal **Overview** page for your app.) | The domain mapping itself. |
128
130
| TXT |`asuid`| The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
129
131
130
-
132
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/cname-record-wildcard.png" alt-text="Screenshot that shows the navigation to an Azure app.":::
131
133
132
134
-----
133
135
@@ -142,22 +144,22 @@ For a wildcard name, like `*` in `*.contoso.com`, create two records, as describ
142
144
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/configure-custom-domain-add.png" alt-text="A screenshot showing the Add button activated after validation." border="true":::
143
145
144
146
> [!NOTE]
145
-
> If you configured the TXT record but not the A or CNAME record, App Service treats the change as a [domain migration](manage-custom-dns-migrate-domain.md) scenario and allows the validation to succeed, but you won't see green check marks next to the records.
147
+
> If you configured the TXT record but not the A or CNAME record, App Service treats the change as a [domain migration](manage-custom-dns-migrate-domain.md) scenario and allows the validation to succeed, but you don't see green check marks next to the records.
146
148
147
149
1. You should see the custom domain added to the list. You might also see a red X and the text **No binding**.
148
150
149
-
If you selected **App Service Managed Certificate** earlier, wait a few minutes for App Service to create the managed certificate for your custom domain. When the process is complete, the red X becomes a green check mark and you see the word **Secured**. If you selected **Add certificate later**, the red X will remain until you [add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
151
+
If you selected **App Service Managed Certificate** earlier, wait a few minutes for App Service to create the managed certificate for your custom domain. When the process is complete, the red X becomes a green check mark and you see the word **Secured**. If you selected **Add certificate later**, the red X remains until you [add a private certificate for the domain](configure-ssl-certificate.md) and [configure the binding](configure-ssl-bindings.md).
150
152
151
153
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/add-custom-domain-complete.png" alt-text="A screenshot showing the custom domains page with the new secured custom domain." border="true":::
152
154
153
155
> [!NOTE]
154
-
> Unless you configure a certificate binding for your custom domain, any HTTPS request from a browser to the domain will receive an error or warning, depending on the browser.
156
+
> Unless you configure a certificate binding for your custom domain, any HTTPS request from a browser to the domain receives an error or warning, depending on the browser.
155
157
156
158
## Test the DNS resolution
157
159
158
-
Browse to the DNS names that you configured.
160
+
Browse to the domain name that you configured.
159
161
160
-
162
+
:::image type="content" source="./media/app-service-web-tutorial-custom-domain/app-with-custom-dns.png" alt-text="Screenshot that shows navigation to an Azure app.":::
Copy file name to clipboardExpand all lines: articles/app-service/includes/managed-certs/managed-certs-note.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,5 +7,5 @@ ms.author: msangapu
7
7
---
8
8
9
9
> [!IMPORTANT]
10
-
> Starting July 28, 2025, changes to App Service **Managed Certificates** (ASMC) will impact how certificates are issued and renewed in certain scenarios. While most customers don’t need to take action, we recommend reviewing our [ASMC detailed blog post](https://go.microsoft.com/fwlink/?linkid=2328307) for more information.
10
+
> As of July 28, 2025, changes to App Service Managed Certificates (ASMC) impact how certificates are issued and renewed in certain scenarios. While most customers don’t need to take action, we recommend reviewing our [ASMC detailed blog post](https://go.microsoft.com/fwlink/?linkid=2328307) for more information.
Copy file name to clipboardExpand all lines: articles/azure-vmware/native-internet-connectivity-design-considerations.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,15 +29,18 @@ Internet connectivity using Azure Firewall is similar to the way Azure virtual n
29
29
## Steps:
30
30
31
31
1. Have or create Azure Firewall or a third-party Network Virtual Appliance in the virtual network local to the private cloud or in the peered virtual network.
32
-
1. Define an Azure route table with a 0.0.0.0/0 route pointing to the next-hop type Virtual Appliance with the next-hop IP address of the Azure Firewall private IP or IP of the Network Virtual Appliance.
33
-
1. Associate the route table to the Azure VMware Solution specific virtual network subnets named “avs-nsx-gw” and “avs-nsx-gw-1”, which are part of the virtual network associated with private cloud.
32
+
2.
33
+
3. Adjust the existing the route table to the Azure VMware Solution specific virtual network subnet named "avs-mgmt", required for management appliances, including vCenter, NSX and HCX Manager to communicate outbound.
34
34
35
-
1. Associate the route table to the Azure VMware Solution specific virtual network subnet named "avs-mgmt", required for management appliances, including vCenter, NSX and HCX Manager to communicate outbound.
35
+
4. Define an Azure user defined route with a 0.0.0.0/0 route pointing to the next-hop type Virtual Appliance with the next-hop IP address of the Azure Firewall private IP or IP of the Network Virtual Appliance.
36
+
37
+
5. Associate the route table to the Azure VMware Solution specific virtual network subnets named “avs-nsx-gw” and “avs-nsx-gw-1”, which are part of the virtual network associated with private cloud.
38
+
39
+
6. Have necessary firewall rules to allow traffic to and from the internet.
36
40
37
41
>[!Note]
38
42
>The Azure route tables (UDR), associated with private cloud uplink subnets, and private cloud VNet need to be in the same Azure resource group.
39
43
40
-
4. Have necessary firewall rules to allow traffic to and from the internet.
41
44
42
45
## Related topics
43
46
-[Connectivity to an Azure Virtual Network](native-network-connectivity.md)
Copy file name to clipboardExpand all lines: articles/cost-management-billing/reservations/prepare-buy-reservation.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,6 +67,9 @@ Reservation discounts apply to the following eligible subscriptions and offer ty
67
67
- CSP subscriptions
68
68
- Microsoft Azure Sponsorship subscriptions (offer number: MS-AZR-0036P)
69
69
70
+
> [!NOTE]
71
+
> Reservations may be applied to eligible resources running in Sponsorship-backed subscriptions; however, Azure Sponsorship credits cannot be used to purchase Reservations.
72
+
70
73
Resources that run in a subscription with other offer types don't receive the reservation discount.
71
74
72
75
Some Azure services do not support Reservation (RI) discounts, so it's important to check eligibility before making a purchase to avoid unnecessary costs. For example: Azure SQL Serverless and Azure Cosmos DB serverless
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments