azd CDN changing January 2025

[danieljurek]

See issue here: #4661

This issue primarily impacts downloaded versions of installed scripts (which should be updated to the latest by visiting https://aka.ms/install-azd.ps1 and https://aka.ms/install-azd.sh), GitHub Actions users (who need to upgrade to azure/setup-azd@v2), some Azure DevOps instances which need to upgrade to the latest version of setup-azd@0, and custom logic that depends on hostnames.

The CDN endpoint for downloading and installing azd is changing. This is because the Edgeio provider is retiring their CDN service effective January 15, 2025.

Depending on hostnames for azd install is not supported. We recommend using the install scripts or supported installation channels like WinGet, Choco, and brew.

The CDN at azdrelease.azureedge.net and the much older unsupported azure-dev.azureedge.net will be taken offline in the coming days.

Impacted:

• azure/setup-azd GitHub Action
• Older downloaded versions of install-azd.ps1 and install-azd.sh scripts
• Any hardcoded references in your system to the older CDN endpoints
• Firewall rules that enable traffic to the *.azureedge.net CDN hosts

Actions:

• Ensure you are using the latest GitHub Action (v2) for azure/setup-azd in your workflows.
• Ensure you are using the latest Azure DevOps task version.
• Ensure any custom install scripts reference the new host name. File paths after the host name will not change.
• Update any firewall rules which allow traffic to azdrelease.azureedge.net to instead use the new hostname.

Not impact:

• The azd client and Azure Developer CLI VSCode extension are not directly impacted
• WinGet, Choco, brew installers
• GitHub releases
• Normal usage of https://aka.ms/install-azd.ps1
  and https://aka.ms/install-azd.sh scripts. Those have already been updated.