[saiprasadpotdar]

Updates the Microsoft Teams page for Teams changes merged to the product since it was rewritten.

• Setup: Nubi is added first, then the tenant is connected either from the welcome card's Connect Microsoft Teams button or from Admin → Integrations with Microsoft sign-in. The button needs no Microsoft sign-in. It works only for the person who added Nubi, signed in to NudgeBee as an admin, for 7 days.
• Using Nubi in Teams:
  • an alert's thread always uses the alert's account;
  • each thread message runs with its writer's access;
  • an approval is recorded as the person who clicked;
  • Nubi can post a message you approve to a channel;
  • what Ask Nubi says when an analysis can't run (failed, budget used up, alert gone, busy, on hold, still running).
• Picker: the default channel is listed as "General (default channel)".
• On-prem: MS_TEAMS_ACTION_SIGNING_KEY also enables the card's Connect button.
• Troubleshooting: the Connect button's messages, and why a card can have no button.

Merge timing: the Connect button, the Ask Nubi replies and the default-channel label are on the product's main branch but not yet released to production. Merge this once they are, or the page describes buttons users don't see yet.

Check it: cd doc-server && npm run build succeeds. The new in-page links (#from-nudgebee-with-microsoft-sign-in, budgets-and-limits#when-a-limit-is-reached) resolve to real headings in the build output.

[gemini-code-assist]

Code Review

This pull request updates the Microsoft Teams integration documentation to reflect changes in the setup flow, specifically introducing a new connection method via Nubi's welcome card that does not require a Microsoft sign-in. It also expands the sections on using Nubi in Teams (covering thread sharing, analysis failures, and workflow approvals) and updates the troubleshooting guide. Feedback is provided to clarify that both listed conditions must be met for the welcome card's connect button to work, resolving potential ambiguity in the bulleted list.