remove Edgio

Author: duongau

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

@@ -226,6 +226,7 @@ Here's how you can use the tool:
 
 ## Log data delays
 
+Microsoft log data is delayed by up to 1 hour. This delay is due to the time it takes to process and store the data.
 
 <a name='diagnostic-log-types-for-cdn-core-analytics'></a>
 

articles/cdn/cdn-large-file-optimization.md

@@ -46,30 +46,6 @@ There are no limits on maximum file size.
 
 Microsoft content delivery network supports transfer encoding responses, but only up to a maximum content size limit of 8 MB. In the case of chunked transfer encoded responses exceeding 8 MB, the Microsoft content delivery network will only cache and serve the initial 8 MB of content.
 
-<a name='optimize-for-delivery-of-large-files-with-azure-cdn-from-verizon'></a>
-
-<a name='optimize-for-delivery-of-large-files-with-azure-cdn-from-edgio'></a>
-
-## Optimize for delivery of large files with Azure Content Delivery Network from Edgio
-
-**Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** endpoints deliver large files without a cap on file size. More features are turned on by default to make delivery of large files faster.
-
-### Complete cache fill
-
-The defaults complete cache fill feature enables the content delivery network to pull a file into the cache when an initial request is abandoned or lost.
-
-Complete cache fill is most useful for large assets. Typically, users don't download them from start to finish. They use progressive download. The default behavior forces the edge server to initiate a background fetch of the asset from the origin server. Afterward, the asset is in the edge server's local cache. After the full object is in the cache, the edge server fulfills byte-range requests to the content delivery network for the cached object.
-
-The default behavior can be disabled through the rules engine in **Azure CDN Premium from Edgio**.
-
-### Peer cache fill hot-filing
-
-The default peer cache fills hot-filing feature uses a sophisticated proprietary algorithm. It uses extra edge caching servers based on bandwidth and aggregate requests metrics to fulfill client requests for large, highly popular objects. This feature prevents a situation in which large numbers of extra requests are sent to a user's origin server.
-
-### Conditions for large file optimization
-
-Large file optimization features for **Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** are turned on by default when you use the general web delivery optimization type. There are no limits on maximum file size.
-
 ## Other considerations
 
 Consider the following aspects for this optimization type:

articles/cdn/cdn-log-analysis.md

