Merge pull request #249819 from MicrosoftDocs/release-rebrand-cdn-edgio

Release rebrand cdn edgio -- scheduled release at 4AM of 8/31

Author: huypub

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

@@ -49,7 +49,7 @@ Open a browser and sign in 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. For **Azure CDN from Verizon** profiles, you can't 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 Edgio** profiles, you can't change the optimization of a CDN endpoint after it has been created.
 
 ## Create a CDN profile and endpoint
 
@@ -82,7 +82,7 @@ Azure creates the profile and endpoint. The new endpoint appears in the **Endpoi
  Because it takes time for the registration to propagate, the endpoint isn't immediately available for use: 
    - For **Azure CDN Standard from Microsoft** profiles, propagation usually completes in 10 minutes. 
    - For **Azure CDN Standard from Akamai** profiles, propagation usually completes within one minute. 
-   - For **Azure CDN Standard from Verizon** and **Azure CDN Premium from Verizon** profiles, propagation usually completes within 90 minutes. 
+   - For **Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** profiles, propagation usually completes within 90 minutes. 
 
 The sample app has an *index.html* file and *css*, *img*, and *js* folders that contain other static assets. The content paths for all of these files are the same at the CDN endpoint. For example, both of the following URLs access the *bootstrap.css* file in the *css* folder:
 

articles/cdn/cdn-analyze-usage-patterns.md

@@ -1,6 +1,6 @@
 ---
-title: Core Reports from Verizon | Microsoft Docs
-description: 'Learn how to access and view Verizon Core Reports via the Manage portal for Verizon profiles.'
+title: Core Reports from Edgio | Microsoft Docs
+description: 'Learn how to access and view Edgio Core Reports via the Manage portal for Edgio profiles.'
 services: cdn
 documentationcenter: ''
 author: zhangmanling
@@ -16,11 +16,11 @@ ms.date: 01/23/2017
 ms.author: mazha
 
 ---
-# Core Reports from Verizon
+# Core Reports from Edgio
 
 [!INCLUDE [cdn-verizon-only](../../includes/cdn-verizon-only.md)]
 
-By using Verizon Core Reports via the Manage portal for Verizon profiles, you can view usage patterns for your CDN with the following reports:
+By using Edgio Core Reports via the Manage portal for Edgio profiles, you can view usage patterns for your CDN with the following reports:
 
 * Bandwidth
 * Data Transferred
@@ -29,7 +29,9 @@ By using Verizon Core Reports via the Manage portal for Verizon profiles, you ca
 * Cache Hit Ratio
 * IPV4/IPV6 Data Transferred
 
-## Accessing Verizon Core Reports
+<a name='accessing-verizon-core-reports'></a>
+
+## Accessing Edgio Core Reports
 1. From the CDN profile blade, click the **Manage** button.
 
     ![CDN profile Manage button](./media/cdn-reports/cdn-manage-btn.png)
@@ -129,4 +131,3 @@ This report shows the traffic usage distribution in IPV4 vs IPV6.
 
 ## Considerations
 Reports can only be generated within the last 18 months.
-

articles/cdn/cdn-app-dev-net.md

