Update Old .NET Domains Before January 7, 2025

Microsoft is making “unexpected changes” to the way it distributes .NET installers and archives. This shift means developers globally must update both their production infrastructure and DevOps setup to avoid disruptions.

Program manager Richard Lander, on Microsoft’s .NET team, emphasizes: “We expect that most users will not be directly affected, however, it is critical that you validate if you are affected and to watch for downtime or other kinds of breakage,” noting potential issues are likely. See his statement:
.

Here’s What Happened: .NET’s .NET installers and other binaries are partly hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge[.]net, managed by Edgio.
Earlier this year, Akamai, a web security firm, bought parts of Edgio, leaving .azureedge[.]net domains and Edgio at risk.
With a scheduled shutdown for January 15, 2025, Microsoft decided a move was urgently needed.

Microsoft’s Resolution:

Microsoft is transferring its CDN setup from Edgio to Azure Front Door. Customers on the current system will get migrated automatically—if they haven’t customized it—before January 7, 2025.

However: Users relying on *.vo.msecnd.net domains in their .NET projects aren’t automatically part of the shift. Those desiring a different provider than Azure Front Door also need to activate a “Feature Flag” , preventing the change.
Further information from Microsoft here.

• .NET advises stopping configuration updates

.NET recommends reviewing and updating these domain references,

.NET urges its users to quickly migrate to Azure Front Door

It is advised. Due to Edgio’s impending closure.

Microsoft stressed the use of *.azureedge[.]net is temporary

The move could cause disruption
It also underscores the significance of robust risk mitigation strategies