Latest news 4 months ago

Some Microsoft .NET Azure CDN Domains to Cease Operation – Act Now!

Azure CDN domains by Edgio face imminent shutdown. Learn key migration steps to avoid service disruption and secure your operations today.

  • Edgio Shutdown:
    Edgio, a CDN provider for Azure, previously committed to supporting services until November 2025. However, the shutdown has been accelerated to January 15, 2025 due to financial issues.
  • Affected Resources:
    • .NET binaries and installers hosted on Azure CDN domains ending in .azureedge.net domains (managed by Edgio) will need to migrate to new CDN with new domains. These domains may experience downtime or become permanently unavailable.
    • Services like Azure DevOps and GitHub Actions rely on these resources, and work is underway to mitigate impacts.

Microsoft is transitioning these resources to Azure Front Door to ensure continuity. However, in cases of unexpected disruptions, they will update scripts and links to maintain service, albeit with potential issues for users with strict firewall rules.

  • January 3, 2025: Profiles on Edgio CDN will be locked.
  • January 6, 2025: Automatic migration to Azure Front Door will be blocked.
  • January 7, 2025: Microsoft will attempt “best effort” migrations for customers who haven’t migrated, which may cause billing, feature, or performance issues.

Note: Automatic migrations are not possible for domains ending in .vo.mcecnd.net.

Microsoft strongly recommends completing migration away from Edgio before January 7, 2025, to avoid service interruptions. Here are the steps to follow:

  1. Switch References:
    Update any references to .azureedge.net domains with the new domains.
  2. Update Local Scripts:
    Ensure your local copies of install scripts point to the updated CDN domains.
  3. Validate Firewall Rules:
    Confirm your firewall rules are compatible with Akamai and/or Azure Front Door CDNs.
  4. Monitor Updates:
    Keep an eye on the tracking issue: azureedge tracking issue #9674 for further updates.
  5.  Migrate to Azure Front Door:
    Microsoft have provided information regarding their Azure Front Door Azure Front Door | Microsoft Learn and step-by-step instructions for migration: Migrate Azure CDN from Edgio to Azure Front Door

Many organizations face challenges migrating during the first week of January due to change freezes. Early preparation is vital.

Microsoft acknowledges potential service disruptions but is working to minimize impact.

Edgio’s administrative process will liquidate its assets, and customers may need to discuss potential recompense with account managers.

Act now to ensure your services remain uninterrupted!

Other Microsoft recommended reading:

Q1: What has Microsoft announced about Edgio and Azure CDN domains in December 2024

Microsoft announced that Edgio, a key Azure Content Delivery Network (CDN) provider, will cease operations on January 15, 2025, much earlier than its original commitment to operate until November 2025. This unexpected change results from Edgio’s Chapter 11 bankruptcy and subsequent sale of assets. The shutdown impacts several Azure CDN domains, including those ending in .azureedge.net, which host critical .NET binaries and installers on .azureedge.net, a service used by  Azure DevOps and GitHub Actions.


Q2: What caused Edgio to shut down?

In September 2024, Edgio filed for Chapter 11 bankruptcy to facilitate the sale of its assets under new ownership. Akamai acquired selected assets, finalizing the transaction in December 2024. As part of this transition, Microsoft was notified that Edgio’s platform would terminate by January 15, 2025, leaving organizations reliant on its services with a narrow window for migration.


Q3: Which Azure CDN domains are affected?

The affected domains are primarily .azureedge.net, which host critical .NET binaries, installers, and other resources. These domains are integral to services including Azure DevOps and GitHub Actions, which depend on them for installation and functionality. Without migration, these domains could experience downtime or become permanently unavailable​.

Microsoft has emphasized the importance of migrating these resources to new domains, as continued dependency on Edgio services beyond the shutdown date is not feasible.


Q4: What actions is Microsoft taking to mitigate disruptions?

