Microsoft has introduced that it is making an “sudden change” to the best way .NET installers and archives are distributed, requiring builders to replace their manufacturing and DevOps infrastructure.
“We anticipate that the majority customers is not going to be instantly affected, nevertheless, it’s important that you simply validate in case you are affected and to observe for downtime or other forms of breakage,” Richard Lander, a program supervisor on the .NET staff, stated in an announcement 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) domains that finish in .azureedge[.]web — dotnetcli.azureedge.web and dotnetbuilds.azureedge.web — that are hosted on Edgio.
Final month, internet infrastructure and safety firm Akamai acquired choose property from Edgio following its chapter. As a part of this transition, the Edgio platform is scheduled to finish service on January 15, 2025.
On condition that the .azureedge[.]web domains may stop to develop into unavailable sooner or later, Microsoft stated it is migrating to Azure Entrance Door CDNs. The Home windows maker stated it should routinely migrate prospects’ workloads by January 7, 2025, if no motion is taken.
Nevertheless, it is value noting that computerized migration is not going to be doable for endpoints with *.vo.msecnd.web domains. Customers who plan emigrate to Akamai or one other CDN supplier are additionally required to set the Characteristic Flag DoNotForceMigrateEdgioCDNProfiles earlier than January 7, 2025, in order to forestall computerized migration to Azure Entrance Door.
“Notice you should have till January 14, 2025 to finish your migration to a different CDN, however once more Microsoft can not assure your companies will probably be obtainable on the Edgio platform earlier than this date,” Microsoft stated.
“Please be suggested we might want to halt all configuration modifications to Azure CDN by Edgio profiles beginning on January 3, 2025. This implies you won’t be able to replace your CDN profile configuration, however your companies on Azure CDN from Edgio will nonetheless function till you’re migrated or the Edgio platform is shut down on January 15, 2025. If you happen to apply the DoNotForceMigrateEdgioCDNProfiles characteristic flag earlier than January 3, your configuration is not going to be frozen for modifications.”
Whereas counting on *.azureedge[.]web and *.azurefd[.]web is not beneficial attributable to availability dangers, customers have the non permanent choice of migrating to Azure Entrance Door whereas retaining the domains.
“To make sure better flexibility and keep away from a single level of failure, it is advisable to undertake a customized area as quickly as doable,” Microsoft warns.
Moreover, to keep away from safety issues with a nasty actor buying the azureedge[.]web area for malware distribution or poisoning the software program provide chain, the tech large stated it has taken management of it. However as for why the previous domains couldn’t be used to resolve to the brand new servers, it is being stated that “this feature wasn’t being made obtainable.”
Customers are beneficial 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
