Merge pull request #293579 from duongau/retireedgio1

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

Author: JamesJBarnett

articles/cdn/cdn-custom-ssl.md

@@ -69,10 +69,7 @@ To enable HTTPS on a custom domain, follow these steps:
 
 1. Go to the [Azure portal](https://portal.azure.com) to find a certificate managed by your Azure CDN. Search for and select **CDN profiles**.
 
-2. Choose your profile:
-    - **Azure CDN Standard from Microsoft**
-    - **Azure CDN Standard from Edgio**
-    - **Azure CDN Premium from Edgio**
+2. Choose **Azure CDN Standard from Microsoft (classic)**.
 
 3. In the list of CDN endpoints, select the endpoint containing your custom domain.
 
@@ -95,10 +92,6 @@ To enable HTTPS on a custom domain, follow these steps:
 
 # [Option 2: Enable HTTPS with your own certificate](#tab/option-2-enable-https-with-your-own-certificate)
 
-> [!IMPORTANT]
-> * This option is available only with **Azure CDN from Microsoft**.
-> * The option to use your own certificate with Azure CDN from Edgio has undergone maintenance on June 20, 2024. This feature will be unavailable during this time and will be available again in early 2025.
-
 You can use your own certificate to enable the HTTPS feature. This process is done through an integration with Azure Key Vault, which allows you to store your certificates securely. Azure CDN uses this secure mechanism to get your certificate and it requires a few extra steps. When you create your TLS/SSL certificate, you must create a complete certificate chain with an allowed certificate authority (CA) that is part of the [Microsoft Trusted CA List](https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT). If you use a nonallowed CA, your request is rejected. If a certificate without complete chain is presented, requests, which involve that certificate aren't guaranteed to work as expected.
 
 ### Prepare your Azure Key Vault account and certificate
@@ -174,7 +167,7 @@ If your CNAME record is in the correct format, DigiCert automatically verifies y
 Automatic validation typically takes a few hours. If you don't see your domain validated in 24 hours, open a support ticket.
 
 >[!NOTE]
-> If you have a Certificate Authority Authorization (CAA) record with your DNS provider, it must include the appropriate CAs for authorization. DigiCert is the CA for Microsoft and Edgio profiles. For information about managing CAA records, see [Manage CAA records](https://support.dnsimple.com/articles/manage-caa-record/). For a CAA record tool, see [CAA Record Helper](https://sslmate.com/caa/).
+> If you have a Certificate Authority Authorization (CAA) record with your DNS provider, it must include the appropriate CAs for authorization. DigiCert is the CA for Azure CDN profiles. For information about managing CAA records, see [Manage CAA records](https://support.dnsimple.com/articles/manage-caa-record/). For a CAA record tool, see [CAA Record Helper](https://sslmate.com/caa/).
 
 ### Custom domain isn't mapped to your CDN endpoint
 
@@ -247,7 +240,7 @@ In this section, you learn how to disable HTTPS for your custom domain.
 
 1. In the [Azure portal](https://portal.azure.com), search for and select **CDN profiles**.
 
-2. Choose your **Azure CDN Standard from Microsoft**, **Azure CDN Standard from Edgio**, or **Azure CDN Premium from Edgio** profile.
+2. Select your **Azure CDN Standard from Microsoft (classic)** profile.
 
 3. In the list of endpoints, pick the endpoint containing your custom domain.
 
@@ -267,14 +260,11 @@ After the custom domain HTTPS feature is disabled, it can take up to 6-8 hours f
 
 1. *Who is the certificate provider and what type of certificate is used?*
 
-    A dedicated certificate provided by Digicert is used for your custom domain for:
-
-    - **Azure Content Delivery Network from Edgio**
-    - **Azure Content Delivery Network from Microsoft**
+    A dedicated certificate provided by Digicert is used for your custom domain for **Azure Content Delivery Network from Microsoft (classic)**.
 
 2. *Do you use IP-based or Server Name Indication (SNI) TLS/SSL?*
 
-    Both **Azure CDN from Edgio** and **Azure CDN Standard from Microsoft** use SNI TLS/SSL.
+    **Azure CDN Standard from Microsoft (classic)** use SNI TLS/SSL.
 
 3. *What if I don't receive the domain verification email from DigiCert?*
 
@@ -290,20 +280,10 @@ After the custom domain HTTPS feature is disabled, it can take up to 6-8 hours f
 
     Certificate Authority Authorization record isn't currently required. However, if you do have one, it must include DigiCert as a valid CA.
 
-6. *On June 20, 2018, Azure CDN from Edgio started using a dedicated certificate with SNI TLS/SSL by default. What happens to my existing custom domains using Subject Alternative Names (SAN) certificate and IP-based TLS/SSL?*
-
-    Your existing domains are gradually migrated to single certificate in the upcoming months if Microsoft analyzes that only SNI client requests are made to your application.
-
-    If non-SNI clients are detected, your domains stay in the SAN certificate with IP-based TLS/SSL. Requests to your service or clients that are non-SNI, are unaffected.
-
-7. *How do cert renewals work with Bring Your Own Certificate?*
+6. *How do cert renewals work with Bring Your Own Certificate?*
 
     To ensure a newer certificate is deployed to POP infrastructure, upload your new certificate to Azure Key Vault. In your TLS settings on Azure Content Delivery Network, choose the newest certificate version and select save. Azure Content Delivery Network will then propagate your new updated cert.
 
-    > [!IMPORTANT]
-    > * As of June 20, 2024, Azure CDN Standard and Premium from Edgio won't support the **Use my own certificates** feature. This feature will be reintroduced again in early 2025.
-    > * What are the required actions for custom domains using this feature? BYOC certificates already deployed on the Edgio platform will remain valid until its expiration date. No action is required for certificates expiring in 2025. We encourage you to switch over to *CDN Managed* for certificates requiring an update or will be expiring this year. If you're requiring additional assistance, submit a support request to work with a support engineer.
-
 ## Next steps
 
 In this tutorial, you learned how to:

articles/cdn/cdn-ddos.md

@@ -22,14 +22,6 @@ A content delivery network provides DDoS Protection by design. In addition to th
 
 Azure Content Delivery Network from Microsoft is protected by [Azure Basic DDoS](../ddos-protection/ddos-protection-overview.md). It's integrated into the Azure content delivery network from Microsoft platform by default and at no extra cost. The full scale and capacity of Azure Content Delivery Network 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 content delivery network endpoints. This service also has a proven track record in protecting Microsoft's enterprise and consumer services from large-scale attacks.
 
-<a name='azure-cdn-from-verizon'></a>
-
-<a name='azure-cdn-from-edgio'></a>
-
-## Azure Content Delivery Network from Edgio
-
-Azure Content Delivery Network from Edgio is protected by Edgio's proprietary DDoS mitigation platform. It's integrated into Azure Content Delivery Network from Edgio 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 content delivery network endpoints.
-
 ## Next steps
 
 Learn more about [Azure DDoS](../ddos-protection/ddos-protection-overview.md).

articles/cdn/cdn-dynamic-site-acceleration.md

@@ -16,10 +16,7 @@ With the explosion of social media, electronic commerce, and the hyper-personali
 
 Standard content delivery network capability includes the ability to cache files closer to end users to speed up delivery of static files. However, with dynamic web applications, caching that content in edge locations isn't possible because the server generates the content in response to user behavior. Speeding up the delivery of such content is more complex than traditional edge caching and requires an end-to-end solution that finely tunes each element along the entire data path from inception to delivery. With Azure Content Delivery Network dynamic site acceleration (DSA) optimization, the performance of web pages with dynamic content is measurably improved.
 
-**Azure CDN from Edgio** offers DSA optimization through the **Optimized for** menu during endpoint creation. Dynamic site acceleration from Microsoft is offered via [Azure Front Door](../frontdoor/front-door-overview.md).
-
-> [!IMPORTANT]
-> For **Azure CDN from Edgio** profiles, you can't change the optimization of a content delivery network endpoint after it has been created.
+Dynamic site acceleration from Microsoft is offered through [Azure Front Door](../frontdoor/front-door-overview.md).
 
 <a name='cdn-endpoint-configuration-to-accelerate-delivery-of-dynamic-files'></a>
 
@@ -62,29 +59,16 @@ Route optimization is important because the Internet is a dynamic place, where t
 
 Route optimization chooses the most optimal path to the origin so that a site is continuously accessible and dynamic content is delivered to end users via the fastest and most reliable route possible.
 
-The Edgio network uses a combination of Anycast DNS, high capacity support PoPs, and health checks, to determine the best gateways to best route data from the client to the origin.
-
 As a result, fully dynamic and transactional content is delivered more quickly and more reliably to end users, even when it's not cacheable.
 
 ### TCP Optimizations
 
-Transmission Control Protocol (TCP) is the standard of the Internet Protocol suite used to deliver information between applications on an IP network. By default, the establishment of a TCP connection requires multiple bidirectional requests. Additionally, there are limits in place to prevent network congestion, which can lead to inefficiencies when operating at scale. **Azure CDN from Edgio** handles this problem by optimizing in three areas:
-
-- [Eliminating TCP slow start](#eliminating-tcp-slow-start)
-- [Using persistent connections](#leveraging-persistent-connections)
+Transmission Control Protocol (TCP) is the standard of the Internet Protocol suite used to deliver information between applications on an IP network. By default, the establishment of a TCP connection requires multiple bidirectional requests. Additionally, there are limits in place to prevent network congestion, which can lead to inefficiencies when operating at scale.
 
 #### Eliminating TCP slow start
 
 TCP *slow start* is an algorithm of the TCP protocol that prevents network congestion by limiting the amount of data sent over the network. It starts off with small congestion window sizes between sender and receiver until the maximum is reached or packet loss is detected.
 
-**Azure CDN from Edgio** profiles eliminate TCP slow start with the following three steps:
-
-1. Health and bandwidth monitoring is used to measure the bandwidth of connections between edge POP servers.
-
-2. Metrics are shared between edge POP servers so that each server is aware of the network conditions and server health of the other PoPs around them.
-
-3. The content delivery network edge servers make assumptions about some transmission parameters, such as what the optimal window size should be when communicating with other content delivery network edge servers in its proximity. This step means that the initial congestion window size can be increased if the health of the connection between the content delivery network edge servers is capable of higher packet data transfers.
-
 <a name='leveraging-persistent-connections'></a>
 
 #### Using persistent connections
@@ -93,16 +77,12 @@ When you're using a content delivery network, fewer unique machines connect to y
 
 As previously mentioned, several handshake requests are required to establish a TCP connection. Persistent connections, which get implemented by the `Keep-Alive` HTTP header, reuse existing TCP connections for multiple HTTP requests to save round-trip times and speed up delivery.
 
-**Azure CDN from Edgio** also sends periodic keep-alive packets over the TCP connection to prevent an open connection from being closed.
-
 ## Caching
 
 With DSA, caching is turned off by default on the content delivery network, even when the origin includes `Cache-Control` or `Expires` headers in the response. DSA is typically used for dynamic assets that shouldn't be cached because they're unique to each client. Caching can break this behavior.
 
 If you have a website with a mix of static and dynamic assets, it's best to take a hybrid approach to get the best performance.
 
-With **Azure CDN Standard from Edgio** profiles, you can turn on caching for specific DSA endpoints by using [caching rules](cdn-caching-rules.md).
-
 To access caching rules:
 
 1. From the **CDN profile** page, under settings, select **Caching rules**.
@@ -113,8 +93,6 @@ To access caching rules:
 
 2. Create a global or custom caching rule to turn on caching for your DSA endpoint.
 
-For **Azure CDN Premium from Edgio** profiles only, you turn on caching for specific DSA endpoints by using the [rules engine](./cdn-verizon-premium-rules-engine.md). Any rules that are created affect only those endpoints of your profile that are optimized for DSA.
-
 To access the rules engine:
 
 1. From the **CDN profile** page, select **Manage**.

articles/cdn/cdn-edge-performance.md

@@ -46,7 +46,7 @@ This dashboard consists of:
 
 1. From the CDN profile page, select the **Manage** button.
 
-    :::image type="content" source="./media/cdn-edge-performance/cdn-manage-btn.png" alt-text="Screenshot of the manage button from an Azure CDN Edgio Premium profile.":::
+    :::image type="content" source="./media/cdn-edge-performance/cdn-manage-btn.png" alt-text="Screenshot of the manage button from an Azure CDN profile.":::
 
     The CDN management portal opens.
 2. Hover over the **Analytics** tab, then hover over the **Edge Performance Analytics** flyout. Select on **Dashboard**.
@@ -144,7 +144,7 @@ Each report in this module contains a chart and statistics on bandwidth and traf
 
 1. From the CDN profile page, select the **Manage** button.
 
-    :::image type="content" source="./media/cdn-edge-performance/cdn-manage-btn.png" alt-text="Screenshot of the manage button from an Azure CDN Edgio Premium profile.":::
+    :::image type="content" source="./media/cdn-edge-performance/cdn-manage-btn.png" alt-text="Screenshot of the manage button from an Azure CDN profile.":::
 
     The CDN management portal opens.
 2. Hover over the **Analytics** tab, then hover over the **Edge Performance Analytics** flyout. Select on **HTTP Large Object**.

articles/cdn/cdn-features.md

@@ -14,11 +14,7 @@ ms.custom: mvc
 
 [!INCLUDE [Azure CDN from Microsoft (classic) retirement notice](../../includes/cdn-classic-retirement.md)]
 
-Azure Content Delivery Network includes three products:
 
-- **Azure CDN Standard from Microsoft**
-- **Azure CDN Standard from Edgio (formerly Verizon)**
-- **Azure CDN Premium from Edgio (formerly Verizon)**.
 
 The following table compares the features available with each product.