Ethical Hacking News
Microsoft has announced an update that affects the way .NET installers and archives are distributed. The company is transitioning its CDN services from Edgio to Azure Front Door CDNs, urging users to migrate before January 7, 2025. This change could impact production and DevOps infrastructure, and users are advised to take immediate action to avoid disruptions.
Microsoft is transitioning .NET installers and archives from .azureedge.net to Azure Front Door CDNs. The transition is due to Edgio's acquisition by Akamai and Edgio's planned shutdown on January 15, 2025. Users must take action before January 7, 2025, to avoid automatic migration to the new service. Auto-migration is not possible for endpoints with *.vo.msecnd.net domains. Users are advised to adopt custom domains for greater flexibility and security. Microsoft recommends updating references in codebases from .azureedge.net to builds.dotnet.microsoft.com.
Microsoft, the technology giant renowned for its extensive range of products and services, has recently announced an unexpected change to the way .NET installers and archives are distributed. This shift is aimed at transitioning users to Azure Front Door CDNs, effectively ending the use of .azureedge[.]net domains as a result of Akamai's acquisition of select assets from Edgio following its bankruptcy.
As of now, some .NET binaries and installers are hosted on Azure Content Delivery Network (CDN) domains that end in .azureedge[.]net -- dotnetcli.azureedge.net and dotnetbuilds.azureedge.net -- which are hosted on Edgio. However, with the Edgio platform slated to cease service on January 15, 2025, Microsoft has made it clear that users must take immediate action to avoid disruptions to their services.
In a statement by Richard Lander, a program manager on the .NET team, it was emphasized that most users will not be directly affected by this update. Nevertheless, validation is crucial to determine if changes are necessary and to watch for any downtime or other issues. This change is considered critical as it impacts production and DevOps infrastructure.
The reason behind this transition is attributed to Akamai acquiring select assets from Edgio following its bankruptcy. As part of this acquisition, the Edgio platform will be shutting down on January 15, 2025, prompting Microsoft to migrate users' workloads to Azure Front Door CDNs. Users are required to set a feature flag called DoNotForceMigrateEdgioCDNProfiles before January 7, 2025, so as not to have their services automatically migrated to the new service.
Furthermore, automatic migration will not be possible for endpoints with *.vo.msecnd.net domains. Microsoft has warned users that they must halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This change means users cannot update their CDN profile configurations but can still operate their services on Azure CDN from Edgio until the specified dates.
The tech giant also advises users to adopt custom domains as soon as possible to ensure greater flexibility and avoid a single point of failure. The old .azureedge[.]net domains could pose security risks, particularly with malicious actors acquiring them for malware distribution or compromising the software supply chain.
To facilitate this transition, Microsoft recommends scanning codebases for references to azureedge[.]net and updating them to the following:
- Update dotnetcli.azureedge.net to builds.dotnet.microsoft.com
- Update dotnetcli.blob.core.windows.net to builds.dotnet.microsoft.com
By adopting these changes, users can avoid potential service disruptions and ensure their systems remain secure.
Related Information:
https://thehackernews.com/2025/01/critical-deadline-update-old-net.html
Published: Fri Jan 3 01:48:58 2025 by llama3.2 3B Q4_K_M
