Merge pull request #289361 from duongau/edgioretire

Azure CDN - Edgio to Azure Front Door migration using Traffic Manager

Author: v-dirichards

articles/cdn/edgio-retirement-faq.md

@@ -0,0 +1,65 @@
+---
+title: Azure CDN from Edgio retirement FAQ
+titleSuffix: Azure Content Delivery Network
+description: Common questions about the retirement of Azure CDN Standard from Edgio.
+services: cdn
+author: duongau
+ms.service: azure-cdn
+ms.topic: how-to
+ms.date: 10/30/2024
+ms.author: duau
+---
+
+# Azure CDN from Edgio retirement FAQ
+
+Azure CDN from Edgio will be retired on November 4, 2025. You must migrate your workload to Azure Front Door before this date to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
+
+## Frequently asked questions
+
+### I see Edgio filed for Chapter 11 bankruptcy. Can Microsoft guarantee that Azure CDN from Edgio’s availability and services until November 4, 2025?
+
+Edgio informed us that their services remain operational until at least November 4, 2025. However, we can't guarantee that Edgio doesn't unexpectedly cease operations before this date due to circumstances beyond our control.
+
+### How does Microsoft assist me with migrating my workloads from Azure CDN from Edgio?
+
+You're encouraged to migrate their workloads to Azure Front Door. You need to determine if Azure Front Door is suitable for their workloads and set up a test environment to validate compatibility. For a feature comparison, see [Azure Front Door and Azure CDN features](../frontdoor/front-door-cdn-comparison.md).
+
+If Azure Front Door isn't compatible with your workload, we offer a service called [Routing Preference Unmetered](../virtual-network/ip-services/routing-preference-unmetered.md) also known as *CDN Interconnect*. This service routes traffic from your Azure resources to another CDN. You can choose to continue working with Edgio directly to minimize interruptions and keep your origins on Azure. For further information, you can contact Microsoft support or reach out to [Edgio](https://edg.io/contact-us/).
+
+### Does Microsoft validate my workloads work on Azure Front Door?
+
+You need to determine if Azure Front Door suits your workloads. We recommend setting up a test environment to validate that your services are compatible with Azure Front Door.
+
+### What alternative solutions does Microsoft offer?
+
+We encourage you to consider migrating your workloads to Azure Front Door. For a feature comparison between Azure Front Door and Azure CDN from Edgio, see [Azure CDN Features](cdn-features.md). For a pricing comparison, visit [Azure CDN Pricing](https://azure.microsoft.com/pricing/details/cdn/).
+
+### If I determined my workload isn't a match for Azure Front Door, what are my options?
+
+If you find that Azure Front Door isn't suitable for your workload, we offer an alternative service called [Routing Preference Unmetered](../virtual-network/ip-services/routing-preference-unmetered.md), also known as "CDN Interconnect." This service might allow free data transfer for traffic egressing from your Azure resources to another CDN of your choice.
+
+Additionally, you can choose to continue working directly with Edgio to minimize interruptions, keeping your origins on Azure while utilizing Edgio's services. For further information, contact Microsoft Support or reach out to [Edgio](https://edg.io/contact-us/).
+
+### If I find Azure Front Door isn't compatible with my workload, can I transfer my services to Edgio and have them bill me directly?
+
+Edgio informed Microsoft that they strive to facilitate seamless transitions for users who contact them directly. However, Microsoft can't guarantee the success of these transitions.
+
+### What are Azure Front Door and Microsoft's media delivery capabilities?
+
+Azure Front Door supports live and on-demand video streaming for small to medium-sized businesses. Edgio enabled Microsoft to deliver large-scale streaming workloads, such as major live events and over-the-top (OTT) services. While A Azure Front Door is exploring the capability to deliver streaming services for large-scale enterprises, there's currently no estimated time of arrival (ETA) for this feature.
+
+### What will happen if I don't take action before November 4, 2025?
+
+If no action is taken before November 4, 2025, Azure CDN from Edgio profiles and associated data will be removed from Edgio systems. It's imperative that users migrate their workloads before this date to avoid any service disruptions and data loss.
+
+### Is Microsoft publishing a self-service guide to manually migrate my Azure Front Door-compatible workloads from Azure CDN from Edgio to Azure Front Door?
+
+Yes, you can migrate your workloads manually by following the steps in the [Azure CDN to Azure Front Door migration guide](../frontdoor/migrate-cdn-to-front-door.md). This guide provides detailed instructions on how to set up an Azure Front Door profile, test functionality, and migrate your workloads from Azure CDN from Edgio to Azure Front Door with the help of Azure Traffic Manager.
+
+### How is Microsoft communicating the retirement of Azure CDN from Edgio, and how often are reminders sent?
+
+We communicate the retirement of Azure CDN from Edgio through multiple channels, including email notifications and in-portal messages. Reminders are sent at least monthly to all users with active Edgio profiles to ensure they're aware of the upcoming changes and necessary actions.
+
+## Next steps
+
+Migrate your Azure CDN from Edgio workloads to Azure Front Door by following the steps in the [Azure CDN to Azure Front Door migration guide](../frontdoor/migrate-cdn-to-front-door.md).

articles/frontdoor/TOC.yml

@@ -246,6 +246,8 @@
       href: ../cdn/classic-cdn-retirement-faq.md
     - name: Akamai retirement FAQ
       href: ../cdn/akamai-retirement-faq.md?toc=/azure/frontdoor/TOC.json
+    - name: Edgio retirement FAQ
+      href: ../cdn/edgio-retirement-faq.md?toc=/azure/frontdoor/TOC.json
     - name: Security baseline
       href: /security/benchmark/azure/baselines/content-delivery-network-security-baseline?toc=/azure/frontdoor/TOC.json
     - name: DDoS protection
@@ -454,6 +456,8 @@
           href: ../cdn/cdn-app-dev-node.md?toc=/azure/frontdoor/TOC.json
     - name: Edgio
       items:
+      - name: Migrate to Azure Front Door
+        href: migrate-cdn-to-front-door.md
       - name: Standard
         items:
         - name: Optimize content

articles/frontdoor/media/migrate-cdn-to-front-door/add-origin.png

@@ -0,0 +1,196 @@
+---
+title: Migrate Azure CDN from Edgio to Azure Front Door
+titleSuffix: Azure Content Delivery Network
+description: Learn how to migrate your workloads from Azure CDN from Edgio to Azure Front Door using Azure Traffic Manager.
+services: frontdoor
+author: duongau
+ms.service: azure-frontdoor
+ms.topic: how-to
+ms.date: 10/30/2024
+ms.author: duau
+---
+
+# Migrate Azure CDN from Edgio to Azure Front Door
+
+Azure CDN from Edgio will be retired on November 4, 2025. You must migrate your workload to Azure Front Door before this date to avoid service disruption. This article provides guidance on how to migrate your workloads from Azure CDN from Edgio to Azure Front Door using Azure Traffic Manager. The migration process in this article can also be used to migrate workloads from a legacy CDN to Azure Front Door.
+
+Azure Traffic Manager initially routes all traffic to the Azure CDN from Edgio. After you set up Azure Front Door, you can update the Traffic Manager profile to incrementally route traffic to the Azure Front Door. This approach allows you to validate if Azure Front Door is compatible with your workloads before fully migrating.
+
+We recommend that your plan this migration well in advance and test the functionality over the course of a few days to ensure a smooth transition. 
+
+## Prerequisites
+
+- Review the [feature differences](front-door-cdn-comparison.md) between Azure CDN and Azure Front Door to determine if there are any compability gaps.
+- You need access to a VM connected to the internet that can run Wget on Linux or Invoke-WebRequest on Windows using PowerShell.
+- You need access to a monitoring tool such as CatchPoint or ThousandEyes to verify the availability of your URLs before and after the migration. These tools are the most ideal because they can monitor the availability of your URLs from different locations around the world. `webpagetest.org` is another option, but it only provides a limited view of your URLs from a few locations.
+
+## Migrate your workloads
+
+The followings steps assume you're using an Azure Blob Storage account as your origin. If you're using a different origin, adjust the steps accordingly.
+
+:::image type="content" source="./media/migrate-cdn-to-front-door/cdn-traffic-manager.png" alt-text="Diagram of Azure Traffic Manager distributing traffic between Azure Front Door and Azure CDN from Edgio.":::
+
+### Gather information
+
+1. Collect the following information from your Azure CDN from Edgio profile:
+
+    - Endpoints
+    - Origin configurations
+    - Custom domains
+    - Caching settings
+    - Compression settings
+    - Web application firewall (WAF) settings
+    - Custom rules settings
+
+1. Determine which tier of Azure Front Door is suitable for your workloads. For more information, see [Azure Front Door comparison](../frontdoor/front-door-cdn-comparison.md).
+
+1. Review the origin settings in your Azure CDN from Edgio profile.
+
+1. Determine a test URL with your Azure CDN from Edgio profile and perform a `wget` or `Invoke-WebRequest` to obtain the HTTP header information. 
+
+1. Enter the URL into the monitoring tool to understand the geographic availability of your URL.
+
+### Set up Azure Front Door
+
+1. From the Azure portal, select **+ Create a resource**, then search for **Front Door**.
+
+1. Select **Front Door and CDN profiles** and then select **Create**.
+
+1. On the *Compare offerings* pages, select **Azure Front Door** and then select **Custom create**.
+
+1. Select **Continue to create a Front Door**.
+
+1. Select the subscription and resource group. Enter a name for the Azure Front Door profile. Then select the tier that best suits your workloads and select the **Endpoint** tab.
+
+1. Select **Add an endpoint**. Enter a name for the endpoint, then select **Add**. The endpoint name will look like `<endpointname>-<hash>.xxx.azurefd.net`.
+
+1. Select **+ Add a route**. Enter a name for the route and note the **Domain** selected. Leave the **Patterns to match** and **Accepted protocols** as the default settings.
+
+    > [!NOTE]
+    > A CDN profile can have multiple endpoints, so you may need to create multiple routes.
+
+1. Select **Add a new origin group**. Enter a name for the origin group and select the **+ Add an origin** button. Enter the origin name and select the origin type. This example uses Azure Blob Storage, so select **Storage** as the origin type. Select the hostname of the Azure Blob Storage account and leave the rest of the settings as default. Select **Add**.
+
+    :::image type="content" source="./media/migrate-cdn-to-front-door/add-origin.png" alt-text="Screenshot of adding an Azure Blob Storage as an origin to Azure Front Door.":::
+
+1. Leave the rest of the settings as default and select **Add**.
+
+1. If caching was enabled in your Azure CDN from Edgio profile, select **Enable caching** and set the caching rules.
+
+    > [!NOTE]
+    > Azure CDN from Edgio *Standard-cache* is equivalent to Azure Front Door *Ignore query string* caching.
+
+1. Select **Enable compression** if you have compression enabled in your Azure CDN from Edgio profile. Ensure the origin path matches the path in your Azure CDN from Edgio profile. If this isn't set correctly, the origin won't be able to serve the content and will return a 4xx error.
+
+1. Select **Add** to create the route.
+
+1. Select **+ Add a policy** to set up web application firewall (WAF) settings and set up custom rules you determined in the previous steps.
+
+1. Select **Review + create** and then select **Create**.
+
+1. Set up the custom domain for the Azure Front Door profile. For more information, see [Custom domains](front-door-custom-domain.md). You may have multiple custom domains in your Azure CDN from Edgio profile. Ensure you add all custom domains to the Azure Front Door profile and associate them with the correct routes.
+
+### Set up Traffic Manager
+
+The steps in this section need to be repeated for each endpoint in your Azure CDN from Edgio profile. It is critical that the health check is set up correctly to ensure that the Traffic Manager profile routes traffic to the Azure CDN or Azure Front Door.
+
+1. From the Azure portal, select **+ Create a resource**, then search for **Traffic Manager profile**.
+
+1. Enter a name for the Traffic Manager profile.
+
+1. Select the routing method **Weighted**.
+
+1. Select the same subscription and resource group as the Azure Front Door profile then select **Create**.
+
+1. Select **Endpoints** from the left-hand menu, and then select **+ Add**.
+
+1. For the **Type**, select **External endpoint**.
+
+1. Enter a name for the endpoint and leave the **Enable Endpoint** checked.
+
+1. Enter the **Fully-qualified domain name (FQDN)** of the Azure CDN from Edgio profile. For example, `yourdomain.azureedge.net`.
+
+1. Set the **Weight** to 100.
+
+1. For *Health check*, select **Always serve traffic**. This setting disables the health check and always routes traffic to the endpoint.
+
+    :::image type="content" source="./media/migrate-cdn-to-front-door/cdn-endpoint.png" alt-text="Screenshot of adding the Azure CDN from Edgio as an endpoint in Azure Traffic Manager.":::
+
+1. Add another endpoint for the Azure Front Door profile and select **External endpoint**.
+
+1. Enter a name for the endpoint and uncheck the **Enable Endpoint** setting.
+
+1. Enter the **Fully-qualified domain name (FQDN)** of the Azure Front Door profile. For example, `your-new-endpoint-name.azurefd.net`.
+
+1. Set the **Weight** to 1.
+
+1. Since the endpoint is disabled, the **Health check** setting isn't relevant.
+
+### Internal testing of Traffic Manager profile
+
+1. Perform a DNS dig to test the Traffic Manager profile: `dig your-profile.trafficmanager.net`. The dig command should always return the CNAME of the Azure CDN from Edgio profile: `yourdomain.azureedge.net`.
+
+1. Test the Azure Front Door profile by manually adding a DNS entry in your local hosts file pointing to the Azure Front Door profile:
+
+    1. Get the IP address of the Azure Front Door profile by performing a DNS dig.
+    
+    1. Add a new line to your hosts file with the IP address followed by a space and then `your-new-endpoint-name.azurefd.net`. For example, `203.0.113.254 your-new-endpoint-name.azurefd.net`.
+    
+        1. For Windows, the hosts file is located at `C:\Windows\System32\drivers\etc\hosts`.
+        
+        1. For Linux, the hosts file is located at `/etc/hosts`.
+    
+    1. Test the functionality of the Azure Front Door profile locally and ensure everything is working as expected.
+    
+    1. Remove the entry from the hosts file when testing is complete.
+
+### Configure Traffic Manager with CNAME
+
+We only recommend this step after you have fully tested the Azure Front Door profile and are confident that it is working as expected.
+
+1. Sign into your DNS provider and locate the CNAME record for the Azure CDN from Edgio profile.
+
+1. Locate the custom domain you want to migrate to Azure Front Door and set the time-to-live (TTL) to 600 secs (10 minutes).
+
+1. Update the CNAME record to point to the Traffic Manager profile: `your-profile.trafficmanager.net`.
+
+1. In the Azure portal, navigate to the Traffic Manager profile and select **Endpoints**.
+
+1. Enable the Azure Front Door endpoint and select **Always serve traffic** for the health check.
+
+1. Use a tool like dig or nslookup to verify that the DNS change propagated and pointed to the correct Traffic Manager profile.
+
+1. Verify that the Azure CDN from Edgio profile is working properly by checking the monitoring tool you set up earlier.
+
+### Gradual traffic shift
+
+The initial traffic distribution starts by routing a small percentage of traffic to the Azure Front Door profile. Monitor the performance of the Azure Front Door profile and gradually increase the traffic percentage until all traffic is routed to the Azure Front Door profile.
+
+1. Start by routing 10% of the traffic to the Azure Front Door profile and the rest to the Azure CDN from Edgio profile.
+
+1. Monitor the performance of the Azure Front Door profile and the Azure CDN from Edgio profile using the monitoring tool you set up earlier. Review your internal applications and systems logs to ensure that the Azure Front Door profile is working as expected. Look at metrics and logs to observe for 4xx/5xx errors, cache/byte hit ratios, and origin health.
+
+    > [!NOTE]
+    > If you don't have access to a third-party tool, you can use [Webpagetest](https://webpagetest.org) to verify the availability of your endpoint from a remote location. However, this tool only provides a limited view of your URLs from a few locations around the world, so you may not see any changes until you have fully shifted traffic to the Azure Front Door profile.
+
+1. Gradually increase the traffic percentage to the Azure Front Door profile by 10% increments until all traffic is routed to the Azure Front Door profile. Ensure that you're testing and monitoring the performance of the Azure Front Door profile at each increment.
+
+1. Once you're confident that the Azure Front Door profile is working as expected, update the Traffic Manager profile to route all traffic to the Azure Front Door profile.
+
+    1. Ensure the Azure Front Door endpoint is enabled, Weight is set to 100, and the health check is set to **Always serve traffic**.
+
+    1. Ensure the Azure CDN from Edgio endpoint is disabled.
+
+### Remove Azure Traffic Manager
+
+1. Sign in to your DNS provider. Change the CNAME record from the Traffic Manager profile to the Azure Front Door profile: `<endpointname>-<hash>.xxx.azurefd.net`.
+
+1. Over the next few hours, begin testing using dig, and monitor using the monitoring tool to ensure the DNS is fully propagated correctly around the world.
+
+1. Set the DNS TTL back to the original value (60 minutes).
+
+At this stage you have fully migrated all traffic from Azure CDN from Edgio to Azure Front Door.
+
+## Next steps
+
+Learn about [best practices](best-practices.md) for Azure Front Door.

articles/frontdoor/media/migrate-cdn-to-front-door/cdn-endpoint.png

@@ -11,4 +11,6 @@
 ---
 
 > [!IMPORTANT]
-> Azure CDN Standard from Microsoft (classic) will be retired on **September 30, 2027**. To avoid any service disruption, it is important that you [**migrate your Azure CDN Standard from Microsoft (classic) profiles**](../articles/cdn/migrate-tier.md) to Azure Front Door Standard or Premium tier by September 30, 2027. For more information, see [**Azure CDN Standard from Microsoft (classic) retirement**](https://azure.microsoft.com/updates/v2/Azure-CDN-Standard-from-Microsoft-classic-will-be-retired-on-30-September-2027).
+> Azure CDN Standard from Microsoft (classic) will be retired on **September 30, 2027**. To avoid any service disruption, it is important that you [**migrate your Azure CDN Standard from Microsoft (classic) profiles**](../articles/cdn/migrate-tier.md) to Azure Front Door Standard or Premium tier by September 30, 2027. For more information, see [**Azure CDN Standard from Microsoft (classic) retirement**](https://azure.microsoft.com/updates/v2/Azure-CDN-Standard-from-Microsoft-classic-will-be-retired-on-30-September-2027).
+>
+> Azure CDN from Edgio will be retired on **November 4, 2025**. You must [migrate your workload](../articles/frontdoor/migrate-cdn-to-front-door.md) to Azure Front Door before this date to avoid service disruption. For more information, see [**Azure CDN from Edgio retirement FAQ**](../articles/cdn/edgio-retirement-faq.md).