Merge pull request #293586 from duongau/retireedgio3

Azure CDN from Edgio - Retire/remove content (Batch 4)

Author: Court72

articles/cdn/cdn-storage-custom-domain-https.md

@@ -41,16 +41,12 @@ If you create multiple SAS URLs for the same blob endpoint, consider enabling qu
 
 ## HTTP-to-HTTPS redirection
 
-You can elect to redirect HTTP traffic to HTTPS by creating a URL redirect rule with the [Standard rules engine](cdn-standard-rules-engine.md) or the [Edgio Premium rules engine](cdn-verizon-premium-rules-engine.md). Standard Rules engine is available only for Azure Content Delivery Network from Microsoft profiles, while Edgio premium rules engine is available only from Azure Content Delivery Network Premium from Edgio profiles.
+You can redirect HTTP traffic to HTTPS by creating a URL redirect rule with the [Standard rules engine](cdn-standard-rules-engine.md).
 
 ![Microsoft redirect rule](./media/cdn-storage-custom-domain-https/cdn-standard-redirect-rule.png)
 
 In the above rule, leaving Hostname, Path, Query string, and Fragment results in the incoming values being used in the redirect.
 
-![Edgio redirect rule](./media/cdn-storage-custom-domain-https/cdn-url-redirect-rule.png)
-
-In the above rule, *Cdn-endpoint-name* refers to the name that you configured for your content delivery network endpoint. The value for *origin-path* refers to the path within your origin storage account where your static content resides. If you're hosting all static content in a single container, replace *origin-path* with the name of that container.
-
 ## Pricing and billing
 
 When you access blobs through Azure Content Delivery Network, you pay [Blob storage prices](https://azure.microsoft.com/pricing/details/storage/blobs/) for traffic between the POP servers and the origin (Blob storage), and [Azure content delivery network pricing](https://azure.microsoft.com/pricing/details/cdn/) for data accessed from the POP servers.

articles/cdn/cdn-traffic-manager.md

@@ -34,24 +34,15 @@ If the profile is unavailable, requests are directed to the secondary profile. R
 
 Using Azure Traffic Manager in this way ensures your web application is always available.
 
-This article provides guidance and an example of how to configure failover with profiles from:
-
-- **Azure CDN Standard from Edgio**
-- **Azure CDN from Microsoft**
+This article provides guidance and an example of how to configure failover with Azure CDN profiles.
 
 <a name='create-azure-cdn-profiles'></a>
 
 ## Create Azure Content Delivery Network profiles
 
 Create two or more Azure Content Delivery Network profiles and endpoints with different providers.
 
-1. Create two content delivery network profiles:
-    - **Azure CDN Standard from Edgio**
-    - **Azure CDN from Microsoft**
-
-    Create the profiles by following the steps in [Create a new content delivery network profile](cdn-create-new-endpoint.md#create-a-new-cdn-profile).
-
-   ![Screenshot of the content delivery network multiple profiles.](./media/cdn-traffic-manager/cdn-multiple-profiles.png)
+1. Create two Azure CDN profiles. Create the profiles by following the steps in [Create a new content delivery network profile](cdn-create-new-endpoint.md#create-a-new-cdn-profile).
 
 2. In each of the new profiles, create at least one endpoint by following the steps in [Create a new content delivery network endpoint](cdn-create-new-endpoint.md#create-a-new-cdn-endpoint).
 
@@ -68,9 +59,7 @@ Create an Azure Traffic Manager profile and configure load balancing across your
     - **Type**, select **External endpoints**.
     - **Priority**, enter a number.
 
-    For example, create **cdndemo101microsoft.azureedge.net** with a priority of **1** and **cdndemo101verizon.azureedge.net** with a priority of **2**.
-
-   ![Screenshot of the content delivery network Traffic Manager endpoints.](./media/cdn-traffic-manager/cdn-traffic-manager-endpoints.png)
+    For example, create **cdndemo101microsoft.azureedge.net** with a priority of **1** and **cdndemo101microsoft2.azureedge.net** with a priority of **2**.
 
 <a name='configure-custom-domain-on-azure-cdn-and-azure-traffic-manager'></a>
 
@@ -112,9 +101,9 @@ After you configure your content delivery network and Traffic Manager profiles,
 
     For example:
 
-    `cdnverify.cdndemo101.dustydogpetcare.online  CNAME  cdnverify.cdndemo101verizon.azureedge.net`
+    `cdnverify.cdndemo101.dustydogpetcare.online  CNAME  cdnverify.cdndemo101microsoft2.azureedge.net`
 
-4. From your Azure Content Delivery Network profile, select the second content delivery network endpoint (Edgio) and repeat step 2. Select **Add custom domain**, and enter **cdndemo101.dustydogpetcare.online**.
+4. From your Azure Content Delivery Network profile, select the second content delivery network endpoint and repeat step 2. Select **Add custom domain**, and enter **cdndemo101.dustydogpetcare.online**.
 
 After you complete these steps, your multi-content delivery network service with failover capabilities is configured with Azure Traffic Manager.
 

articles/cdn/cdn-troubleshoot-compression.md

@@ -53,11 +53,7 @@ First, we should do a quick sanity check on the request. You can use your browse
 
 ![CDN request headers](./media/cdn-troubleshoot-compression/cdn-request-headers.png)
 
-### Verify compression settings (standard CDN profiles)
-
-> [!NOTE]
-> This step applies only if your CDN profile is an **Azure CDN Standard from Microsoft** or **Azure CDN Standard from Edgio** profile.
->
+### Verify compression settings
 
 Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and select the **Configure** button.
 
@@ -66,50 +62,6 @@ Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and se
 
 ![CDN compression settings](./media/cdn-troubleshoot-compression/cdn-compression-settings.png)
 
-### Verify compression settings (Premium CDN profiles)
-
-> [!NOTE]
-> This step applies only if your CDN profile is an **Azure CDN Premium from Edgio** profile.
->
-
-Navigate to your endpoint in the [Azure portal](https://portal.azure.com) and select the **Manage** button. The supplemental portal opens. Hover over the **HTTP Large** tab, then hover over the **Cache Settings** flyout. Select **Compression**.
-
-- Verify compression is enabled.
-- Verify the **File Types** list contains a comma-separated list (no spaces) of MIME types.
-- Verify the MIME type for the content to be compressed is included in the list of compressed formats.
-
-![CDN premium compression settings](./media/cdn-troubleshoot-compression/cdn-compression-settings-premium.png)
-
-<a name='verify-the-content-is-cached-verizon-cdn-profiles'></a>
-
-### Verify the content is cached (Edgio CDN profiles)
-
-> [!NOTE]
-> This step applies only if your CDN profile is an **Azure CDN Standard from Edgio** or **Azure CDN Premium from Edgio** profile.
->
->
-
-Using your browser's developer tools, check the response headers to ensure the file is cached in the region where it's being requested.
-
-- Check the **Server** response header. The header should have the format **Platform (POP/Server ID)**, as seen in the following example.
-- Check the **X-Cache** response header. The header should read **HIT**.
-
-![CDN response headers](./media/cdn-troubleshoot-compression/cdn-response-headers.png)
-
-<a name='verify-the-file-meets-the-size-requirements-verizon-cdn-profiles'></a>
-
-### Verify the file meets the size requirements (Edgio CDN profiles)
-
-> [!NOTE]
-> This step applies only if your CDN profile is an **Azure CDN Standard from Edgio** or **Azure CDN Premium from Edgio** profile.
->
->
-
-To be eligible for compression, a file must meet the following size requirements:
-
-- Larger than 128 bytes (Content-Length: 128)
-- Smaller than 3 MB
-
 ### Check the request at the origin server for a **Via** header
 
 The **Via** HTTP header indicates to the web server that the request is being passed by a proxy server. Microsoft IIS web servers by default don't compress responses when the request contains a **Via** header. To override this behavior, perform the following:

articles/cdn/cdn-troubleshoot-endpoint.md

@@ -34,9 +34,7 @@ There are several possible causes, including:
 ## Troubleshooting steps
 
 > [!IMPORTANT]
-> After creating a content delivery network endpoint, it will not immediately be available for use, as it takes time for the registration to propagate through the content delivery network:
-> - For **Azure CDN Standard from Microsoft** profiles, propagation usually completes in ten minutes.
-> - For **Azure CDN Standard from Edgio** and **Azure CDN Premium from Edgio** profiles, propagation usually completes within 90 minutes.
+> After creating an endpoint, it won't immediately be available for use, as it can take up to ten minutes for the registration to propagate through the content delivery network.
 >
 > If you complete the steps in this document and you're still getting 404 responses, consider waiting a few hours to check again before opening a support ticket.
 

articles/cdn/media/cdn-storage-custom-domain-https/cdn-url-redirect-rule.png

@@ -15,7 +15,6 @@ ms.custom: references_regions
 > [!div class="op_single_selector"]
 > - [POP locations by region](cdn-pop-locations.md)
 > - [Microsoft POP locations by abbreviation](microsoft-pop-abbreviations.md)
-> - [Edgio POP locations by abbreviation](cdn-pop-abbreviations.md)
 
 This article lists Microsoft POP locations, sorted by POP abbreviation, for **Azure CDN**.
 

articles/cdn/media/cdn-traffic-manager/cdn-multiple-profiles.png

@@ -81,9 +81,7 @@ After you've registered your custom domain, you can then add it to your CDN endp
 
    Azure verifies that the CNAME record exists for the custom domain name you entered. If the CNAME is correct, your custom domain is validated.
 
-   It can take some time for the new custom domain settings to propagate to all CDN 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 ten minutes for the new custom domain settings to propagate to all CDN edge nodes.
 
 ## Enable HTTPS on your custom domain
 

articles/cdn/media/cdn-traffic-manager/cdn-traffic-manager-endpoints.png

@@ -22,13 +22,13 @@ Azure CDN from Microsoft is the only CDN offering that is available to trial sub
 
 ## Pay-as-you-go
 
-Bandwidth for Azure CDN from Microsoft and Edgio gets throttled until the subscription is determined to be in good standing and has a sufficient payment history. The process for determining the subscription status and having throttling removed happens automatically after the first payment has been received.
+Bandwidth for Azure CDN from Microsoft gets throttled until the subscription is determined to be in good standing and has a sufficient payment history. The process for determining the subscription status and having throttling removed happens automatically after the first payment has been received.
 
 If you have made a payment and throttling hasn't been removed, you can request to do so by [contacting support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 
 ## Enterprise agreements
 
-All Azure CDNs are available to Enterprise Agreement subscriptions. Enterprise Agreements subscriptions don't have any bandwidth restrictions.
+Azure CDN is available to Enterprise Agreement subscriptions. Enterprise Agreements subscriptions don't have any bandwidth restrictions.
 
 ## Other offer types