Merge pull request #228814 from duongau/cdnfreshness4

CDN freshness review (Batch 4)

Author: JamesJBarnett

articles/cdn/cdn-add-to-web-app.md

@@ -2,30 +2,27 @@
 title: Tutorial - Add Azure CDN to an Azure App Service web app | Microsoft Docs
 description: In this tutorial, Azure Content Delivery Network (CDN) is added to an Azure App Service web app to cache and deliver your static files from servers close to your customers around the world.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
+manager: kumudd
 ms.assetid: 
 ms.service: azure-cdn
 ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.topic: tutorial
-ms.date: 05/14/2018
+ms.date: 02/27/2023
 ms.author: duau
 ms.custom: mvc
-
 ---
+
 # Tutorial: Add Azure CDN to an Azure App Service web app
 
-This tutorial shows how to add [Azure Content Delivery Network (CDN)](cdn-overview.md) to a [web app in Azure App Service](../app-service/overview.md). Web apps is a service for hosting web applications, REST APIs, and mobile back ends. 
+This tutorial shows how to add [Azure Content Delivery Network (CDN)](cdn-overview.md) to a [web app in Azure App Service](../app-service/overview.md). Web apps are services for hosting web applications, REST APIs, and mobile back ends. 
 
-Here's the home page of the sample static HTML site that you'll work with:
+Here's the home page of the sample static HTML site that you work with:
 
 ![Sample app home page](media/cdn-add-to-web-app/sample-app-home-page.png)
 
-What you'll learn:
+What you learn:
 
 > [!div class="checklist"]
 > * Create a CDN endpoint.
@@ -44,29 +41,29 @@ To complete this tutorial:
 
 ## Create the web app
 
-To create the web app that you'll work with, follow the [static HTML quickstart](../app-service/quickstart-html.md) through the **Browse to the app** step.
+To create the web app that you work with, follow the [static HTML quickstart](../app-service/quickstart-html.md) through the **Browse to the app** step.
 
