Critical: .NET Install links are changing

What a embarrassing failure on Microsoft's end, in multiple ways. Using a third-party like this (not just as a white-label Azure service, apparently, but for first-party stuff like .NET even), not having a solid migration path or fallback plan, not having proper control over the azureedge.net domain to allow its use to be continued regardless of the backing Edge CDN, the short migration time-line being a complete surprise to them. Everything about this seems like the stuff of amateur companies, not one of the supposedly leading hyperscaler clouds.

2 comments

What a embarrassing failure on Microsoft's end, in multiple ways. Using a third-party like this (not just as a white-label Azure service, apparently, but for first-party stuff like .NET even), not having a solid migration path or fallback plan, not having proper control over the azureedge.net domain to allow its use to be continued regardless of the backing Edge CDN, the short migration time-line being a complete surprise to them. Everything about this seems like the stuff of amateur companies, not one of the supposedly leading hyperscaler clouds.
Less than 3 weeks while people are on vacation... I'm sure this will go smoothly