You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cdn/edgio-retirement-faq.md
+44-30Lines changed: 44 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,31 +6,31 @@ services: cdn
6
6
author: duongau
7
7
ms.service: azure-cdn
8
8
ms.topic: how-to
9
-
ms.date: 12/22/2024
9
+
ms.date: 1/3/2025
10
10
ms.author: duau
11
11
---
12
12
13
13
# Azure CDN from Edgio retirement FAQ
14
14
15
-
Azure CDN from Edgio will be shut down on January 15, 2025. You must migrate your workload to Azure Front Door before January 7, 2025 to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
15
+
Azure CDN from Edgio is shutting down on January 15, 2025. You must migrate your workload to Azure Front Door before January 7, 2025 to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
16
16
17
17
## Frequently asked questions
18
18
19
19
### Why was the retirement date of Azure CDN from Edgio changed from November 4, 2025, to January 15, 2025?
20
20
21
-
[Akamai acquired select assets](https://www.prnewswire.com/news-releases/akamai-completes-acquisition-of-select-assets-of-edgio-302331398.html) from Edgio in December of 2024, and Microsoft was informed that the Edgio platform will end service on January 15, 2025. All Azure CDN from Edgio users must migrate their workloads to Azure Front Door or other CDN services before this date.
21
+
[Akamai acquired select assets](https://www.prnewswire.com/news-releases/akamai-completes-acquisition-of-select-assets-of-edgio-302331398.html) from Edgio in December of 2024, and Microsoft was informed that the Edgio platform is ending service on January 15, 2025. All Azure CDN from Edgio users must migrate their workloads to Azure Front Door or other CDN services before this date.
22
22
23
23
### I see Edgio filed for Chapter 11 bankruptcy. Can Microsoft guarantee that Azure CDN from Edgio’s availability and services until November 4, 2025?
24
24
25
-
Edgio has informed us that their services will remain operational until at least January 15, 2025. However, we can't guarantee that Edgio won't unexpectedly cease operations before this date due to circumstances beyond our control. Therefore, we'll automatically migrate your workload if you haven't taken action by January 7, 2025. Automatic migration will not be possible for endpoints with `*.vo.msecnd.net` domains.
25
+
Edgio informed us that their services are remaining operational until at least January 15, 2025. However, we can't guarantee that Edgio won't unexpectedly cease operations before this date due to circumstances beyond our control. Therefore, we'll automatically migrate your workload if you haven't taken action by January 7, 2025. Automatic migration isn't possible for endpoints with `*.vo.msecnd.net` domains.
26
26
27
27
### How can I see my impacted Azure CDN from Edgio resources?
28
28
29
29
You can see them in the [Migrate away from Azure CDN from Edgio](https://portal.azure.com/#view/Microsoft_Azure_Expert/RecommendationList.ReactView/recommendationTypeId/2c9e3f2a-7373-45e1-ab8b-f361e5f0c37f) dashboard.
30
30
31
31
### What options do I have with migrating my workloads out of Azure CDN from Edgio?
32
32
33
-
The following is a recap of the migration options we sent to all users:
33
+
The following process is a recap of the migration options we sent to all users:
34
34
35
35
- Validate if your workloads on Azure CDN from Edgio are compatible with Azure Front Door and migrate as soon as possible using these instructions before January 7, 2025. For more information, see [Comparison between Azure Front Door and Azure CDN services](../frontdoor/front-door-cdn-comparison.md) and [Frequently asked questions for Azure Front Door](../frontdoor/front-door-faq.yml).
36
36
- If you already use custom domains, follow steps in [Migrate Azure CDN from Edgio to Azure Front Door](../frontdoor/migrate-cdn-to-front-door.md).
@@ -39,10 +39,34 @@ The following is a recap of the migration options we sent to all users:
39
39
- 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.
40
40
41
41
> [!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.
43
-
> -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.
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 prevents Microsoft from migrating you to Azure Front Door (see the following comments). You have until January 14, 2025 to complete your migration to another CDN, but again Microsoft can't guarantee your services to be available on the Edgio platform before this date.
43
+
> -Be advised we need to halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This means you can't update your CDN profile configuration, but your services on Azure CDN from Edgio can still operate until you're migrated or the Edgio platform is shut down on January 15, 2025. If you apply the `DoNotForceMigrateEdgioCDNProfiles` feature flag before January 3, your configuration won't be frozen for changes.
44
44
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 (see the previous comments), we'll attempt to migrate your services to Azure Front Door between January 7th and 14th, 2025. We're 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 workloads to Azure Front Door, we'll send you a follow-up email to advise you of the status of the migration, and provide potential actions or 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 don't [set the Feature Flag](../azure-resource-manager/management/preview-features.md)`DoNotForceMigrateEdgioCDNProfiles` before 7 January 2025, Microsoft will migrate existing Azure CDN from Edgio profiles to Azure Front Door Standard profiles. Migration is happening between January 7th and 14th, 2025. These migrations to Azure Front Door are performed 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'll switch the traffic from Edgio platform to Front Door platform.
54
+
- We are not able to roll back the automatic migration.
55
+
- Microsoft can't always maintain feature level parity in the new Front Door configuration.
56
+
- Automatic migration isn't possible for endpoints with `*.vo.msecnd.net` domains.
| December 13, 2024 | No new Azure CDN from Edgio profiles can be created. |
64
+
| January 3, 2025 | No more profile changes are 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 are migrated to Azure Front Door if the said Feature Flag isn't 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. |
46
70
47
71
### Can I retain my existing *.azureedge.net domain when I move to Azure Front Door?
48
72
@@ -58,7 +82,7 @@ You can temporarily retain your *.azureedge.net domain by following the instruct
58
82
59
83
### How does Azure Front Door billing work?
60
84
61
-
Depending on your workloads, Azure Front Door can be more cost-effective than Azure CDN from Edgio. Note that the Azure Front Door billing model differs from Azure CDN from Edgio and includes different billing components. Specifically, Azure Front Door charges a base fee for each profile deployed. Additionally, charges are incurred for requests and data transfer based on usage. See the following for details:
85
+
Depending on your workloads, Azure Front Door can be more cost-effective than Azure CDN from Edgio. The Azure Front Door billing model differs from Azure CDN from Edgio and includes different billing components. Specifically, Azure Front Door charges a base fee for each profile deployed. Additionally, charges are incurred for requests and data transfer based on usage. See the following for details:
62
86
63
87
-[Understand Azure Front Door billing](../frontdoor/billing.md)
@@ -71,33 +95,15 @@ For any questions regarding billing changes, reach out to our support team or yo
71
95
72
96
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.
73
97
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
-
80
-
### What will happen after Microsoft migrates my workloads to Azure Front Door on January 7, 2025?
98
+
### What happens after Microsoft migrates my workloads to Azure Front Door on January 7, 2025?
81
99
82
100
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).
83
101
84
102
If the migration was unsuccessful or if you encounter issues with availability, performance, or feature functionality after a successful migration, contact Microsoft support for assistance.
85
103
86
104
### How is Microsoft communicating the retirement of Azure CDN from Edgio, and how often are reminders sent?
87
105
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.
| 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.
101
107
102
108
### Can I request an extension for the retirement/shutdown of the Azure CDN from Edgio service?
103
109
@@ -109,4 +115,12 @@ No, extensions aren't possible. If you don't want us to automatically migrate yo
109
115
110
116
### Can I set the feature flag at resource/profile level instead of subscription level?
111
117
112
-
No
118
+
No.
119
+
120
+
### Can I be informed regarding the exact date and time when my Edgio profile is automatically migrated?
121
+
122
+
No. We're doing this migration on a "best effort" basis between January 7th and 14th, 2025 for customers who did not take action prior. Therefore we can't inform each customer regarding migration timings, but as noted previously after the migration we'll inform you as to whether it was successful.
123
+
124
+
## Next steps
125
+
126
+
[Set up preview features](../azure-resource-manager/management/preview-features.md)
0 commit comments