Microsoft has issued an urgent warning to .NET developers regarding the imminent shutdown of two critical domains used for installing .NET components: dotnetcli.azureedge.net and dotnetbuilds.azureedge.net. This action is prompted by the bankruptcy of Edgio, the Content Delivery Network (CDN) provider that hosts these domains. As a result, developers are advised to update their applications and pipelines to avoid potential disruptions.
Background on the shutdown
The affected domains are set to go offline in the coming months, which poses a significant risk for projects that rely on them. Microsoft has stated that these domains will likely be permanently retired in early 2025. The company emphasized that any applications or services still referencing these domains could experience functionality issues, particularly those using GitHub Actions, Azure DevOps, Docker, or custom scripts.
Recommended actions for developers
To mitigate disruptions, Microsoft recommends that developers take immediate action by:
- Searching code and configurations: developers should check their codebases for any references to the outdated domains and replace them with the new domain: builds.dotnet.microsoft.com.
- Updating CI/CD pipelines: it is crucial for Continuous Integration/Continuous Deployment (CI/CD) teams to ensure that their GitHub Actions (specifically
actions/setup-dotnet) and Azure DevOps tasks are updated to versions that support the new domains. - Adjusting firewall settings: as new CDN domains will be introduced, firewall configurations must be updated to allow traffic from builds.dotnet.microsoft.com and ci.dot.net.
Transition period challenges
The timing of this transition is notably challenging, as it falls during the holiday season when many IT teams are operating with reduced staff. Microsoft acknowledged this inconvenience but stressed the necessity of migrating away from the affected domains. Rich Lander, Program Manager for .NET at Microsoft, explained that transferring ownership of the domains was not an option provided by Edgio, despite Microsoft’s ownership of them now preventing future misuse.
Monitoring updates
For developers affected by this change, Microsoft encourages following updates on a dedicated GitHub page where they can track the status of this migration and any further developments.In summary, .NET developers must act swiftly to update their applications and configurations in light of these changes. Failure to do so could lead to significant operational disruptions as the shutdown date approaches.