Settings Microsoft Teams

Microsoft Teams

Connect Microsoft Teams to start agent sessions by mentioning @iKanban in a channel, and to get their progress and outcome in the same thread.

Everything happens on Agent settings → Connections, in the Communication card.

What Teams does

  • Start a session from Teams. Post @iKanban fix the failing login test in a channel where the iKanban app is added. iKanban creates an agent session in the team and project you chose, and replies in the thread with its link. To pick another agent, put its name first: @iKanban copilot: add tests for the parser. Claude is the default.
  • It runs on a laptop, not on an API key. The session runs on the laptop of the admin who connected Teams, in their iKanban desktop app, with their own sign-in to the agent. If that app is closed, the reply says Queued and the work starts when it opens.
  • Live progress and the answer in the thread. The bot’s first reply updates as the agent works (steps, time, the last few actions), then the outcome and the agent’s answer arrive as a reply in the thread.

Why you bring your own bot

Microsoft no longer lets one shared bot serve many organisations, so each iKanban workspace registers its own Azure Bot. iKanban never holds anything outside your organisation: the bot, its secret and the Teams app are yours.

You need:

  • to be an admin of the iKanban workspace;
  • a Microsoft 365 account with Teams, in an organisation that allows uploading custom apps (Teams admin center → Teams apps → Setup policies → Upload custom apps; a change can take up to 24 hours);
  • an Azure subscription in the same Microsoft tenant as your Teams. Microsoft requires one for any Teams bot. The Azure Bot Free tier costs nothing for Teams.

Set it up (about 10 minutes)

  1. In iKanban, click Microsoft Teams → Connect and copy the Messaging endpoint.
  2. In portal.azure.com (same work account as Teams): Create a resource → Azure Bot → Create. Pick a bot handle, Pricing tier: Free, Type of App: Single Tenant, Create new Microsoft App ID → Review + create → Create.
  3. Open the bot → Settings → Configuration:
    • Messaging endpoint: paste iKanban’s, exactly → Apply.
    • Copy Microsoft App ID and App Tenant ID.
  4. Manage Password → Certificates & secrets → New client secret → Add. Copy its Value now; Azure shows it once. Note when it expires.
  5. Bot → Settings → Channels → Microsoft Teams → accept → Apply.
  6. Back in iKanban’s dialog: paste the App ID, Tenant ID and the secret’s Value, pick the team and project sessions go to → Connect. iKanban checks the credentials with Microsoft before saving.
  7. Download Teams app in the same dialog. In Teams: Apps → Manage your apps → Upload an app → Upload a custom app → the zip → Add → choose your team.
  8. In a channel of that team: @iKanban reply with a one-line summary of this repository. The reply arrives in the thread.

Prefer an agent to walk you through it? Use the Teams setup prompt, or /ikanban-teams-setup in Claude Code once This laptop is set up.

When it doesn’t work

  • “Microsoft didn’t accept these credentials”: the secret’s ID was pasted instead of its Value, or the App ID and Tenant ID are swapped.
  • No reply in Teams: the messaging endpoint in Azure doesn’t match iKanban’s, the Teams channel isn’t turned on for the bot, or the app isn’t added to that team.
  • It worked, then stopped: the client secret expired. Create a new one and paste it in the dialog; leave the IDs as they are.
  • “Teams isn’t linked to an iKanban team yet”: pick a team and project in the dialog.
  • Private channels: bots can’t post there. Use a standard channel.
  • Updates for sessions started elsewhere: not posted to Teams yet; only sessions started from Teams report back there.