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/cdn/cdn-china-delivery.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,12 @@ description: Learn about using Azure Content Delivery Network (CDN) to deliver c
4
4
services: cdn
5
5
documentationcenter: ''
6
6
author: duongau
7
-
manager: danielgi
8
-
editor: ''
9
-
10
-
ms.assetid:
7
+
manager: kumudd
11
8
ms.service: azure-cdn
12
9
ms.workload: tbd
13
10
ms.tgt_pltfrm: na
14
11
ms.topic: conceptual
15
-
ms.date: 05/16/2018
12
+
ms.date: 02/27/2023
16
13
ms.author: duau
17
14
ms.custom: mvc
18
15
@@ -22,7 +19,7 @@ ms.custom: mvc
22
19
23
20
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.
24
21
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.
26
23
27
24
## Comparison of Azure CDN global and Azure CDN China
Copy file name to clipboardExpand all lines: articles/cdn/cdn-ddos.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,32 @@
1
1
---
2
2
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
4
4
services: cdn
5
-
documentationcenter: ''
6
5
author: duongau
7
-
manager: danielgi
8
-
editor: ''
9
-
10
-
ms.assetid:
6
+
manager: kumudd
11
7
ms.service: azure-cdn
12
8
ms.workload: tbd
13
9
ms.tgt_pltfrm: na
14
10
ms.topic: article
15
-
ms.date: 03/22/2019
11
+
ms.date: 02/27/2023
16
12
ms.author: duau
17
13
18
14
---
19
15
# Azure CDN DDoS Protection
20
16
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.
22
18
23
19
## Azure CDN from Microsoft
24
20
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.
26
22
27
23
## Azure CDN from Verizon
28
24
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.
30
26
31
27
## Azure CDN from Akamai
32
28
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.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-manage-powershell.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,20 +4,20 @@ description: Use this tutorial to learn how to use PowerShell to manage aspects
4
4
services: cdn
5
5
documentationcenter: ''
6
6
author: duongau
7
-
manager: danielgi
8
-
editor: ''
9
-
7
+
manager: kumudd
10
8
ms.assetid: fb6f57a5-6e26-4847-8fd9-b51fb05a79eb
11
9
ms.service: azure-cdn
12
10
ms.workload: tbd
13
11
ms.tgt_pltfrm: na
14
12
ms.topic: how-to
15
-
ms.date: 11/20/2019
13
+
ms.date: 02/27/2023
16
14
ms.author: duau
17
15
ms.custom: devx-track-azurepowershell
18
16
19
17
---
18
+
20
19
# Manage Azure CDN with PowerShell
20
+
21
21
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.
22
22
23
23
## Prerequisites
@@ -32,6 +32,7 @@ To use PowerShell to manage your Azure CDN profiles and endpoints, you must have
32
32
>
33
33
34
34
## Listing the Azure CDN cmdlets
35
+
35
36
You can list all the Azure CDN cmdlets using the `Get-Command` cmdlet.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-media-streaming-optimization.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,22 +2,18 @@
2
2
title: Media streaming optimization with Azure CDN
3
3
description: Learn about options to optimize streaming media in Azure Content Delivery Network, such as partial cache sharing and cache fill wait time.
4
4
services: cdn
5
-
documentationcenter: ''
6
5
author: duongau
7
-
manager: danielgi
8
-
editor: ''
9
-
10
-
ms.assetid:
6
+
manager: kumudd
11
7
ms.service: azure-cdn
12
8
ms.workload: tbd
13
9
ms.tgt_pltfrm: na
14
10
ms.topic: how-to
15
-
ms.date: 05/01/2018
11
+
ms.date: 02/27/2023
16
12
ms.author: duau
17
13
---
18
14
# Media streaming optimization with Azure CDN
19
15
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.
21
17
22
18
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.
23
19
@@ -33,12 +29,13 @@ Media streaming optimization for **Azure CDN Standard from Microsoft** is effect
33
29
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.
34
30
35
31
### Partial cache sharing
32
+
36
33
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.
37
34
38
35
39
36
## Media streaming optimizations for Azure CDN from Verizon
40
37
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.
42
39
43
40
### Partial cache sharing
44
41
@@ -59,7 +56,7 @@ The general media delivery or video-on-demand media delivery optimization types
59
56
60
57
### Configure an Akamai CDN endpoint to optimize media streaming
61
58
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:
63
60
64
61
1. To add a new endpoint, on an Akamai **CDN profile** page, select **Endpoint**.
65
62
@@ -73,20 +70,20 @@ After you create the endpoint, it applies the optimization for all files that ma
73
70
74
71
### Caching
75
72
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.
77
74
78
75
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.
79
76
80
77
| Caching | General web delivery | General media streaming | Video-on-demand media streaming
81
78
|--- | --- | --- | ---
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
83
80
| Caching: Negative <br> HTTP 204, 305, 404, <br> and 405 | None | 1 second | 1 second
84
81
85
82
### Deal with origin failure
86
83
87
84
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.
88
85
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.
90
87
91
88
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.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-migrate.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,13 @@
2
2
title: Migrate Azure CDN profile from Verizon Standard to Verizon Premium
3
3
description: Learn about the details of migrating a profile from Verizon Standard to Verizon Premium.
4
4
services: cdn
5
-
documentationcenter: ''
6
5
author: duongau
7
-
manager: danielgi
8
-
editor: ''
9
-
10
-
ms.assetid:
6
+
manager: kumudd
11
7
ms.service: azure-cdn
12
8
ms.workload: tbd
13
9
ms.tgt_pltfrm: na
14
10
ms.topic: how-to
15
-
ms.date: 06/21/2018
11
+
ms.date: 02/27/2023
16
12
ms.author: duau
17
13
ms.custom:
18
14
@@ -21,7 +17,7 @@ ms.custom:
21
17
22
18
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).
23
19
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.
25
21
26
22
> [!IMPORTANT]
27
23
> 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
31
27
32
28
## Profile comparison
33
29
**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.
36
32
- 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/).
37
33
38
-
**Azure CDN Premium from Verizon** profiles have the following additional features:
34
+
**Azure CDN Premium from Verizon** profiles have the following extra features:
39
35
-[Token authentication](cdn-token-auth.md): Allows users to obtain and use a token to fetch secure resources.
40
36
-[Rules engine](./cdn-verizon-premium-rules-engine.md): Enables you to customize how HTTP requests are handled.
Copy file name to clipboardExpand all lines: articles/cdn/cdn-preload-endpoint.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,24 +2,22 @@
2
2
title: Pre-load assets on an Azure CDN endpoint | Microsoft Docs
3
3
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.
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.
23
21
24
22
> [!NOTE]
25
23
> 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
31
29
## To pre-load assets
32
30
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.
33
31
34
-
2.Click the endpoint in the list. The endpoint pane opens.
32
+
2.Select the endpoint in the list. The endpoint pane opens.
0 commit comments