When dowloading azure-functions-core-tools@4.14.0, we got some authentication error

Question

When dowloading azure-functions-core-tools@4.14.0, we got some authentication error

Brian 20

User's image

Why this dependancy chalk need to go to Azure "pkgs.dev.azure.com" and need authentication? This break our Azure devops build pipelines... I need to downgrade it to "4.13.0" to work around. Is it a bug or something need to be fixed from your(Azure Function Team) side?

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-27T16:49:43.3133333+00:00

Hi @Brian

Thank you for bringing this issue to our attention.

Our analysis indicates that the authentication error is caused by a dependency reference included in Azure Functions Core Tools 4.14.0. Specifically, the chalk package is being resolved through an Azure Artifacts feed (pkgs.dev.azure.com) instead of the public npm registry. As a result, environments without access to that feed may encounter authentication failures during installation.

Based on our findings, this behavior is related to the packaging of Azure Functions Core Tools 4.14.0 and is not caused by your Azure DevOps pipeline configuration or credentials. The issue originates from the dependency resolution path defined within the 4.14.0 package.

The issue is already being tracked by the Azure Functions team in GitHub issue #5569. [github.com]

Thank you!
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-28T23:26:06.42+00:00

Hi @Brian

I wanted to follow up and check if you had an opportunity to review the details shared regarding the Azure Functions Core Tools 4.14.0 dependency issue.

Please let us know if you have any additional questions or concerns.

Thank you!
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-29T23:58:24.7066667+00:00

Hi @Brian

I just wanted to follow up and check if you had an opportunity to review the details shared regarding the Azure Functions Core Tools 4.14.0 dependency issue.

Thank you!

1 answer

Your answer

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-27T16:49:43.3133333+00:00

Hi @Brian

Thank you for bringing this issue to our attention.

Our analysis indicates that the authentication error is caused by a dependency reference included in Azure Functions Core Tools 4.14.0. Specifically, the chalk package is being resolved through an Azure Artifacts feed (pkgs.dev.azure.com) instead of the public npm registry. As a result, environments without access to that feed may encounter authentication failures during installation.

Based on our findings, this behavior is related to the packaging of Azure Functions Core Tools 4.14.0 and is not caused by your Azure DevOps pipeline configuration or credentials. The issue originates from the dependency resolution path defined within the 4.14.0 package.

The issue is already being tracked by the Azure Functions team in GitHub issue #5569. [github.com]

Thank you!
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-28T23:26:06.42+00:00

Hi @Brian

I wanted to follow up and check if you had an opportunity to review the details shared regarding the Azure Functions Core Tools 4.14.0 dependency issue.

Please let us know if you have any additional questions or concerns.

Thank you!
Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-08-29T23:58:24.7066667+00:00

Hi @Brian

I just wanted to follow up and check if you had an opportunity to review the details shared regarding the Azure Functions Core Tools 4.14.0 dependency issue.

Thank you!

Answer 1

Mohammad Wasi Haider 5

Hi Brian,

This is a known packaging issue with azure-functions-core-tools@4.14.0, not a problem with your pipeline authentication. The package accidentally directs the chalk dependency to an internal Azure Artifacts feed, which causes the 401 error.

The issue is already being tracked by the Azure Functions team in GitHub issue #5569. For now, staying on version 4.13.0 is the safest workaround until a corrected version is released.

Thank you, and feel free to respond back for more assistance.

0 comments