Microsoft has introduced that it is making an “unexpected change” to the best way .NET installers and archives are distributed, requiring builders to replace their manufacturing and DevOps infrastructure.
“We expect that most users will not be directly affected, however, it is critical that you validate if you are affected and to watch for downtime or other kinds of breakage,” Richard Lander, a program supervisor on the .NET group, mentioned in a press release 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[.]internet — dotnetcli.azureedge.internet and dotnetbuilds.azureedge.internet — that are 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.
Provided that the .azureedge[.]internet domains may stop to grow to be unavailable sooner or later, Microsoft mentioned it is migrating to Azure Entrance Door CDNs. The Home windows maker mentioned it’ll robotically migrate clients’ workloads by January 7, 2025, if no motion is taken.
Nevertheless, it is value noting that automated migration is not going to be attainable for endpoints with *.vo.msecnd.internet 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 stop automated migration to Azure Entrance Door.
“Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date,” Microsoft mentioned.
“Please be advised we will need to halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This means you will not be able to update your CDN profile configuration, but your services on Azure CDN from Edgio will still operate until you are migrated or the Edgio platform is shut down on January 15, 2025. If you apply the DoNotForceMigrateEdgioCDNProfiles feature flag before January 3, your configuration will not be frozen for changes.”
Whereas counting on *.azureedge[.]internet and *.azurefd[.]internet is not really useful because of availability dangers, customers have the momentary choice of migrating to Azure Entrance Door whereas retaining the domains.
“To ensure greater flexibility and avoid a single point of failure, it’s advisable to adopt a custom domain as soon as possible,” Microsoft warns.
Moreover, to keep away from safety issues with a foul actor buying the azureedge[.]internet area for malware distribution or poisoning the software program provide chain, the tech large mentioned 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 mentioned that “this option wasn’t being made available.”
Customers are really useful to scan their codebases for references to azureedge[.]internet and replace them to the next –
- Replace dotnetcli.azureedge.internet to builds.dotnet.microsoft.com
- Replace dotnetcli.blob.core.home windows.internet to builds.dotnet.microsoft.com
