cd.yml reference in use-CICD-template.md 404

[jjhritz89]

Steps to reproduce

at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/use-cicd-template?tabs=certificate, if I copy the cd.yml file as described and deploy it, the npm install step fails because of a 404 error.

Expected behavior

Github actions should publish the agent for me

Actual behavior

Fails to publish.

Error details

Run npm install @microsoft/atk-cli@3.0.4
npm install @microsoft/atk-cli@3.0.4
shell: /usr/bin/bash -e {0}
env:
TEAMSAPP_CLI_VERSION: 3.0.4
AZURE_SERVICE_PRINCIPAL_CLIENT_SECRET: ***
AZURE_SERVICE_PRINCIPAL_CLIENT_ID: ***
AZURE_TENANT_ID: ***
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@microsoft%2fatk-cli - Not found
npm error 404
npm error 404 '@microsoft/atk-cli@3.0.4' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-09-12T18_54_31_431Z-debug-0.log

[m365-agent-toolkit-assistant]

👋 Hi @jjhritz89,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Your error occurs because the npm package @microsoft/atk-cli does not exist in the public npm registry, resulting in a 404. This is confirmed by other users and tracked in GitHub issues. The documentation might reference a deprecated or incorrect package name due to product rebranding (from Teams Toolkit CLI to Microsoft 365 Agents Toolkit).

Workaround:

• Remove or update the npm install @microsoft/atk-cli@3.0.4 step in your cd.yml.
• Instead, use the current CLI tool:

  npm install -g @microsoft/m365agentstoolkit-cli

  and update any references in your workflow to use atk (the new CLI command).

Reference:
See discussion: Missing NPM package

If this doesn’t resolve your CI/CD deployment, please provide your Teams Toolkit version and workflow script for deeper troubleshooting.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

@jjhritz89 - Thanks for bringing this issue to our attention.
An npm E404 error indicates that the runner cannot locate the package or version in your current npm registry. This usually occurs if:

1. The package or version hasn’t been published to the public registry, or
2. The package is hosted in a private feed (such as Azure Artifacts) and your GitHub Action lacks authentication setup.

Could you please verify the below checkpoints?

1. Verify if the package is available on your local or development machine:
   Use: npm view @microsoft/atk-cli versions
   If there’s no result or a 404 error, the package isn’t publicly available.
2. If the package is private or on Azure Artifacts, configure registry authentication in your workflow:
   Include actions/setup-node and set up a ~/.npmrc file with the registry URL and an authentication token (NPM_TOKEN or AZURE_ARTIFACTS_PAT) stored in your GitHub secrets.
3. If the package or version is unavailable, adjust your workflow to use a published CLI (such as npx @microsoft/atk-cli@latest) or set TEAMSAPP_CLI_VERSION to a supported value.

[Nivedipa-MSFT]

@jjhritz89 - Have you verified the above checkpoints?

[jjhritz89]

@jjhritz89 - Have you verified the above checkpoints?

I had to use @microsoft/m365agentstoolkit-cli then the ATK arguments were available. I'm still running into some issues deploying, but at least the tools are available now so I should be good.

Regardless, the documentation needs to be updated.