-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azureedge.net CDN (where Edge WebDriver installs are located) will cease operations by 15th January 2025 #183
Comments
Thanks for taking this issue forward @captainbrosset |
As discussed with @leotlee internally, it seems like the azureedge.net endpoint will continue to work as is even after the edge.io provided stops working. |
Why will the azureedge.net endpoint continue to work for the Edge Web Driver downloads? All the other MS stuff I have looked at (azcopy and dotnet) seem to indicate that azureedge.net is not a good option once Jan 15th hits. The build5nines.com article listed above also indicates that not updating contains risks. Just trying to understand. Thank you! |
@captainbrosset , @leotlee |
Confirming here the azureedge.net CDN servicing of Edge will continue to work, I'm closing this issue. The Azure CDN azureedget.net is not going away. Edgio is one of the CDN provider behind it that is going away on Jan 15th. We are not using Edgio as the CDN provider; we are using Microsoft CDN (classic) provider instead. We're already tracking the 2027 sunset date for that. More info here. |
Originally posted by @Delta456 at MicrosoftDocs/edge-developer#3335:
The text was updated successfully, but these errors were encountered: