Repository navigation
[Bot validation] TeamsJS and TeamsFx distinction (2026-09-28) #78
Description
Activity
👋 Hi @Alive-Fish,
Thank you for reporting this issue. Here is an AI-generated initial response:
Classification: Not a bug — the assumption conflates TeamsFx with TeamsJS; replacing your tab’s TeamsJS calls with the Microsoft 365 Agents SDK is not required.
- Microsoft’s TeamsJS guidance still recommends TeamsJS for hosted tabs and documents
app.initialize()andapp.getContext(). Its TeamsFx deprecation notice applies to TeamsFx, not TeamsJS. - Tab SSO guidance continues to document
authentication.getAuthToken(). The Agents SDK is a framework for conversational agents, not a replacement for those tab-host APIs.
What to do now:
- Keep
@microsoft/teams-jsfor the tab; do not migrate these calls solely because of the TeamsFx notice. - If token acquisition fails, check the tab’s SSO configuration and capture the exact error and host/client details.
Useful links:
- No sufficiently relevant related issue found in the searched repos.
- Teams JavaScript client library
- Add code to enable tab SSO
Note: AI-generated guidance may be incomplete or incorrect. Please verify suggestions before applying them.
- Microsoft’s TeamsJS guidance still recommends TeamsJS for hosted tabs and documents
Validation Context
Controlled end-to-end validation requested by the repository owner. This is a synthetic scenario, not a confirmed product defect. Please keep this issue identifiable as a validation artifact rather than citing it as evidence for unrelated issues.
Scenario and Question
Our Teams tab uses @microsoft/teams-js 2.57.0 for app.initialize(), app.getContext() and authentication.getAuthToken(). We do not use TeamsFx. After reading a TeamsFx deprecation notice, we assumed TeamsJS was retired too and tried to replace these client calls with the M365 Agents SDK, but could not find equivalent tab APIs. Is that assumption correct, and is that replacement required?