Skip to content

Commit 84c6a1f

Browse files
authored
Merge pull request #228828 from duongau/cdnfreshness8
CDN freshness review (Batch 8)
2 parents cada20f + 2b9350d commit 84c6a1f

8 files changed

+42
-56
lines changed

articles/cdn/cdn-china-delivery.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,12 @@ description: Learn about using Azure Content Delivery Network (CDN) to deliver c
44
services: cdn
55
documentationcenter: ''
66
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
10-
ms.assetid:
7+
manager: kumudd
118
ms.service: azure-cdn
129
ms.workload: tbd
1310
ms.tgt_pltfrm: na
1411
ms.topic: conceptual
15-
ms.date: 05/16/2018
12+
ms.date: 02/27/2023
1613
ms.author: duau
1714
ms.custom: mvc
1815

@@ -22,7 +19,7 @@ ms.custom: mvc
2219

2320
Azure Content Delivery Network (CDN) global can serve content to China users with point-of-presence (POP) locations near China or any POP that provides the best performance to requests originating from China. However, if China is a significant market for your customers and they need fast performance, consider using Azure CDN China instead.
2421

25-
Azure CDN China differs from Azure CDN global in that it delivers content from POPs inside of China by partnering with a number of local providers. Due to Chinese compliance and regulation, you must register a separate subscription to use Azure CDN China and your websites need to have an ICP license. The portal and API experience to enable and manage content delivery is identical between Azure CDN global and Azure CDN China.
22+
Azure CDN China differs from Azure CDN global in that it delivers content from POPs inside of China by partnering with many local providers. Due to Chinese compliance and regulation, you must register a separate subscription to use Azure CDN China and your websites need to have an ICP license. The portal and API experience to enable and manage content delivery is identical between Azure CDN global and Azure CDN China.
2623

2724
## Comparison of Azure CDN global and Azure CDN China
2825

articles/cdn/cdn-ddos.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,32 @@
11
---
22
title: Azure CDN DDoS Protection capabilities | Microsoft Docs
3-
description: Azure CDN from Microsoft is protected by DDoS Protection basic for no additional cost
3+
description: Azure CDN from Microsoft is protected by DDoS Protection basic for no extra cost
44
services: cdn
5-
documentationcenter: ''
65
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
10-
ms.assetid:
6+
manager: kumudd
117
ms.service: azure-cdn
128
ms.workload: tbd
139
ms.tgt_pltfrm: na
1410
ms.topic: article
15-
ms.date: 03/22/2019
11+
ms.date: 02/27/2023
1612
ms.author: duau
1713

1814
---
1915
# Azure CDN DDoS Protection
2016

21-
A content delivery network provides DDoS protection by design. In addition to the global capacity to absorb volumetric attacks, Azure CDN has additional DDoS protection as outlined below, for no extra cost.
17+
A content delivery network provides DDoS protection by design. In addition to the global capacity to absorb volumetric attacks, Azure CDN has extra DDoS protection as outlined in this article, for no extra cost.
2218

2319
## Azure CDN from Microsoft
2420

25-
Azure CDN from Microsoft is protected by [Azure Basic DDoS](../ddos-protection/ddos-protection-overview.md). It is integrated into the Azure CDN from Microsoft platform by default and at no additional cost. The full scale and capacity of Azure CDN from Microsoft’s globally deployed network provides defense against common network layer attacks through always-on traffic monitoring and real-time mitigation. Basic DDoS protection also defends against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints. This service also has a proven track record in protecting Microsoft’s enterprise and consumer services from large-scale attacks.
21+
Azure CDN from Microsoft is protected by [Azure Basic DDoS](../ddos-protection/ddos-protection-overview.md). It's integrated into the Azure CDN from Microsoft platform by default and at no extra cost. The full scale and capacity of Azure CDN from Microsoft’s globally deployed network provides defense against common network layer attacks through always-on traffic monitoring and real-time mitigation. Basic DDoS protection also defends against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints. This service also has a proven track record in protecting Microsoft’s enterprise and consumer services from large-scale attacks.
2622

2723
## Azure CDN from Verizon
2824

29-
Azure CDN from Verizon is protected by Verzion's proprietary DDoS mitigation platform. It's integrated into Azure CDN from Verizon by default and at no additional cost. It provides basic protection against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints.
25+
Azure CDN from Verizon is protected by Verizon's proprietary DDoS mitigation platform. It's integrated into Azure CDN from Verizon by default and at no extra cost. It provides basic protection against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints.
3026

3127
## Azure CDN from Akamai
3228

