Microsoft has introduced that it’s making an “surprising change” to the way in which it distributes .NET installers and archives, requiring builders to replace their manufacturing and DevOps infrastructure.
“We count on that the majority customers is not going to be instantly affected, nevertheless, it is crucial that you simply affirm if you’re affected and monitor for downtime or different disruptions,” Richard Lander, .NET mentioned a program supervisor of the group. A press release final week.
This transfer is a results of the truth that some .NET binaries and installers are hosted on Azure Content material Supply Community (CDN) domains at .azureedge(.)web — dotnetcli.azureedge.web and dotnetbuilds.azureedge.web — ends. Which is hosted on Edgio.
Final month, internet infrastructure and safety firm Akamai acquired choose belongings 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 .azureedge(.)web domains might stop to be obtainable sooner or later, Microsoft mentioned it’s shifting to Azure Entrance Door CDNs. The Home windows maker mentioned it’s going to robotically migrate customers’ workloads by January 7, 2025 if no motion is taken.
Nevertheless, it’s value noting that computerized migration is not going to be attainable for endpoints with *.vo.msecnd.web domains. Clients who plan emigrate to Akamai or one other CDN supplier should additionally set the DoNotForceMigrateEdgioCDNProfiles function flag earlier than January 7, 2025, to forestall computerized migration to the Azure entrance door.
“Be aware that you’ve till January 14, 2025 to finish your migration to a different CDN, however Microsoft once more can’t assure that your companies will likely be obtainable on the Edgio platform earlier than that date,” Microsoft mentioned. Can be.”
“Please be suggested that we’ll be required to dam all configuration modifications to Azure CDN through Edgio profiles from January 3, 2025. Which means that you will be unable to replace your CDN profile configuration, however from Edgio. Your companies on Azure CDN will proceed to operate till you migrate or the Edgio platform is shut down on January 15, 2025 for those who apply DoNotForceMigrateEdgioCDNProfiles flag highlighted earlier than January third, your configuration is not going to be frozen for modifications.”
Though counting on *.azureedge(.)web and *.azurefd(.)web is just not advisable because of availability dangers, prospects have the non permanent choice to migrate to Azure Entrance Door whereas holding the domains. is
“To make sure better flexibility and keep away from a single level of failure, it’s advisable to undertake a customized area as early as attainable,” warns Microsoft.
Moreover, to keep away from safety considerations with a foul actor buying the azureedge(.) web area to distribute malware or poison the software program provide chain, the tech big mentioned it has taken management of it. However as for why the outdated domains could not be used to resolve the brand new servers, it says “this feature was not being made obtainable.”
Customers are suggested to scan their codebase 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
