Microsoft has introduced that it is making an “surprising exchange” to the way in which .NET installers and archives are disbursed, requiring builders to replace their manufacturing and DevOps infrastructure.
“We think that almost all customers might not be without delay affected, alternatively, it’s important that you simply validate if you’re affected and to stay up for downtime or different sorts of breakage,” Richard Lander, a program supervisor at the .NET group, mentioned in a commentary final week.
The transfer is the results of the truth that some .NET binaries and installers are hosted on Azure Content material Supply Community (CDN) domain names that result in .azureedge[.]web — dotnetcli.azureedge.web and dotnetbuilds.azureedge.web — which can be hosted on Edgio.
Final month, internet infrastructure and safety corporate Akamai got make a choice property from Edgio following its chapter. As a part of this transition, the Edgio platform is scheduled to finish provider on January 15, 2025.
For the reason that the .azureedge[.]web domain names may just stop to turn into unavailable at some point, Microsoft mentioned it is migrating to Azure Entrance Door CDNs. The Home windows maker mentioned it’ll routinely migrate consumers’ workloads by means of January 7, 2025, if no motion is taken.
Alternatively, it is value noting that computerized migration might not be imaginable for endpoints with *.vo.msecnd.web domain names. Customers who plan emigrate to Akamai or any other CDN supplier also are required to set the Function Flag DoNotForceMigrateEdgioCDNProfiles sooner than January 7, 2025, with the intention to save you computerized migration to Azure Entrance Door.
“Be aware you’ll have till January 14, 2025 to finish your migration to any other CDN, however once more Microsoft can’t ensure your services and products will probably be to be had at the Edgio platform sooner than this date,” Microsoft mentioned.
“Please be recommended we will be able to want to halt all configuration adjustments to Azure CDN by means of Edgio profiles beginning on January 3, 2025. This implies you’ll now not be capable of replace your CDN profile configuration, however your services and products on Azure CDN from Edgio will nonetheless perform till you’re migrated or the Edgio platform is close down on January 15, 2025. Should you follow the DoNotForceMigrateEdgioCDNProfiles characteristic flag sooner than January 3, your configuration might not be frozen for adjustments.”
Whilst depending on *.azureedge[.]web and *.azurefd[.]web is not really helpful because of availability dangers, customers have the transient choice of migrating to Azure Entrance Door whilst protecting the domain names.
“To verify better flexibility and steer clear of a unmarried level of failure, it is recommended to undertake a customized area once imaginable,” Microsoft warns.
Moreover, to steer clear of safety issues with a foul actor obtaining the azureedge[.]web area for malware distribution or poisoning the device provide chain, the tech large mentioned it has taken keep watch over of it. However as for why the previous domains may just now not be used to unravel to the brand new servers, it is being mentioned that “this selection wasn’t being made to be had.”
Customers are really helpful to scan their codebases for references to azureedge[.]web and replace them to the next –
- Replace dotnetcli.azureedge.web to builds.dotnet.microsoft.com
- Replace dotnetcli.blob.core.home windows.web to builds.dotnet.microsoft.com