Microsoft is working to migrate resources to its Azure Front Door platform. They are collaborating with internal teams to ensure continuity of service, including updating scripts and links to new URLs if disruptions occur.


Q5: What did Richard Lander, the principal program manager, .NET core at Microsoft, say in his announcement?

“Azure DevOps and GitHub Actions installation tools are dependent on some of the resources (mentioned in Q3). We are working directly with those teams to maintain continuity of service. They are moving to the new domains at best speed.” With this work Microsoft will be hoping that there will be limited impact to services.

Microsoft did add however, “there is a chance that the Edgio CDN services will be terminated before we, our partners, and our users have a chance to adapt to the proposed changes in a staged and safe manner. If that happens, we will change existing scripts and links to use the new URLs and CDN immediately. That approach would maintain service for the bulk of users but might break users with firewall rules.”


Q6: What are the key dates to keep in mind?

January 3, 2025: Profiles on Edgio CDN will be locked.
January 6, 2025: Automatic migration to Azure Front Door will no longer be supported.
January 7, 2025: Microsoft will attempt “best effort” migrations for remaining customers, which may involve significant risks.

Note: Automatic migrations are not possible for domains ending in .vo.mcecnd.net.


Q7: Are there risks of early service termination?

Yes. Microsoft acknowledged that Edgio’s CDN services may end before all users adapt to the proposed changes. In such a scenario, existing scripts and links will be updated immediately to maintain service for most users. However, this approach may cause issues for users with strict firewall configuration.


Q8: What immediate actions should organizations take to minimize disruptions?

Microsoft recommends taking the following immediate actions:
1. Update References: Replace any .azureedge.net domain references with the new domains.
2. Update Local Scripts: Ensure all local scripts point to updated CDN domains.
3. Validate Firewall Rules: Verify that your firewall rules are compatible with Akamai and Azure Front Door CDNs.
4. Monitor Updates: Keep track of Microsoft’s updates via the azureedge tracking issue #9674.
5. Migrate to Azure Front Door: Use Microsoft’s step-by-step migration instructions:
Azure Front Door Overview
Migrate Azure CDN from Edgio to Azure Front Door


Q9: What challenges might businesses face during this transition?

1. January Change Freezes: Many organizations enforce change freezes during the first week of January, complicating efforts to migrate.
2. Technical Adjustments: Updates to firewall rules, scripts, and domain configurations may require significant IT resources.
3. Limited Support for Late Migrations: Microsoft’s “best effort” migration approach may cause billing, feature, and performance discrepancies​.


Q10: What happens if businesses fail to migrate by January 7, 2025?

Microsoft will attempt to migrate remaining services to Azure Front Door on a “best effort” basis. This process could result in:
Billing discrepancies.
Feature and performance limitations.
Businesses using .vo.mcecnd.net domains will not be automatically migrated​


Q11: What is happening to Edgio as a company?

Edgio will undergo an administrative liquidation process to sell its remaining assets. Customers should discuss with their account managers to understand if and when they may receive any compensation.


Q12: How does this impact ITAA’s role in supporting clients?

While ITAA cannot provide direct support for this specific migration, we offer:
Vendor management expertise: Helping businesses navigate vendor transitions effectively.
IT procurement strategies: Ensuring optimized contracts and service arrangements.
Microsoft licensing knowledge: Addressing challenges similar to the Edgio shutdown and mitigating risks in future scenarios.
To ensure we can help businesses navigate similar challenges in the future.
ITAA is a trusted partner for organizations seeking to strengthen their IT strategies, navigate complex technology landscapes and prepare organization for unforeseen technology transitions.

The Edgio shutdown highlights the importance of proactive IT management and vendor preparedness. While this specific situation may not allow for immediate external support, organizations can partner with ITAA to develop strategies for future challenges, ensuring resilience and continuity.

GDPR Data*
This field is for validation purposes and should be left unchanged.

Find out how we can help

Please fill out the form and we’ll be in touch.

This field is for validation purposes and should be left unchanged.
Talk to us today