Microsoft has revealed significant changes to its .NET installers and archives distribution system, requiring developers to update their production and DevOps infrastructure. The modification stems from the hosting of .NET binaries and installers on Azure CDN domains (dotnetcli.azureedge.net and dotnetbuilds.azureedge.net) currently managed by Edgio.

Following Akamai’s acquisition of Edgio’s assets amid bankruptcy, the Edgio platform will cease operations on January 15, 2025. In response, Microsoft is transitioning to Azure Front Door CDNs, with automatic migration scheduled for January 7, 2025.

Key Points:
– Automatic migration won’t apply to *.vo.msecnd.net domains
– Users planning to migrate to alternative CDN providers must set the DoNotForceMigrateEdgioCDNProfiles feature flag before January 7, 2025
– Configuration changes to Azure CDN by Edgio profiles will halt on January 3, 2025
– Microsoft has secured control of the azureedge.net domain to prevent security risks

Required Domain Updates:
– Replace dotnetcli.azureedge.net with builds.dotnet.microsoft.com
– Replace dotnetcli.blob.core.windows.net with builds.dotnet.microsoft.com

Microsoft recommends implementing custom domains to ensure greater flexibility and avoid single points of failure. While temporary migration to Azure Front Door with existing domains is possible, it’s not recommended due to availability risks.