Skip to content

Commit a22a5fd

Browse files
committed
replace PR 292602
1 parent 39be76c commit a22a5fd

File tree

1 file changed

+33
-23
lines changed

1 file changed

+33
-23
lines changed

articles/cdn/edgio-retirement-faq.md

Lines changed: 33 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: cdn
66
author: duongau
77
ms.service: azure-cdn
88
ms.topic: how-to
9-
ms.date: 12/22/2024
9+
ms.date: 1/2/2025
1010
ms.author: duau
1111
---
1212

@@ -39,10 +39,34 @@ The following is a recap of the migration options we sent to all users:
3939
- If Azure Front Door isn't compatible with your workloads, determine if Akamai could be compatible via Azure Marketplace or work with another CDN provider. If you chose to work with Akamai, feel free to contact Microsoft Support, and we can put you in touch with the Akamai team dedicated to performing migrations to their platform.
4040

4141
> [!IMPORTANT]
42-
> - If you plan a migration to Akamai or another CDN provider, you must set the Feature Flag `DoNotForceMigrateEdgioCDNProfiles` before January 7, 2025. Doing so will prevent Microsoft from migrating you to Azure Front Door (please see below). Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date.
42+
> - If you plan a migration to Akamai or another CDN provider, you [must set the Feature Flag]((../azure-resource-manager/management/preview-features.md)) `DoNotForceMigrateEdgioCDNProfiles` before January 7, 2025. Doing so will prevent Microsoft from migrating you to Azure Front Door (please see below). Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date.
4343
> - Please be advised we will need to halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This means you will not be able update your CDN profile configuration, but your services on Azure CDN from Edgio will still operate until you are migrated or the Edgio platform is shut down on January 15, 2025. If you apply the `DoNotForceMigrateEdgioCDNProfiles` feature flag before January 3, your configuration will not be frozen for changes.
4444
45-
- If you have any services running on Azure CDN from Edgio on January 7, 2025 and haven't informed us of your plans (please see above), we'll attempt to migrate your services over to Azure Front Door on January 7, 2025. We'll be performing this migration to Azure Front Door on a “best effort” basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio.
45+
- If you have any services running on Azure CDN from Edgio on January 7, 2025 and haven't informed us of your plans (please see above), we'll attempt to migrate your services over to Azure Front Door between January 7th and 14th, 2025. We'll be performing this migration to Azure Front Door on a “best effort” basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio. If Microsoft attempts to migrate your workload(s) to Azure Front Door, we will send you a follow-up email to advise customers of the status of the migration, and any potential actions/guidance.
46+
47+
### Can you provide more insights into the automatic migration to Azure Front Door Standard?
48+
49+
If Azure CDN from Edgio customers do not set a Feature Flag by following [these instructions]((../azure-resource-manager/management/preview-features.md)) (select the Feature Flag "DoNotForceMigrateEdgioCDNProfiles") before 7 January 2025, Microsoft will migrate existing Azure CDN from Edgio profile to an Azure Front Door Standard profile between January 7th and 14th, 2025. We will be performing these migrations to Azure Front Door on a "best effort" basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio. Hence, as noted previously, customers should migrate themselves and not rely on this automatic migration.
50+
Important notes regarding these “best effort” automatic migrations to Azure Front Door Standard:
51+
- Between January 7th and 14th, 2025 you'll receive an email notification confirming if your workloads have been successfully migrated to Azure Front Door Standard or if the migration was unsuccessful. If the migration was successful and you encounter issues with availability, performance, or feature functionality, contact Microsoft support for assistance. For customers whom the migration unsuccessful will be provided guidance on possible next steps they can take.
52+
- We're migrating customers to Azure Front Door Standard as it may be more cost-effective. If you need the extra features of Azure Front Door Premium, you can [upgrade your service](../frontdoor/tier-upgrade.md).
53+
- Existing Azure CDN from Edgio domains (custom domains and/or *.azureedge.net domains) will be added as custom domains on the new Front Door endpoints and we will switch the traffic from Edgio platform to Front Door platform.
54+
- We will not be able to rollback the automatic migration.
55+
- Microsoft will not always be able to maintain feature level parity in the new Front Door configuration.
56+
- Automatic migration will not be possible for endpoints with `*.vo.msecnd.net` domains.
57+
58+
59+
### What is the recap of the key dates?
60+
61+
| Date | Event |
62+
|-------------------|---------------------------------------------------------------------------------------------------------------------------|
63+
| December 13, 2024 | No new Azure CDN from Edgio profiles can be created. |
64+
| January 3, 2025 | No more profile changes will be allowed on Azure CDN from Edgio. |
65+
| January 6, 2025 | Last date for customers to set a Feature Flag to advise Microsoft not to migrate your workloads to Azure Front Door. |
66+
| January 7-14, 2025 | All remaining Azure CDN from Edgio profiles will be migrated to Azure Front Door if the said Feature Flag is not set. |
67+
| January 7-14, 2025 | Azure CDN from Edgio customers who did not act are notified via email of their migration status to Azure Front Door. |
68+
| January 14, 2025 | Last day of service on Azure CDN from Edgio. |
69+
| January 15, 2025 | Shutdown of the Edgio platform. |
4670

