Microsoft has announced that it is making “unexpected changes” to the way it distributes .NET installers and archives, requiring developers to update their production and DevOps infrastructure.
“We expect that most users will not be directly affected, but it is important that you confirm whether you are affected and monitor for downtime or other types of outages,” said Richard Lander, program manager on the .NET team. said in a statement last week.
This move is a result of some .NET binaries and installers being hosted on Azure Content Delivery Network (CDN) domains ending in .azureedge(.)net — dotnetcli.azureedge.net and dotnetbuilds.azureedge.net — – which are hosted on Edgio.
Last month, web infrastructure and security company Akamai acquired some assets from Edgio after its bankruptcy. As part of this transition, the Edgio platform is scheduled to cease service on January 15, 2025.
Given that .azureedge(.)net domains may no longer be available in the future, Microsoft said is a migration to Azure Front Door CDN. The Windows maker said it will automatically migrate customers’ workloads until January 7, 2025, if no action is taken.
However, it should be noted that automatic migration will not be possible for endpoints with *.vo.msecnd.net domains. Users planning to migrate to Akamai or another CDN provider should also set the DoNotForceMigrateEdgioCDNProfiles flag before January 7, 2025 to prevent automatic migration to Azure Front Door.
“Please note that you will have until January 14, 2025 to complete the migration to another CDN, but again Microsoft cannot guarantee that your services will be available on the Edgio platform before that date,” Microsoft said.
“Please note that we will need to stop all Azure CDN configuration changes using Edgio profiles starting January 3, 2025. This means that you won’t be able to update your CDN profile configuration, but your services on Azure CDN from Edgio will still work. until you transfer or the Edgio platform is terminated on January 15, 2025. If you apply the DoNotForceMigrateEdgioCDNProfiles feature flag before January 3, your configuration will not be frozen for changes.”
While relying on *.azureedge(.)net and *.azurefd(.)net is discouraged due to availability risks, users have a temporary option to migrate to Azure Front Door while keeping their domains.
“To provide greater flexibility and avoid a single point of failure, it is advisable to adopt a custom domain as soon as possible,” warns Microsoft.
Moreover, to avoid security issues related to criminals acquiring the azureedge(.)net domain to spread malware or poison the software supply chain, the tech giant said it took control of it. But why old domain names can’t be used to resolve to new servers, it happens said that “this option was not available”.
Users are advised to scan their codebases for references to azureedge(.)net and update them to the following −
- Update dotnetcli.azureedge.net to builds.dotnet.microsoft.com
- Update dotnetcli.blob.core.windows.net to builds.dotnet.microsoft.com