@@ -32,29 +32,6 @@ For more information, see [Azure CDN HTTP raw logs](monitoring-and-access-log.md
 
 Core analytics is available for content delivery network endpoints for all pricing tiers. Azure Diagnostics logs allow core analytics to be exported to Azure Storage, Event Hubs, or Azure Monitor logs. Azure Monitor logs offers a solution with graphs that are user-configurable and customizable. For more information about Azure diagnostic logs, see [Azure diagnostic logs](cdn-azure-diagnostic-logs.md).
 
-<a name='verizon-core-reports'></a>
-
-## Edgio core reports
-
-**Azure CDN Standard from Edgio** or **Azure CDN Premium from Edgio** profiles provide core reports. You can view core reports in the Edgio supplemental portal. Edgio core reports are accessible via the **Manage** option from the Azure portal and offers different kinds of graphs and views. For more information, see [Core Reports from Edgio](cdn-analyze-usage-patterns.md).
-
-<a name='verizon-custom-reports'></a>
-
-## Edgio custom reports
-
-**Azure CDN Standard from Edgio** or **Azure CDN Premium from Edgio** profiles provide custom reports. You can view custom reports in the Edgio supplemental portal. Edgio custom reports are accessible via the **Manage** option from the Azure portal.
-
-The custom reports display the number of hits or data transferred for each edge CNAME. Data gets grouped by HTTP response code or cache status over period of time. For more information, see [Custom Reports from Edgio](cdn-verizon-custom-reports.md).
-
-<a name='azure-cdn-premium-from-verizon-reports'></a>
-
-## Azure CDN Premium from Edgio reports
-
-With **Azure CDN Premium from Edgio**, you can also access the following reports:
-   - [Advanced HTTP reports](cdn-advanced-http-reports.md)
-   - [Real-time stats](cdn-real-time-stats.md)
-   - [Azure CDN edge node performance](cdn-edge-performance.md)
-
 ## Next steps
 
 In this article, you learned about the different options for analysis reports for Azure CDN.

articles/cdn/cdn-manage-expiration-of-blob-content.md

@@ -39,9 +39,6 @@ You can also control cache settings from the Azure portal by setting content del
 
 The preferred method for setting a blob's `Cache-Control` header is to use caching rules in the Azure portal. For more information about content delivery network caching rules, see [Control Azure Content Delivery Network caching behavior with caching rules](cdn-caching-rules.md).
 
-> [!NOTE]
-> Caching rules are available only for **Azure CDN Standard from Edgio** profiles. For **Azure CDN Premium from Edgio** profiles, you must use the [Azure Content Delivery Network rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
-
 **To navigate to the CDN caching rules page**:
 
 1. In the Azure portal, select a content delivery network profile, then select the endpoint for the blob.

articles/cdn/cdn-manage-expiration-of-cloud-service-content.md

@@ -37,8 +37,6 @@ You can also control cache settings from the Azure portal by setting [content de
 
 The preferred method for setting a web server's `Cache-Control` header is to use caching rules in the Azure portal. For more information about content delivery network caching rules, see [Control Azure Content Delivery Network caching behavior with caching rules](cdn-caching-rules.md).
 
-> [!NOTE]
-> Caching rules are available only for **Azure CDN Standard from Edgio** profiles. For **Azure CDN Premium from Edgio** profiles, you must use the [Azure Content Delivery Network rules engine](./cdn-verizon-premium-rules-engine.md) in the **Manage** portal for similar functionality.
 
 **To navigate to the CDN caching rules page**:
 

articles/cdn/cdn-manage-powershell.md

@@ -195,19 +195,6 @@ Update-AzCdnEndpoint -Name cdnposhdoc -ProfileName CdnPoshDemo -ResourceGroupNam
 Clear-AzCdnEndpointContent -ProfileName CdnPoshDemo -ResourceGroupName CdnDemoRG -EndpointName cdnposhdoc -ContentFilePath @("/images/kitten.png","/video/rickroll.mp4")
 ```
 
-## Pre-load some assets
-
-> [!NOTE]
-> Pre-loading is only available on Azure Content Delivery Network from Edgio profiles.
-
-`Import-AzCdnEndpointContent` pre-loads assets into the content delivery network cache.
-
-```powershell
-Import-AzCdnEndpointContent -ProfileName CdnPoshDemo -ResourceGroupName CdnDemoRG -EndpointName cdnposhdoc -ContentFilePath @("/images/kitten.png","/video/rickroll.mp4")`
-```
-
-<a name='startingstopping-cdn-endpoints'></a>
-
 ## Starting/Stopping content delivery network endpoints
 
 `Start-AzCdnEndpoint` and `Stop-AzCdnEndpoint` can be used to start and stop individual endpoints or groups of endpoints.

articles/cdn/cdn-map-content-to-custom-domain.md

@@ -188,17 +188,14 @@ After you've registered your custom domain, you can then add it to your content
 
    Azure verifies that the CNAME record exists for the custom domain name you entered. If the CNAME is correct, your custom domain gets validated.
 
-   It can take some time for the new custom domain settings to propagate to all content delivery network edge nodes:
-    - For **Azure CDN Standard from Microsoft** profiles, propagation usually completes in 10 minutes.
-    - For **Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** profiles, propagation usually completes in 10 minutes.
+   It can take up to 10 minutes for the new custom domain settings to propagate to all content delivery network edge nodes.
 
 # [**PowerShell**](#tab/azure-powershell)
 
 1. Sign in to Azure PowerShell:
 
 ```azurepowershell-interactive
     Connect-AzAccount
-
 ```
 
 2. Use [New-AzCdnCustomDomain](/powershell/module/az.cdn/new-azcdncustomdomain) to map the custom domain to your content delivery network endpoint.
@@ -222,10 +219,7 @@ After you've registered your custom domain, you can then add it to your content
 
 Azure verifies that the CNAME record exists for the custom domain name you entered. If the CNAME is correct, your custom domain gets validated.
 
-   It can take some time for the new custom domain settings to propagate to all content delivery network edge nodes:
-
-- For **Azure CDN Standard from Microsoft** profiles, propagation usually completes in 10 minutes.
-- For **Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** profiles, propagation usually completes in 10 minutes.
+   It can take up to 10 minutes for the new custom domain settings to propagate to all content delivery network edge nodes.
 
 ---
 

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

@@ -32,18 +32,3 @@ The general media delivery or video-on-demand media delivery optimization types
 
 Partial cache sharing allows the content delivery network to serve partially cached content to new requests. For example, if the first request to the content delivery network results in a cache miss, the request is sent to the origin. Although this incomplete content is loaded into the content delivery network cache, other requests to the content delivery network can start getting this data.
 
-<a name='media-streaming-optimizations-for-azure-cdn-from-verizon'></a>
-
-<a name='media-streaming-optimizations-for-azure-cdn-from-edgio'></a>
-
-## Media streaming optimizations for Azure Content Delivery Network from Edgio
-
-**Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** endpoints deliver streaming media assets directly by using the general web delivery optimization type. A few features on the content delivery network directly help delivering media assets by default.
-
-### Partial cache sharing
-
-Partial cache sharing allows the content delivery network to serve partially cached content to new requests. For example, if the first request to the content delivery network results in a cache miss, the request is sent to the origin. Although this incomplete content is loaded into the content delivery network cache, other requests to the content delivery network can start getting this data.
-
-### Cache fill wait time
-
-The cache fill wait time feature forces the edge server to hold any subsequent requests for the same resource until HTTP response headers arrive from the origin server. If HTTP response headers from the origin arrive before the timer expires, all requests that were put on hold are served out of the growing cache. At the same time, the cache is filled by data from the origin. By default, the cache fill wait time is set to 3,000 milliseconds.

articles/cdn/cdn-optimization-overview.md

@@ -31,12 +31,6 @@ This article provides an overview of various optimization features and when you
 > [!NOTE]
 > Dynamic site acceleration from Microsoft is offered via [Azure Front Door](../frontdoor/front-door-overview.md).
 
-**Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** profiles support the following optimizations:
-
-- [General web delivery](#general-web-delivery). This optimization is also used for media streaming and large file download.
-
-- [Dynamic site acceleration](#dynamic-site-acceleration)
-
 ## Optimization for specific scenarios
 
 You can optimize the content delivery network endpoint for one of these scenarios.
@@ -55,16 +49,12 @@ Media streaming is time-sensitive, because packets that arrive late on the clien
 
 This scenario is common for Azure media service customers. When you use Azure Media Services, you get a single streaming endpoint that can be used for both live and on-demand streaming. With this scenario, customers don't need to switch to another endpoint when they change from live to on-demand streaming. General media streaming optimization supports this type of scenario.
 
-For **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Edgio**, and **Azure CDN Premium from Edgio**, use the general web delivery optimization type to deliver general streaming media content.
-
 For more information about media streaming optimization, see [Media streaming optimization](cdn-media-streaming-optimization.md).
 
 ### Video-on-demand media streaming
 
 Video-on-demand media streaming optimization improves video-on-demand streaming content. If you use an endpoint for video-on-demand streaming, use this option.
 
-For **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Edgio**, and **Azure CDN Premium from Edgio** profiles, use the general web delivery optimization type to deliver video-on-demand streaming media content.
-
 For more information about media streaming optimization, see [Media streaming optimization](cdn-media-streaming-optimization.md).
 
 > [!NOTE]
@@ -73,16 +63,16 @@ For more information about media streaming optimization, see [Media streaming op
 
 ### Large file download
 
-For **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Edgio**, and **Azure CDN Premium from Edgio** profiles, use the general web delivery optimization type to deliver large file download content. There's no limitation on file download size.
+For **Azure CDN Standard from Microsoft** 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 Edgio**, and **Azure CDN Premium from Edgio** profiles. This optimization involves an extra fee to use; for more information, see [Content Delivery Network pricing](https://azure.microsoft.com/pricing/details/cdn/).
+Dynamic site acceleration (DSA) isn't available for **Azure CDN from Microsoft (classic)**.
 
 > [!NOTE]
-> Dynamic site acceleration from Microsoft is offered via [Azure Front Door](../frontdoor/front-door-overview.md) which is a global [anycast](https://en.wikipedia.org/wiki/Anycast) service using Microsoft's private global network to deliver your app workloads.
+> Dynamic site acceleration from Microsoft is offered through [Azure Front Door](../frontdoor/front-door-overview.md) which is a global [anycast](https://en.wikipedia.org/wiki/Anycast) service using Microsoft's private global network to deliver your app workloads.
 
 DSA includes various techniques that benefit the latency and performance of dynamic content. Techniques include route and network optimization, TCP optimization, and more.
 

articles/cdn/cdn-pop-list-api.md

@@ -14,16 +14,6 @@ ms.author: duau
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
-<a name='retrieve-the-current-verizon-pop-ip-list-for-azure-cdn'></a>
-
-<a name='retrieve-the-current-edgio-pop-ip-list-for-azure-cdn'></a>
-
-## Retrieve the current Edgio POP IP list for Azure Content Delivery Network
-
-You can use the REST API to retrieve the set of IPs for Edgio's point of presence (POP) servers. These POP servers make requests to origin servers that are associated with Azure Content Delivery Network endpoints on an Edgio profile (**Azure Content Delivery Network Standard from Edgio** or **Azure CDN Premium from Edgio**). This set of IPs is different from the IPs that a client would see when making requests to the POPs.
-
-For the syntax of the REST API operation for retrieving the POP list, see [Edge Nodes - List](/rest/api/cdn/edge-nodes/list).
-
 <a name='retrieve-the-current-microsoft-pop-ip-list-for-azure-cdn'></a>
 
 ## Retrieve the current Microsoft POP IP list for Azure Content Delivery Network
@@ -36,7 +26,7 @@ To configure Microsoft's backend IP ranges with Azure Content Delivery Network f
 
 ## Typical use case
 
-For security purposes, you can use this IP list to enforce that requests to your origin server are made only from a valid Edgio POP. For example, if someone discovered the hostname or IP address for a content delivery network endpoint's origin server, one could make requests directly to the origin server, therefore bypassing the scaling and security capabilities provided by Azure Content Delivery Network. By setting the IPs in the returned list as the only allowed IPs on an origin server, this scenario can be prevented. To ensure that you have the latest POP list, retrieve it at least once a day.
+For security purposes, you can use this IP list to enforce that requests to your origin server are made only from a valid Azure CDN POP. For example, if someone discovered the hostname or IP address for a content delivery network endpoint's origin server, one could make requests directly to the origin server, therefore bypassing the scaling and security capabilities provided by Azure Content Delivery Network. By setting the IPs in the returned list as the only allowed IPs on an origin server, this scenario can be prevented. To ensure that you have the latest POP list, retrieve it at least once a day.
 
 ## Next steps