Microsoft is forcing .NET builders to rapidly replace their apps and developer pipelines so they don’t use ‘azureedge.web’ domains to put in .NET elements, because the area will quickly be unavailable as a result of chapter and imminent shutdown of CDN supplier Edgio.
Particularly, the domains “dotnetcli.azureedge.web” and “dotnetbuilds.azureedge.web” can be taken offline within the subsequent few months, which might break the performance of tasks counting on the domains.
This contains builders utilizing .NET installers residing on the affected domains, organizations utilizing GitHub Actions or Azure DevOps with customized pipelines utilizing these domains, Docker and script customers with recordsdata and code referencing the retired domains, and extra.
“We preserve a number of Content material Supply Community (CDN) situations for delivering .NET builds. Some finish inazureedge.web. These domains are hosted by edg.io, which is able to quickly stop operations as a result of chapter. We’re required emigrate to a brand new CDN and can be utilizing new domains going ahead,” explains Microsoft.
“It’s doable that azureedge.web domains may have downtime within the near-term. We count on that these domains can be completely retired within the first few months of 2025.”
Microsoft recommends that probably impacted builders search their code, scripts, and configurations for references to azureedge.web and dotnetcli.blob.core.home windows.web and change them with builds.dotnet.microsoft.com.
Throughout the transition, the brand new domains can be catered by a mixture of Edgio, Akamai, and Azure Entrance Door, as Microsoft works on solidifying the ultimate distribution mannequin with different CDN suppliers.
CI/CD groups want to make sure GitHub Actions (actions/setup-dotnet) and Azure DevOps duties are up to date to variations supporting the brand new domains, whereas updates for Azure DevOps Server are anticipated in early 2025.
Moreover, provided that new CDN domains will now be used, even when configurations are auto-updated, firewalls must be set to permit visitors from the brand new places (builds.dotnet.microsoft.com and ci.dot.web).
The tech large notes that the timing is kind of unlucky, as impacted customers are requested to take motion in the course of the holidays when most IT groups are understaffed.
When requested why Microsoft cannot merely switch the domains and proceed utilizing them, Wealthy Lander, Program Supervisor of .NET at Microsoft, mentioned it was not doable.
“We requested the identical query. We have been instructed that this selection wasn’t being made accessible. We do not have extra data on that,” defined Lander.
The reply is complicated as Microsoft’s Scott Hanselman confirmed that Microsoft already obtained possession of the domains, stating that “no different social gathering will ever have entry to make use of these domains.”
By proudly owning the domains and stopping their reuse, the probabilities of a provide chain compromise for these not migrating their purposes are minimal. Nevertheless, it nonetheless would not clarify the sudden rush emigrate domains and the dangers of operational disruptions.
In case you’re impacted, you may observe the problem extra intently and entry standing updates on this GitHub web page.
BleepingComputer contacted Microsoft with questions on this .NET area migration however has not obtained a reply right now.