Edgio bankruptcy: Microsoft changes endpoints for .NET, PowerShell scripts and Win32 apps

[German]Small addendum from 27.12.2024. Microsoft was forced to change the download addresses for .NET, PowerShell scripts and Win32 applications at this time. The background to this is the insolvency of Edgio (Limelight Networks).


Advertising

There are two sources that I have come across in this regard. One is the Microsoft Message Center message MC964310, in which Microsoft announced the change of network endpoints for Win32 applications and PowerShell scripts until December 27, 2024.

MC964310

Summary

Update network endpoints for Win32 apps and PowerShell scripts by December 27, 2024, due to Edgio retirement. Ensure access to new CDN endpoints to maintain functionality for Intune deployments. Refer to the provided links for the updated list of CDN endpoints and update firewall rules accordingly.

More information

On December 27, 2024 as a result of the Edgio retirement, we are updating the required CDN endpoints for Win32 apps and PowerShell scripts. Refer to Network requirements for PowerShell scripts and Win32 apps for the updated list of CDN endpoints required for your tenant location.

How this will affect your organization:

If you are using Intune to deploy PowerShell scripts or Win32 apps, you will need to grant access to the updated endpoints for your location. If access to these endpoints is not granted, users will not be able to install Win32 apps and PowerShell scripts will fail.

What you need to do to prepare:

Update your firewall rules to include the new CDN endpoints for Win32 apps and PowerShell scripts: Network requirements for PowerShell scripts and Win32 apps

Note: have corrected "Edgeio" to "Edgio" in the above message, as this is the new name of Limelight Networks. This is the operator of a private global fiber optic network and developer of a cloud-based digital presence management platform that consolidates digital communications. Microsoft used this CDN – but Edgio filed for bankruptcy in the fall of 2o24.

The second source was Dr. Windows and deskmodder.de, which pointed to the blog post Critical: .NET Install links are changing. There, Microsoft announced that the download addresses for .NET installation programs and archives had to be changed unexpectedly.

The background to this is that Microsoft uses several Content Delivery Network (CDN) instances for the provision of .NET builds. Some end with azureedge.net. These domains are hosted by edg.io, which will soon cease operations due to bankruptcy. Microsoft is therefore forced to migrate to a new CDN and will use new domains in the future.


Advertising

The domains affected are:

  • dotnetcli.azureedge.net
  • dotnetbuilds.azureedge.net

New CDNs:

  • Official builds: builds.dotnet.microsoft.com
  • CI builds: ci.dot.net

Not affected:

  • dotnet.microsoft.com
  • download.visualstudio.microsoft.com

Advertising

This entry was posted in Cloud, Software, Update and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Please note the rules for commenting on the blog (first comments and linked posts end up in moderation, I release them every few hours, I rigorously delete SEO posts/SPAM).