33-
Azure CDN from Akamai is protected by Akamai's proprietary DDoS mitigation platform. It's integrated into Azure CDN from Akamai by default and at no additional cost. It provides basic protection against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints.
29+
Azure CDN from Akamai is protected by Akamai's proprietary DDoS mitigation platform. It's integrated into Azure CDN from Akamai by default and at no extra cost. It provides basic protection against the most common, frequently occurring Layer 7 DNS Query Floods and Layer 3 and 4 volumetric attacks that target CDN endpoints.
3430

3531
## Next steps
3632

articles/cdn/cdn-manage-powershell.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,20 @@ description: Use this tutorial to learn how to use PowerShell to manage aspects
44
services: cdn
55
documentationcenter: ''
66
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
7+
manager: kumudd
108
ms.assetid: fb6f57a5-6e26-4847-8fd9-b51fb05a79eb
119
ms.service: azure-cdn
1210
ms.workload: tbd
1311
ms.tgt_pltfrm: na
1412
ms.topic: how-to
15-
ms.date: 11/20/2019
13+
ms.date: 02/27/2023
1614
ms.author: duau
1715
ms.custom: devx-track-azurepowershell
1816

1917
---
18+
2019
# Manage Azure CDN with PowerShell
20+
2121
PowerShell provides one of the most flexible methods to manage your Azure CDN profiles and endpoints. You can use PowerShell interactively or by writing scripts to automate management tasks. This tutorial demonstrates several of the most common tasks you can accomplish with PowerShell to manage your Azure CDN profiles and endpoints.
2222

2323
## Prerequisites
@@ -32,6 +32,7 @@ To use PowerShell to manage your Azure CDN profiles and endpoints, you must have
3232
>
3333
3434
## Listing the Azure CDN cmdlets
35+
3536
You can list all the Azure CDN cmdlets using the `Get-Command` cmdlet.
3637