4771
### Can I retain my existing *.azureedge.net domain when I move to Azure Front Door?
4872

@@ -71,12 +95,6 @@ For any questions regarding billing changes, reach out to our support team or yo
7195

7296
No, 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.
7397

74-
### What will happen during automatic migration?
75-
76-
Microsoft will convert your existing Azure CDN from Edgio profile to an Azure Front Door Standard profile. Your existing Azure CDN from Edgio domains (custom domains and/or *.azureedge.net domains) will be added as custom domains on the new Front Door endpoints and we will switch the traffic from Edgio platform to Front Door platform.
77-
78-
Note that Microsoft will not be able to maintain feature level parity in the new Front Door configuration. The migration will be done on a “best effort” basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio. We will not be able to rollback the automatic migration in case of any issues. Hence, customers with business critical traffic should migrate by themselves and not rely on automatic migration.
79-
8098
### What will happen after Microsoft migrates my workloads to Azure Front Door on January 7, 2025?
8199

82100
After the migration, you'll receive an email notification confirming whether your workloads have been successfully migrated to Azure Front Door Standard or if the migration was unsuccessful. We're migrating you to Azure Front Door Standard as it may be more cost-effective. If you need the extra features of Azure Front Door Premium, you can [upgrade your service](../frontdoor/tier-upgrade.md).
@@ -85,19 +103,7 @@ If the migration was unsuccessful or if you encounter issues with availability,
85103

86104
### How is Microsoft communicating the retirement of Azure CDN from Edgio, and how often are reminders sent?
87105

88-
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.
89-
90-
### What is the recap of the key dates?
91-
92-
| Date | Event |
93-
|-------------------|---------------------------------------------------------------------------------------------------------------------------|
94-
| December 13, 2024 | Creation of new Azure CDN from Edgio profiles is no longer allowed. |
95-
| January 3, 2025 | No further changes to Azure CDN from Edgio profiles will be permitted. |
96-
| January 6, 2025 | Deadline for setting a Feature Flag to prevent automatic migration to Azure Front Door. |
97-
| January 7, 2025 | Automatic migration of remaining Azure CDN from Edgio profiles to Azure Front Door begins if the Feature Flag isn't set. |
98-
| January 7-8, 2025 | Notifications sent to customers regarding the status of their migration to Azure Front Door. |
99-
| January 14, 2025 | Final day of service for Azure CDN from Edgio. |
100-
| January 15, 2025 | Shutdown of the Edgio platform. |
106+
We communicate the retirement of Azure CDN from Edgio through multiple channels, including email notifications and in-portal messages. Reminders are currently sent at least weekly to all users with active Edgio profiles to ensure they're aware of the upcoming changes and necessary actions.
101107

102108
### Can I request an extension for the retirement/shutdown of the Azure CDN from Edgio service?
103109

@@ -109,4 +115,8 @@ No, extensions aren't possible. If you don't want us to automatically migrate yo
109115

110116
### Can I set the feature flag at resource/profile level instead of subscription level?
111117

112-
No
118+
No.
119+
120+
### Can I be informed regarding the the exact date and time my Edgio profile will be automatically migrated?
121+
122+
No. We are doing this migration on a "best effort" basis between January 7th and 14th, 2025 for customers who did not take action prior. Therefore we will not be able to inform each customer regarding migration timings, but as noted previously after the migration we will inform you whether it was successful or not.

0 commit comments

Comments
 (0)