You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All Functions assets are now distributed from a new domain - cdn.functions.azure.com - which comes from a new Content Delivery Network (CDN). These changes are a result of the original CDN provider ceasing operations.
If you have any dependencies on the old distribution domains (functionscdn.azureedge.net or functionscdnstaging.azureedge.net), you must update to the new cdn.functions.azure.com. We expect azureedge.net domains to cease by 2025-05-31 (at latest).
Azure Functions team remediation
The Azure Functions team migrated our CDNs to Azure Front Door on 2025-01-14 and retained the existing domain during that migration. We have now created new domains pointing to the same resources:
cdn.functions.azure.com
cdn-staging.functions.azure.com
The new domains are fully endpoint compatible and include all existing paths, files, etc. that were available from the old domains.
The Azure Functions team is ensuring that all references are updated within our products. For this repository, you can track progress via #1622. You can see a full list of these updates as sub-issues of Azure/Azure-Functions#2576.
User Remediation
Direct dependency in user code
Please make the following replacements as soon as practical:
The new domains are endpoint compatible with the old domains; all resources available from the old domains are available through the new domains.
Inaction by 2025-05-31 (at latest) may lead to availability issues.
We do not recommend that customers take any dependency on cdn-staging.functions.azure.com. It is purely for internal use, and its documentation here is for completeness. Instead, please just use cdn.functions.azure.com.
Indirect dependency through product assets
Please also prepare to take updates to product assets as the Azure Functions team replaces in-product references. Release updates will be tracked centrally in Azure/Azure-Functions#2580.
You should plan on updates to:
The Azure Functions Core Tools
Azure Functions Docker images
The Azure Functions extension for Visual Studio Code
Visual Studio
You should also plan on updates to any other tools or assets which may have a dependency on the old domains.
Inaction by 2025-05-31 (at latest) may lead to availability issues.
The text was updated successfully, but these errors were encountered:
Azure
locked and limited conversation to collaborators
Feb 6, 2025
All Functions assets are now distributed from a new domain -
cdn.functions.azure.com
- which comes from a new Content Delivery Network (CDN). These changes are a result of the original CDN provider ceasing operations.If you have any dependencies on the old distribution domains (
functionscdn.azureedge.net
orfunctionscdnstaging.azureedge.net
), you must update to the newcdn.functions.azure.com
. We expectazureedge.net
domains to cease by 2025-05-31 (at latest).Azure Functions team remediation
The Azure Functions team migrated our CDNs to Azure Front Door on 2025-01-14 and retained the existing domain during that migration. We have now created new domains pointing to the same resources:
cdn.functions.azure.com
cdn-staging.functions.azure.com
The new domains are fully endpoint compatible and include all existing paths, files, etc. that were available from the old domains.
The Azure Functions team is ensuring that all references are updated within our products. For this repository, you can track progress via #1622. You can see a full list of these updates as sub-issues of Azure/Azure-Functions#2576.
User Remediation
Direct dependency in user code
Please make the following replacements as soon as practical:
functionscdn.azureedge.net
->cdn.functions.azure.com
functionscdnstaging.azureedge.net
->cdn-staging.functions.azure.com
The new domains are endpoint compatible with the old domains; all resources available from the old domains are available through the new domains.
Inaction by 2025-05-31 (at latest) may lead to availability issues.
We do not recommend that customers take any dependency on
cdn-staging.functions.azure.com
. It is purely for internal use, and its documentation here is for completeness. Instead, please just usecdn.functions.azure.com
.Indirect dependency through product assets
Please also prepare to take updates to product assets as the Azure Functions team replaces in-product references. Release updates will be tracked centrally in Azure/Azure-Functions#2580.
You should plan on updates to:
You should also plan on updates to any other tools or assets which may have a dependency on the old domains.
Inaction by 2025-05-31 (at latest) may lead to availability issues.
The text was updated successfully, but these errors were encountered: