|
2 | 2 | title: Create an Azure CDN endpoint | Microsoft Docs
|
3 | 3 | description: This article shows how to create a new Azure Content Delivery Network (CDN) endpoint, including advanced settings.
|
4 | 4 | services: cdn
|
5 |
| -documentationcenter: '' |
6 | 5 | author: duongau
|
7 |
| -manager: danielgi |
8 |
| -editor: '' |
9 |
| - |
| 6 | +manager: kumudd |
10 | 7 | ms.service: azure-cdn
|
11 | 8 | ms.workload: media
|
12 | 9 | ms.tgt_pltfrm: na
|
13 | 10 | ms.topic: how-to
|
14 |
| -ms.date: 09/09/2021 |
| 11 | +ms.date: 02/27/2023 |
15 | 12 | ms.author: duau
|
16 | 13 | ms.custom: mvc
|
17 |
| - |
18 | 14 | ---
|
| 15 | + |
19 | 16 | # Create an Azure CDN endpoint
|
| 17 | + |
20 | 18 | This article describes all the settings for creating an [Azure Content Delivery Network (CDN)](cdn-overview.md) endpoint in an existing CDN profile. After you've created a profile and an endpoint, you can start delivering content to your customers. For a quickstart on creating a profile and endpoint, see [Quickstart: Create an Azure CDN profile and endpoint](cdn-create-new-endpoint.md).
|
21 | 19 |
|
22 | 20 | ## Prerequisites
|
| 21 | + |
23 | 22 | Before you can create a CDN endpoint, you must have created at least one CDN profile, which can contain one or more CDN endpoints. To organize your CDN endpoints by internet domain, web application, or some other criteria, you can use multiple profiles. Because CDN pricing is applied at the CDN profile level, you must create multiple CDN profiles if you want to use a mix of Azure CDN pricing tiers. To create a CDN profile, see [Create a new CDN profile](cdn-create-new-endpoint.md#create-a-new-cdn-profile).
|
24 | 23 |
|
25 |
| -## Log in to the Azure portal |
26 |
| -Log in to the [Azure portal](https://portal.azure.com) with your Azure account. |
| 24 | +## Sign in to the Azure portal |
| 25 | + |
| 26 | +Sign in to the [Azure portal](https://portal.azure.com) with your Azure account. |
27 | 27 |
|
28 | 28 | ## Create a new CDN endpoint
|
29 | 29 |
|
@@ -94,13 +94,13 @@ Log in to the [Azure portal](https://portal.azure.com) with your Azure account.
|
94 | 94 | - For **Azure CDN Standard from Akamai** profiles, propagation usually completes within one minute.
|
95 | 95 | - For **Azure CDN Standard from Verizon** and **Azure CDN Premium from Verizon** profiles, propagation usually completes within 30 minutes.
|
96 | 96 |
|
97 |
| - If you attempt to use the CDN domain name before the endpoint configuration has propagated to the point-of-presence (POP) servers, you might receive an HTTP 404 response status. If it's been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure CDN endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md). |
| 97 | + If you attempt to use the CDN domain name before the endpoint configuration has propagated to the point-of-presence (POP) servers, you might receive an HTTP 404 response status. If it has been several hours since you created your endpoint and you're still receiving a 404 response status, see [Troubleshooting Azure CDN endpoints that return a 404 status code](cdn-troubleshoot-endpoint.md). |
98 | 98 |
|
99 | 99 | > [!NOTE]
|
100 | 100 | > For *Verizon CDN endpoints*, when an endpoint is **disabled** or **stopped** for any reason, all resources configured through the Verizon supplemental portal will be cleaned up. These configurations can't be restored automatically by restarting the endpoint. You will need to make those configuration changes again.
|
101 | 101 |
|
102 | 102 | ## Clean up resources
|
103 |
| -To delete an endpoint when it is no longer needed, select it and then select **Delete**. |
| 103 | +To delete an endpoint when it's no longer needed, select it and then select **Delete**. |
104 | 104 |
|
105 | 105 | ## Next steps
|
106 | 106 | To learn about custom domains, continue to the tutorial for adding a custom domain to your CDN endpoint.
|
|
0 commit comments