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!