3738
```text

articles/cdn/cdn-media-streaming-optimization.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,22 +2,18 @@
22
title: Media streaming optimization with Azure CDN
33
description: Learn about options to optimize streaming media in Azure Content Delivery Network, such as partial cache sharing and cache fill wait time.
44
services: cdn
5-
documentationcenter: ''
65
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
10-
ms.assetid:
6+
manager: kumudd
117
ms.service: azure-cdn
128
ms.workload: tbd
139
ms.tgt_pltfrm: na
1410
ms.topic: how-to
15-
ms.date: 05/01/2018
11+
ms.date: 02/27/2023
1612
ms.author: duau
1713
---
1814
# Media streaming optimization with Azure CDN
1915

20-
Use of high-definition video is increasing on the internet, which creates difficulties for efficient delivery of large files. Customers expect smooth playback of video on demand or live video assets on a variety of networks and clients all over the world. A fast and efficient delivery mechanism for media streaming files is critical to ensure a smooth and enjoyable consumer experience.
16+
Use of high-definition video is increasing on the internet, which creates difficulties for efficient delivery of large files. Customers expect smooth playback of video on demand or live video assets on various networks and clients all over the world. A fast and efficient delivery mechanism for media streaming files is critical to ensure a smooth and enjoyable consumer experience.
2117

2218
Live streaming media is especially difficult to deliver because of the large sizes and number of concurrent viewers. Long delays cause users to leave. Because live streams can't be cached ahead of time and large latencies aren't acceptable to viewers, video fragments must be delivered in a timely manner.
2319

@@ -33,12 +29,13 @@ Media streaming optimization for **Azure CDN Standard from Microsoft** is effect
3329
The general media delivery or video-on-demand media delivery optimization types use Azure Content Delivery Network (CDN) with back-end optimizations to deliver media assets faster. They also use configurations for media assets based on best practices learned over time.
3430

3531
### Partial cache sharing
32+
3633
Partial cache sharing allows the CDN to serve partially cached content to new requests. For example, if the first request to the CDN results in a cache miss, the request is sent to the origin. Although this incomplete content is loaded into the CDN cache, other requests to the CDN can start getting this data.
3734

3835

3936
## Media streaming optimizations for Azure CDN from Verizon
4037

41-
**Azure CDN Standard from Verizon** and **Azure CDN Premium from Verizon** endpoints deliver streaming media assets directly by using the general web delivery optimization type. A few features on the CDN directly assist in delivering media assets by default.
38+
**Azure CDN Standard from Verizon** and **Azure CDN Premium from Verizon** endpoints deliver streaming media assets directly by using the general web delivery optimization type. A few features on the CDN directly help delivering media assets by default.
4239

4340
### Partial cache sharing
4441

@@ -59,7 +56,7 @@ The general media delivery or video-on-demand media delivery optimization types
5956

6057
### Configure an Akamai CDN endpoint to optimize media streaming
6158

62-
You can configure your content delivery network (CDN) endpoint to optimize delivery for large files via the Azure portal. You can also use the REST APIs or any of the client SDKs to do this. The following steps show the process via the Azure portal for an **Azure CDN Standard from Akamai** profile:
59+
You can configure your content delivery network (CDN) endpoint to optimize delivery for large files via the Azure portal. You can also use the REST APIs or any of the client SDKs to optimize the delivery of large files. The following steps show the process via the Azure portal for an **Azure CDN Standard from Akamai** profile:
6360

6461
1. To add a new endpoint, on an Akamai **CDN profile** page, select **Endpoint**.
6562

@@ -73,20 +70,20 @@ After you create the endpoint, it applies the optimization for all files that ma
7370

7471
### Caching
7572

76-
If **Azure CDN Standard from Akamai** detects that the asset is a streaming manifest or fragment, it uses different caching expiration times from general web delivery. (See the full list in the following table.) As always, cache-control or Expires headers sent from the origin are honored. If the asset is not a media asset, it caches by using the expiration times for general web delivery.
73+
If **Azure CDN Standard from Akamai** detects that the asset is a streaming manifest or fragment, it uses different caching expiration times from general web delivery. (See the full list in the following table.) As always, cache-control or Expires headers sent from the origin are honored. If the asset isn't a media asset, it caches by using the expiration times for general web delivery.
7774

7875
The short negative caching time is useful for origin offload when many users request a fragment that doesn’t exist yet. An example is a live stream where the packets aren't available from the origin that second. The longer caching interval also helps offload requests from the origin because video content isn't typically modified.
7976

8077
| Caching | General web delivery | General media streaming | Video-on-demand media streaming
8178
|--- | --- | --- | ---
82-
| Caching: Positive <br> HTTP 200, 203, 300, <br> 301, 302, and 410 | 7 days |365 days | 365 days
79+
| Caching: Positive <br> HTTP 200, 203, 300, <br> 301, 302, and 410 | Seven days |365 days | 365 days
8380
| Caching: Negative <br> HTTP 204, 305, 404, <br> and 405 | None | 1 second | 1 second
8481

8582
### Deal with origin failure
8683

8784
General media delivery and video-on-demand media delivery also have origin timeouts and a retry log based on best practices for typical request patterns. For example, because general media delivery is for live and video-on-demand media delivery, it uses a shorter connection timeout due to the time-sensitive nature of live streaming.
8885

89-
When a connection times out, the CDN retries a number of times before it sends a "504 - Gateway Timeout" error to the client.
86+
When a connection times out, the CDN retries many times before it sends a "504 - Gateway Timeout" error to the client.
9087

9188
When a file matches the file type and size conditions list, the CDN uses the behavior for media streaming. Otherwise, it uses general web delivery.
9289

articles/cdn/cdn-migrate.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,13 @@
22
title: Migrate Azure CDN profile from Verizon Standard to Verizon Premium
33
description: Learn about the details of migrating a profile from Verizon Standard to Verizon Premium.
44
services: cdn
5-
documentationcenter: ''
65
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
10-
ms.assetid:
6+
manager: kumudd
117
ms.service: azure-cdn
128
ms.workload: tbd
139
ms.tgt_pltfrm: na
1410
ms.topic: how-to
15-
ms.date: 06/21/2018
11+
ms.date: 02/27/2023
1612
ms.author: duau
1713
ms.custom:
1814

@@ -21,7 +17,7 @@ ms.custom:
2117

2218
When you create an Azure Content Delivery Network (CDN) profile to manage your endpoints, Azure CDN offers four different products for you to choose from. For information about the different products and their available features, see [Compare Azure CDN product features](cdn-features.md).
2319

24-
If you've create an **Azure CDN Standard from Verizon** profile and are using it to manage your CDN endpoints, you have the option to upgrade it to an **Azure CDN Premium from Verizon** profile. When you upgrade, your CDN endpoints and all of your data will be preserved.
20+
If you've create an **Azure CDN Standard from Verizon** profile and are using it to manage your CDN endpoints, you can upgrade it to an **Azure CDN Premium from Verizon** profile. When you upgrade, your CDN endpoints and all of your data gets preserved.
2521

2622
> [!IMPORTANT]
2723
> Once you've upgraded to an **Azure CDN Premium from Verizon** profile, you cannot later convert it back to an **Azure CDN Standard from Verizon** profile.
@@ -31,11 +27,11 @@ To upgrade an **Azure CDN Standard from Verizon** profile, contact [Microsoft Su
3127

3228
## Profile comparison
3329
**Azure CDN Premium from Verizon** profiles have the following key differences from **Azure CDN Standard from Verizon** profiles:
34-
- For certain Azure CDN features such as [compression](cdn-improve-performance.md), [caching rules](cdn-caching-rules.md), and [geo filtering](cdn-restrict-access-by-country-region.md), you cannot use the Azure CDN interface, you must use the Verizon portal via the **Manage** button.
35-
- API: Unlike with Standard Verizon, you cannot use the API to control those features that are accessed from the Premium Verizon portal. However, you can use the API to control other common features, such as creating/deleting an endpoint, purging/loading cached assets, and enabling/disabling a custom domain.
30+
- For certain Azure CDN features such as [compression](cdn-improve-performance.md), [caching rules](cdn-caching-rules.md), and [geo filtering](cdn-restrict-access-by-country-region.md), you can't use the Azure CDN interface, you must use the Verizon portal via the **Manage** button.
31+
- API: Unlike with Standard Verizon, you can't use the API to control those features that are accessed from the Premium Verizon portal. However, you can use the API to control other common features, such as creating/deleting an endpoint, purging/load cached assets, and enabling/disable a custom domain.
3632
- Pricing: Premium Verizon has a different pricing structure for data transfers than Standard Verizon. For more information, see [Content Delivery Network pricing](https://azure.microsoft.com/pricing/details/cdn/).
3733

38-
**Azure CDN Premium from Verizon** profiles have the following additional features:
34+
**Azure CDN Premium from Verizon** profiles have the following extra features:
3935
- [Token authentication](cdn-token-auth.md): Allows users to obtain and use a token to fetch secure resources.
4036
- [Rules engine](./cdn-verizon-premium-rules-engine.md): Enables you to customize how HTTP requests are handled.
4137
- Advanced analytics tools:

articles/cdn/cdn-preload-endpoint.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,22 @@
22
title: Pre-load assets on an Azure CDN endpoint | Microsoft Docs
33
description: Learn how to pre-load cached content on an Azure Content Delivery Network endpoint. This feature is available on certain versions of the product.
44
services: cdn
5-
documentationcenter: ''
65
author: duongau
7-
manager: danielgi
8-
editor: ''
9-
6+
manager: kumudd
107
ms.assetid: 5ea3eba5-1335-413e-9af3-3918ce608a83
118
ms.service: azure-cdn
129
ms.workload: tbd
1310
ms.tgt_pltfrm: na
1411
ms.topic: how-to
15-
ms.date: 02/12/2018
12+
ms.date: 02/27/2023
1613
ms.author: duau
17-
1814
---
15+
1916
# Pre-load assets on an Azure CDN endpoint
17+
2018
[!INCLUDE [cdn-verizon-only](../../includes/cdn-verizon-only.md)]
2119

22-
By default, assets are cached only when they're requested. Because the edge servers have not yet cached the content and need to forward the request to the origin server, the first request from each region can take longer than subsequent requests. To avoid this first-hit latency, pre-load your assets. In addition to providing a better customer experience, pre-loading your cached assets can reduce network traffic on the origin server.
20+
By default, assets are cached only when they're requested. Because the edge servers haven't yet cached the content and need to forward the request to the origin server, the first request from each region can take longer than subsequent requests. To avoid this first-hit latency, pre-load your assets. In addition to providing a better customer experience, pre-loading your cached assets can reduce network traffic on the origin server.
2321

2422
> [!NOTE]
2523
> Pre-loading assets is useful for large events or content that becomes simultaneously available to many users, such as a new movie release or a software update.
@@ -31,7 +29,7 @@ This tutorial walks you through pre-loading cached content on all Azure CDN edge
3129
## To pre-load assets
3230
1. In the [Azure portal](https://portal.azure.com), browse to the CDN profile containing the endpoint you wish to pre-load. The profile pane opens.
3331

34-
2. Click the endpoint in the list. The endpoint pane opens.
32+
2. Select the endpoint in the list. The endpoint pane opens.
3533
3. From the CDN endpoint pane, select **Load**.
3634

3735
![CDN endpoint pane](./media/cdn-preload-endpoint/cdn-endpoint-blade.png)
@@ -53,7 +51,7 @@ This tutorial walks you through pre-loading cached content on all Azure CDN edge
5351
>
5452
5553
![Load button](./media/cdn-preload-endpoint/cdn-load-paths.png)
56-
5. When you are finished entering content paths, select **Load**.
54+
5. When you're finished entering content paths, select **Load**.
5755

5856

5957
> [!NOTE]

articles/cdn/cdn-traffic-manager.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,10 @@ titleSuffix: Azure Content Delivery Network
44
description: Learn how to configure failover across multiple Azure Content Delivery Network endpoints by using Azure Traffic Manager.
55
services: cdn
66
author: duongau
7+
manager: kumudd
78
ms.service: azure-cdn
89
ms.topic: how-to
9-
ms.date: 10/08/2020
10+
ms.date: 02/27/2023
1011
ms.author: duau
1112
ms.custom:
1213

0 commit comments

Comments
 (0)