Skip to content

Commit 42c0435

Browse files
Merge pull request #292791 from Harikrishnan-M-B/patch-24
added common issues
2 parents 783322d + 36a25d2 commit 42c0435

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/cdn/edgio-retirement-faq.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,14 @@ Important notes regarding these "best effort" automatic migrations to Azure Fron
5555
- Microsoft can't always maintain feature level parity in the new Front Door configuration.
5656
- Automatic migration isn't possible for endpoints with `*.vo.msecnd.net` domains.
5757

58+
### What are the most common issues seen with automatic migration and how to mitigate them?
59+
60+
| Issue | Mitigation |
61+
|-------------------|---------------------------------------------------------------------------------------------------------------------------|
62+
| Custom domain couldn't be migrated as domain validation could not be performed due to missing CNAME | [Manually perform domain validation](../frontdoor/standard-premium/how-to-add-custom-domain.md) |
63+
| Customer was using APEX domain | [Use Alias record on Azure DNS to use APEX domain](../frontdoor/front-door-how-to-onboard-apex-domain.md)|
64+
| Customer was using SAS token through rule engine to access their Azure Storage backend which has public access disabled | [Upgrade](../frontdoor/tier-upgrade.md) to Front Door Premium and use [private link](../frontdoor/standard-premium/how-to-enable-private-link-storage-account.md) |
65+
| Customer was using geo-filtering rules which were not migrated | [Configure geo-filtering using WAF](../web-application-firewall/afds/waf-front-door-tutorial-geo-filtering.md)|
5866

5967
### What is the recap of the key dates?
6068

@@ -119,7 +127,7 @@ No.
119127

120128
### Can I be informed regarding the exact date and time when my Edgio profile is automatically migrated?
121129

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.
130+
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 exact migration timings, but as noted previously after the migration we'll inform you as to whether it was successful.
123131

124132
### I am not able to stop my Azure CDN from Edgio anymore. What is happening?
125133

0 commit comments

Comments
 (0)