Microsoft to Migrate NET Builds to New CDN Due to Edgio Shutdown

2024-12-30

: .NET developers, brace yourselves! Microsoft is urging you to update your apps and pipelines as the company prepares to migrate .NET builds away from ‘azureedge.net’ domains.

: Microsoft is discontinuing the use of ‘azureedge.net’ domains for delivering .NET builds due to the impending shutdown of CDN provider Edgio. This move will impact developers using .NET installers, GitHub Actions, Azure DevOps pipelines, Dockerfiles, and scripts that reference the affected domains. The new CDN domains will be builds.dotnet.microsoft.com and ci.dot.net. Developers are advised to update their code, scripts, and configurations accordingly. CI/CD teams will need to update their workflows to use the new domains. Additionally, firewalls will require adjustments to allow traffic from the new locations. The migration is expected to take place in the first few months of 2025. While Microsoft acknowledges the inconvenience caused by the holiday season timing, they assert they were unable to acquire the ‘azureedge.net’ domains. Some community members express confusion regarding the urgency of the migration and the lack of explanation for not acquiring the domains.

What Undercode Says: Microsoft’s decision to migrate .NET builds to a new CDN due to Edgio’s bankruptcy presents a challenge for developers. While Microsoft cannot transfer the ‘azureedge.net’ domains, they have secured ownership to prevent their reuse, minimizing supply chain risks. The urgency of the migration during the holidays and the lack of clarity surrounding the domain acquisition process raise concerns. Here’s a breakdown of the key points and potential implications:

Why

Impact on developers: The migration will necessitate updates to developers’ code, scripts, and configurations. This can be time-consuming and lead to project delays. To minimize disruptions, developers should prioritize updating their projects as soon as possible.

Opportunity for Microsoft: The migration presents an opportunity to enhance the .NET developer experience. The new CDN has the potential to deliver better performance, reliability, and security. To ensure a smooth transition, Microsoft should prioritize clear communication and provide comprehensive documentation to support developers.