@@ -288,7 +288,7 @@ private static void PromptPurgeCdnEndpoint(CdnManagementClient cdn)
 ```
 
 > [!NOTE]
-> In the example previously, the string `/*` denotes that I want to purge everything in the root of the endpoint path.  This is equivalent to checking **Purge All** in the Azure portal's "purge" dialog. In the `CreateCdnProfile` method, I created our profile as an **Azure CDN from Verizon** profile using the code `Sku = new Sku(SkuName.StandardVerizon)`, so this will be successful.  However, **Azure CDN from Akamai** profiles do not support **Purge All**, so if I was using an Akamai profile for this tutorial, I would need to include specific paths to purge.
+> In the example previously, the string `/*` denotes that I want to purge everything in the root of the endpoint path.  This is equivalent to checking **Purge All** in the Azure portal's "purge" dialog. In the `CreateCdnProfile` method, I created our profile as an **Azure CDN from Edgio** profile using the code `Sku = new Sku(SkuName.StandardVerizon)`, so this will be successful.  However, **Azure CDN from Akamai** profiles do not support **Purge All**, so if I was using an Akamai profile for this tutorial, I would need to include specific paths to purge.
 >
 >
 

articles/cdn/cdn-azure-diagnostic-logs.md

@@ -222,9 +222,9 @@ Here's how you can use the tool:
 
 ## Log data delays
 
-The following table shows log data delays for **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Akamai**, and **Azure CDN Standard/Premium from Verizon**.
+The following table shows log data delays for **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Akamai**, and **Azure CDN Standard/Premium from Edgio**.
 
-Microsoft log data delays | Verizon log data delays | Akamai log data delays
+Microsoft log data delays | Edgio log data delays | Akamai log data delays
 --- | --- | ---
 Delayed by 1 hour. | Delayed by 1 hour and can take up to 2 hours to start appearing after endpoint propagation completion. | Delayed by 24 hours; if it was created more than 24 hours ago, it takes up to 2 hours to start appearing. If it was recently created, it can take up to 25 hours for the logs to start appearing.
 
@@ -237,12 +237,12 @@ The following table shows a list of metrics available in the core analytics logs
 
 * **Azure CDN Standard from Microsoft**
 * **Azure CDN Standard from Akamai**
-* **Azure CDN Standard/Premium from Verizon**
+* **Azure CDN Standard/Premium from Edgio**
 
 Not all metrics are available from all providers, although such differences are minimal. The table also displays whether a given metric is available from a provider. The metrics are available for only those CDN endpoints that have traffic on them.
 
 
-|Metric                     | Description | Microsoft | Verizon | Akamai |
+|Metric                     | Description | Microsoft | Edgio | Akamai |
 |---------------------------|-------------|-----------|---------|--------|
 | RequestCountTotal         | Total number of request hits during this period. | Yes | Yes |Yes |
 | RequestCountHttpStatus2xx | Count of all requests that resulted in a 2xx HTTP code (for example, 200, 202). | Yes | Yes |Yes |

articles/cdn/cdn-billing.md

@@ -54,7 +54,7 @@ If you're using Azure Blob storage as the origin for your content, you also incu
 - 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 as followed.
+> 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 Edgio 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).
 

articles/cdn/cdn-caching-rules-tutorial.md

@@ -21,7 +21,7 @@ ms.custom: mvc
 # Tutorial: Set Azure CDN caching rules
 
 > [!NOTE] 
-> Caching rules are available only for **Azure CDN Standard from Verizon** and **Azure CDN Standard from Akamai** profiles. For **Azure CDN from Microsoft** profiles, you must use the [Standard rules engine](cdn-standard-rules-engine-reference.md) For **Azure CDN Premium from Verizon** profiles, you must use the [Verizon Premium rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
+> Caching rules are available only for **Azure CDN Standard from Edgio** and **Azure CDN Standard from Akamai** profiles. For **Azure CDN from Microsoft** profiles, you must use the [Standard rules engine](cdn-standard-rules-engine-reference.md) For **Azure CDN Premium from Edgio** profiles, you must use the [Edgio Premium rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
  
 
 This tutorial describes how you can use Azure Content Delivery Network (CDN) caching rules to set or modify default cache expiration behavior both globally and with custom conditions, such as a URL path and file extension. Azure CDN provides two types of caching rules:
@@ -110,4 +110,4 @@ In this tutorial, you learned how to:
 Advance to the next article to learn how to configure additional caching rule settings.
 
 > [!div class="nextstepaction"]
-> [Control Azure CDN caching behavior with caching rules](cdn-caching-rules.md)
+> [Control Azure CDN caching behavior with caching rules](cdn-caching-rules.md)

articles/cdn/cdn-caching-rules.md

@@ -15,7 +15,7 @@ ms.author: duau
 This article describes how you can use content delivery network (CDN) caching rules to set or modify default cache expiration behavior. These caching rules can either be global or with custom conditions, such as a URL path and file extension.
 
 > [!NOTE] 
-> Caching rules are available only for **Azure CDN Standard from Verizon** and **Azure CDN Standard from Akamai** profiles. For **Azure CDN from Microsoft** profiles, you must use the [Standard rules engine](cdn-standard-rules-engine-reference.md) For **Azure CDN Premium from Verizon** profiles, you must use the [Verizon Premium rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
+> Caching rules are available only for **Azure CDN Standard from Edgio** and **Azure CDN Standard from Akamai** profiles. For **Azure CDN from Microsoft** profiles, you must use the [Standard rules engine](cdn-standard-rules-engine-reference.md) For **Azure CDN Premium from Edgio** profiles, you must use the [Edgio Premium rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
  
 Azure Content Delivery Network (CDN) offers two ways to control how your files get cached:
 
@@ -106,7 +106,7 @@ When you set these rules, a request for _<endpoint hostname>_.azureedge.ne
 >
 > Azure CDN configuration changes can take some time to propagate through the network: 
 > - For **Azure CDN Standard from Akamai** profiles, propagation usually completes within one minute. 
-> - For **Azure CDN Standard from Verizon** profiles, propagation usually completes in 10 minutes.  
+> - For **Azure CDN Standard from Edgio** profiles, propagation usually completes in 10 minutes.  
 >
 
 ## See also

articles/cdn/cdn-change-provider.md

@@ -21,7 +21,7 @@ The purpose of this article is to share best practices when migrating from one C
 
 **Azure Front Door:** release two new tiers (Standard and Premium) on March 29, 2022, which is the next generation Front Door service. It combines the capabilities of Azure Front Door (classic), Microsoft CDN (classic), and Web Application Firewall. With features such as private link integration, enhancements to rules engine, diagnostics, and a one-stop secure application acceleration for Azure customers. For more information about Azure Front Door, see [Front Door overview](../frontdoor/front-door-overview.md).
 
-**Azure CDN Standard/Premium from Verizon:** is an alternative to Azure Front Door for your general CDN and media solutions. Azure CDN from Verizon is optimized for large media streaming workloads. It has unique CDN features such as cache warmup, log delivery services, and reporting features.  
+**Azure CDN Standard/Premium from Edgio:** is an alternative to Azure Front Door for your general CDN and media solutions. Azure CDN from Edgio is optimized for large media streaming workloads. It has unique CDN features such as cache warmup, log delivery services, and reporting features.  
 
 **Azure CDN Standard from Akamai (Retiring October 31, 2023)**: In May of 2016, Azure partnered with Akamai Technologies Inc to offer Azure CDN Standard from Akamai. Recently, Azure and Akamai Technologies Inc have decided not to renew this partnership. As a result, starting October 31, 2023, Azure CDN Standard from Akamai will no longer be supported.
 
@@ -55,7 +55,7 @@ Create a small-scale proof of concept testing environment with your potential re
 * Define success criteria:
     * Cost - does the new CDN profile meet your cost requirements?
     * Performance - does the new CDN profile meet the performance requirements of your workload?
-* Create a new profile - for example, Azure CDN with Verizon.
+* Create a new profile - for example, Azure CDN with Edgio.
 * Configure your new profile with similar configuration settings as your existing profile.
 * Fine tune caching and compression configuration settings to meet your requirements.
 
@@ -92,4 +92,4 @@ For more information, see [Failover CDN endpoints with Traffic Manager](cdn-traf
 ## Next Steps
 
 * Create an [Azure Front Door](../frontdoor/create-front-door-portal.md) profile.
-* Create an [Azure CDN from Verizon](cdn-create-endpoint-how-to.md) profile.
+* Create an [Azure CDN from Edgio](cdn-create-endpoint-how-to.md) profile.

articles/cdn/cdn-china-delivery.md

@@ -31,7 +31,7 @@ Azure CDN global and Azure CDN China have the following features:
 
      - Performs content delivery outside of China
 
-     - Four pricing tiers: Microsoft standard, Verizon standard, Verizon premium, and Akamai standard
+     - Four pricing tiers: Microsoft standard, Edgio standard, Edgio premium, and Akamai standard
 
      - [Documentation](./index.yml)
 
@@ -56,4 +56,4 @@ To learn more about Azure CDN China, see:
 
 - [Use the Azure Content Delivery Network](https://docs.azure.cn/en-us/cdn/cdn-how-to-use)
 
-- [Azure service availability in China](/azure/china/concepts-service-availability)
+- [Azure service availability in China](/azure/china/concepts-service-availability)

articles/cdn/cdn-cors.md

@@ -70,9 +70,11 @@ On Azure CDN Standard from Microsoft, you can create a rule in the [Standard rul
 
 On **Azure CDN Standard from Akamai**, the only mechanism to allow for multiple origins without the use of the wildcard origin is to use [query string caching](cdn-query-string.md). Enable the query string setting for the CDN endpoint and then use a unique query string for requests from each allowed domain. Doing so results in the CDN caching a separate object for each unique query string. This approach isn't ideal, however, as it results in multiple copies of the same file cached on the CDN.  
 
-### Azure CDN Premium from Verizon
+<a name='azure-cdn-premium-from-verizon'></a>
 
-Using the Verizon Premium rules engine, you need to [create a rule](./cdn-verizon-premium-rules-engine.md) to check the **Origin** header on the request.  If it's a valid origin, your rule sets the **Access-Control-Allow-Origin** header with the origin provided in the request. If the origin specified in the **Origin** header isn't allowed, your rule should omit the **Access-Control-Allow-Origin** header, which causes the browser to reject the request. 
+### Azure CDN Premium from Edgio
+
+Using the Edgio Premium rules engine, you need to [create a rule](./cdn-verizon-premium-rules-engine.md) to check the **Origin** header on the request.  If it's a valid origin, your rule sets the **Access-Control-Allow-Origin** header with the origin provided in the request. If the origin specified in the **Origin** header isn't allowed, your rule should omit the **Access-Control-Allow-Origin** header, which causes the browser to reject the request. 
 
 There are two ways to resolve this problem with the Premium rules engine. In both cases, the **Access-Control-Allow-Origin** header from the file's origin server is ignored and the CDN's rules engine completely manages the allowed CORS origins.
 
@@ -85,7 +87,7 @@ https?:\/\/(www\.contoso\.com|contoso\.com|www\.microsoft\.com|microsoft.com\.co
 ```
 
 > [!TIP]
-> **Azure CDN Premium from Verizon** uses [Perl Compatible Regular Expressions](https://pcre.org/) as its engine for regular expressions.  You can use a tool like [Regular Expressions 101](https://regex101.com/) to validate your regular expression.  Note that the "/" character is valid in regular expressions and doesn't need to be escaped, however, escaping that character is considered a best practice and is expected by some regex validators.
+> **Azure CDN Premium from Edgio** uses [Perl Compatible Regular Expressions](https://pcre.org/) as its engine for regular expressions.  You can use a tool like [Regular Expressions 101](https://regex101.com/) to validate your regular expression.  Note that the "/" character is valid in regular expressions and doesn't need to be escaped, however, escaping that character is considered a best practice and is expected by some regex validators.
 > 
 > 
 
@@ -101,4 +103,4 @@ Rather than regular expressions, you can instead create a separate rule for each
 > [!TIP]
 > In the example, the use of the wildcard character * tells the rules engine to match both HTTP and HTTPS.
 > 
->
+>