-## Log in to the Azure portal
+## Sign in to the Azure portal
 
 Open a browser and navigate to the [Azure portal](https://portal.azure.com).
 
 ### Dynamic site acceleration optimization
 If you want to optimize your CDN endpoint for dynamic site acceleration (DSA), you should use the [CDN portal](cdn-create-new-endpoint.md) to create your profile and endpoint. With [DSA optimization](cdn-dynamic-site-acceleration.md), the performance of web pages with dynamic content is measurably improved. For instructions about how to optimize a CDN endpoint for DSA from the CDN portal, see [CDN endpoint configuration to accelerate delivery of dynamic files](cdn-dynamic-site-acceleration.md#cdn-endpoint-configuration-to-accelerate-delivery-of-dynamic-files). 
-Otherwise, if you don't want to optimize your new endpoint, you can use the web app portal to create it by following the steps in the next section. Note that for **Azure CDN from Verizon** profiles, you cannot change the optimization of a CDN endpoint after it has been created.
+Otherwise, if you don't want to optimize your new endpoint, you can use the web app portal to create it by following the steps in the next section. For **Azure CDN from Verizon** profiles, you can't change the optimization of a CDN endpoint after it has been created.
 
 ## Create a CDN profile and endpoint
 
 In the left navigation, select **App Services**, and then select the app that you created in the [static HTML quickstart](../app-service/quickstart-html.md).
 
-![Select App Service app in the portal](media/cdn-add-to-web-app/portal-select-app-services.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-app-services.png" alt-text="Screenshot of select an App Service app in the portal.":::
 
-In the **App Service** page, in the **Settings** section, select **Networking > Configure Azure CDN for your app**.
+In the **App Service** page, in the **Settings** section, select **Networking > Azure CDN**.
 
-![Select CDN in the portal](media/cdn-add-to-web-app/portal-select-cdn.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-cdn.png" alt-text="Screenshot of select Azure CDN from networking setting of an App Service.":::
 
 In the **Azure Content Delivery Network** page, provide the **New endpoint** settings as specified in the table.
 
-![Create profile and endpoint in the portal](media/cdn-add-to-web-app/portal-new-endpoint.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-new-endpoint.png" alt-text="Screenshot of create Azure CDN profile and endpoint in the portal.":::
 
 | Setting | Suggested value | Description |
 | ------- | --------------- | ----------- |
@@ -78,7 +75,7 @@ Select **Create** to create a CDN profile.
 
 Azure creates the profile and endpoint. The new endpoint appears in the **Endpoints** list, and when it's provisioned, the status is **Running**.
 
-![New endpoint in list](media/cdn-add-to-web-app/portal-new-endpoint-in-list.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-new-endpoint-in-list.png" alt-text="Screenshot of new Azure CDN endpoint in list.":::
 
 ### Test the CDN endpoint
 
@@ -142,7 +139,7 @@ http://<appname>.azurewebsites.net/index.html
 
 ![V2 in title in web app](media/cdn-add-to-web-app/v2-in-web-app-title.png)
 
-If you browse to the CDN endpoint URL for the home page, you won't see the change because the cached version in the CDN hasn't expired yet. 
+If you browse to the CDN endpoint URL for the home page, you don't see the changes because the cached version in the CDN hasn't expired yet. 
 
 ```
 http://<endpointname>.azureedge.net/index.html
@@ -156,29 +153,29 @@ To trigger the CDN to update its cached version, purge the CDN.
 
 In the portal left navigation, select **Resource groups**, and then select the resource group that you created for your web app (myResourceGroup).
 
-![Select resource group](media/cdn-add-to-web-app/portal-select-group.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-group.png" alt-text="Screenshot of selecting resource group from left menu pane in the portal.":::
 
 In the list of resources, select your CDN endpoint.
 
-![Select endpoint](media/cdn-add-to-web-app/portal-select-endpoint.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-endpoint.png" alt-text="Screenshot of Azure CDN endpoint from resource group.":::
 
 At the top of the **Endpoint** page, select **Purge**.
 
-![Select Purge](media/cdn-add-to-web-app/portal-select-purge.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-purge.png" alt-text="Screenshot of purge button in an Azure CDN profile.":::
 
 Enter the content paths you want to purge. You can pass a complete file path to purge an individual file, or a path segment to purge and refresh all content in a folder. Because you changed *index.html*, ensure that is in one of the paths.
 
 At the bottom of the page, select **Purge**.
 
-![Purge page](media/cdn-add-to-web-app/app-service-web-purge-cdn.png)
+:::image type="content" source="./media/cdn-add-to-web-app/app-service-web-purge-cdn.png" alt-text="Screenshot of purge page in an Azure CDN profile.":::
 
 ### Verify that the CDN is updated
 
 Wait until the purge request finishes processing, which is typically a couple of minutes. To see the current status, select the bell icon at the top of the page. 
 
-![Purge notification](media/cdn-add-to-web-app/portal-purge-notification.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-purge-notification.png" alt-text="Screenshot of purge notification for an Azure CDN profile.":::
 
-When you browse to the CDN endpoint URL for *index.html*, you'll see the *V2* that you added to the title on the home page, which indicates that the CDN cache has been refreshed.
+When you browse to the CDN endpoint URL for *index.html*, you see the *V2* that you added to the title on the home page, which indicates that the CDN cache has been refreshed.
 
 ```
 http://<endpointname>.azureedge.net/index.html
@@ -196,7 +193,7 @@ Azure CDN offers the following caching behavior options:
 * Bypass caching for query strings
 * Cache every unique URL 
 
-The first option is the default, which means there is only one cached version of an asset regardless of the query string in the URL. 
+The first option is the default, which means there's only one cached version of an asset regardless of the query string in the URL. 
 
 In this section of the tutorial, you change the caching behavior to cache every unique URL.
 
@@ -208,7 +205,7 @@ Select **Cache every unique URL** from the **Query string caching behavior** dro
 
 Select **Save**.
 
-![Select query string caching behavior](media/cdn-add-to-web-app/portal-select-caching-behavior.png)
+:::image type="content" source="./media/cdn-add-to-web-app/portal-select-caching-behavior.png" alt-text="Screenshot of cache rules settings for an Azure CDN profile.":::
 
 ### Verify that unique URLs are cached separately
 

articles/cdn/cdn-billing.md

@@ -2,17 +2,13 @@
 title: Understanding Azure CDN billing | Microsoft Docs
 description: Learn about the billing structure for content hosted by Azure Content Delivery Network, including billing regions, delivery charges, and to manage costs.
 services: cdn
-documentationcenter: ''
 author: duongau
-manager: danielgi
-editor: ''
-
-ms.assetid: 
+manager: kumudd
 ms.service: azure-cdn
 ms.workload: media
 ms.tgt_pltfrm: na
 ms.topic: article
-ms.date: 09/13/2019
+ms.date: 02/27/2023
 ms.author: duau
 
 ---
@@ -21,6 +17,7 @@ ms.author: duau
 This FAQ describes the billing structure for content hosted by Azure Content Delivery Network (CDN).
 
 ## What is a billing region?
+
 A billing region is a geographic area used to determine what rate is charged for delivery of objects from Azure CDN. The current billing zones and their regions are as follows:
 
 - Zone 1: North America, Europe, Middle East, and Africa
@@ -38,17 +35,17 @@ For information about point-of-presence (POP) regions, see [Azure CDN POP locati
 For information about Azure CDN pricing, see [Content Delivery Network pricing](https://azure.microsoft.com/pricing/details/cdn/).
 
 ## How are delivery charges calculated by region?
-The Azure CDN billing region is based on the location of the source server delivering the content to the end user. The destination (physical location) of the client is not considered the billing region.
+The Azure CDN billing region is based on the location of the source server delivering the content to the end user. The destination (physical location) of the client isn't considered the billing region.
 
-For example, if a user located in Mexico issues a request and this request is serviced by a server located in a United States POP due to peering or traffic conditions, the billing region will be the United States.
+For example, if a user located in Mexico issues a request and this request gets serviced by a server located in a United States POP due to peering or traffic conditions, the billing region is the United States.
 
 ## What is a billable Azure CDN transaction?
-Any HTTP(S) request that terminates at the CDN is a billable event, which includes all response types: success, failure, or other. However, different responses may generate different traffic amounts. For example, *304 Not Modified* and other header-only responses generate little traffic because they are a small header response; similarly, error responses (for example, *404 Not Found*) are billable but incur a small cost because of the tiny response payload.
+Any HTTP(S) request that terminates at the CDN is a billable event, which includes all response types: success, failure, or other. However, different responses may generate different traffic amounts. For example, *304 Not Modified* and other header-only responses generate little traffic because they're a small header response. Similarly, error responses (for example, *404 Not Found*) are billable but incur a small cost because of the tiny response payload.
 
 ## What other Azure costs are associated with Azure CDN use?
 Using Azure CDN also incurs some usage charges on the services used as the origin for your objects. These costs are typically a small fraction of the overall CDN usage cost.
 
-If you are using Azure Blob storage as the origin for your content, you also incur the following storage charges for cache fills:
+If you're using Azure Blob storage as the origin for your content, you also incur the following storage charges for cache fills:
 
 - Actual GB used: The actual storage of your source objects.
 
@@ -57,11 +54,11 @@ If you are using Azure Blob storage as the origin for your content, you also inc
 - Transfers in GB: The amount of data transferred to fill the CDN caches.
 
 > [!NOTE]
-> Starting October 2019, If you are using Azure CDN from Microsoft, the cost of data transfer from Origins hosted in Azure to CDN PoPs is free of charge. Azure CDN from Verizon and Azure CDN from Akamai are subject to the rates described below.
+> Starting October 2019, If you are using Azure CDN from Microsoft, the cost of data transfer from Origins hosted in Azure to CDN PoPs is free of charge. Azure CDN from Verizon and Azure CDN from Akamai are subject to the rates described as followed.
 
 For more information about Azure Storage billing, see [Plan and manage costs for Azure Storage](../storage/common/storage-plan-manage-costs.md).
 
-If you are using *hosted service delivery*, you will incur charges as follows:
+If you're using *hosted service delivery*, you incur charges as follows:
 
 - Azure compute time: The compute instances that act as the origin.
 
@@ -74,16 +71,16 @@ If your client uses byte-range requests (regardless of origin service), the foll
 - When a request arrives for only part of an object (by specifying a byte-range header), the CDN may fetch the entire object into its cache. As a result, even though the billable transaction from the CDN is for a partial response, the billable transaction from the origin may involve the full size of the object.
 
 ## How much transfer activity occurs to support the cache?
-Each time a CDN POP needs to fill its cache, it makes a request to the origin for the object being cached. As a result, the origin incurs a billable transaction on every cache miss. The number of cache misses depends on a number of factors:
+Each time a CDN POP needs to fill its cache, it makes a request to the origin for the object being cached. As a result, the origin incurs a billable transaction on every cache miss. The number of cache misses depends on many factors:
 
-- How cacheable the content is: If the content has high TTL (time-to-live)/expiration values and is accessed frequently so it stays popular in cache, then the vast majority of the load is handled by the CDN. A typical good cache-hit ratio is well over 90%, meaning that less than 10% of client requests have to return to origin, either for a cache miss or object refresh.
+- How cacheable the content is: If the content has high TTL (time-to-live)/expiration values and is accessed frequently so it stays popular in cache, then most of the load gets handled by the CDN. A typical good cache-hit ratio is well over 90%, meaning that less than 10% of client requests have to return to origin, either for a cache miss or object refresh.
 
 - How many nodes need to load the object: Each time a node loads an object from the origin, it incurs a billable transaction. As a result, more global content (accessed from more nodes) results in more billable transactions.
 
 - TTL influence: A higher TTL for an object means it needs to be fetched from the origin less frequently. It also means clients, such as browsers, can cache the object longer, which can reduce the transactions to the CDN.
 
 ## Which origin services are eligible for free data transfer with Azure CDN from Microsoft? 
-If you use one of the following Azure services as your CDN origin, you will not be charged from Data transfer from the Origin to the CDN PoPs. 
+If you use one of the following Azure services as your CDN origin, you don't get charged from Data transfer from the Origin to the CDN PoPs. 
 
 - Azure Storage
 - Azure Media Services

articles/cdn/cdn-optimization-overview.md

@@ -2,11 +2,10 @@
 title: Optimize Azure CDN for the type of content delivery
 description: Learn how Azure Content Delivery Network can optimize delivery based on type of content. Optimization best practices improve performance and origin offload.
 services: cdn
-documentationcenter: ''
 author: duongau
 ms.service: azure-cdn
 ms.topic: how-to
-ms.date: 03/25/2019
+ms.date: 02/27/2023
 ms.author: duau
 ---
 # Optimize Azure CDN for the type of content delivery
@@ -107,13 +106,13 @@ For more information about media streaming optimization, see [Media streaming op
 
 For **Azure CDN Standard from Akamai** profiles, large file downloads are optimized for content larger than 10 MB. If your average file size is smaller than 10 MB, use general web delivery. If your average files sizes are consistently larger than 10 MB, it might be more efficient to create a separate endpoint for large files. For example, firmware or software updates typically are large files. To deliver files larger than 1.8 GB, the large file download optimization is required.
 
-For **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Verizon**, and **Azure CDN Premium from Verizon** profiles, use the general web delivery optimization type to deliver large file download content. There is no limitation on file download size.
+For **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Verizon**, and **Azure CDN Premium from Verizon** profiles, use the general web delivery optimization type to deliver large file download content. There's no limitation on file download size.
 
 For more information about large file optimization, see [Large file optimization](cdn-large-file-optimization.md).
 
 ### Dynamic site acceleration
 
- Dynamic site acceleration (DSA) is available for **Azure CDN Standard from Akamai**, **Azure CDN Standard from Verizon**, and **Azure CDN Premium from Verizon** profiles. This optimization involves an additional fee to use; for more information, see [Content Delivery Network pricing](https://azure.microsoft.com/pricing/details/cdn/).
+ Dynamic site acceleration (DSA) is available for **Azure CDN Standard from Akamai**, **Azure CDN Standard from Verizon**, and **Azure CDN Premium from Verizon** profiles. This optimization involves an extra fee to use; for more information, see [Content Delivery Network pricing](https://azure.microsoft.com/pricing/details/cdn/).
 
 > [!NOTE]
 > Dynamic site acceleration from Microsoft is offered via [Azure Front Door Service](../frontdoor/front-door-overview.md) which is a global [anycast](https://en.wikipedia.org/wiki/Anycast) service leveraging Microsoft's private global network to deliver your app workloads.

articles/cdn/cdn-standard-rules-engine-reference.md

@@ -3,10 +3,9 @@ title: Standard rules engine reference for Azure CDN | Microsoft Docs
 description: Reference documentation for match conditions and actions in the Standard rules engine for Azure Content Delivery Network (Azure CDN).
 services: cdn
 author: duongau
-
 ms.service: azure-cdn
 ms.topic: article
-ms.date: 07/31/2021
+ms.date: 02/23/2023
 ms.author: duau
 
 ---
@@ -15,7 +14,7 @@ ms.author: duau
 
 In the [Standard rules engine](cdn-standard-rules-engine.md) for Azure Content Delivery Network (Azure CDN), a rule consists of one or more match conditions and an action. This article provides detailed descriptions of the match conditions and features that are available in the Standard rules engine for Azure CDN.
 
-The rules engine is designed to be the final authority on how specific types of requests are processed by Standard Azure CDN.
+The rules engine is designed to be the final authority on how specific types of requests get processed by Standard Azure CDN.
 
 **Common uses for the rules**:
 
@@ -29,7 +28,7 @@ To define a rule in the rules engine, set [match conditions](cdn-standard-rules-
 
  ![Azure CDN rules structure](./media/cdn-standard-rules-engine-reference/cdn-rules-structure.png)
 
-Each rule can have up to ten match conditions and five actions. Each Azure CDN endpoint can have up to 25 rules. 
+Each rule can have up to 10 match conditions and 5 actions. Each Azure CDN endpoint can have up to 25 rules. 
 
 Included in this limit is a default *global rule*. The global rule doesn't have match conditions; actions that are defined in a global rule always triggered.