Skip to main content
Microsoft Teams lets the assistant sit in the team like a teammate. Someone @mentions it in a channel or a chat, and the answer stays there. The thread is also in History.

​
When to use it

Use it when the work already happens in Teams: an internal question, a shared channel with a customer, or a place where people expect to @mention a helper. Connecting an assistant gives that mention the assistant’s instructions and tools.

​
What the assistant hears

The assistant hears @mentions in channels and chats that reach the bot. Add to Teams installs the shared app. A manual Azure Bot receives what you point at the Famulor messaging endpoint.

​
Where the keys come from

The linked provider guide shows the screens for these clicks. Follow the clicks below together with those pictures. Add to Teams asks an admin to consent. It does not ask you to copy an app password. A manual bot is an Azure Bot in the Azure portal. Copy the Microsoft App ID. Create a client secret under Certificates & secrets and copy the value once; that value is the App password / client secret. If the bot is single-tenant, also copy the directory tenant ID. Official guide: Azure Bot Service.

​
Create it at the provider

Skip this section if you use Add to Teams.
  1. In the Azure portal, create an Azure Bot.
  2. Copy the Microsoft App ID.
  3. Open Certificates & secrets, create a client secret, and copy the secret value immediately.
  4. If this bot is single-tenant, copy the Directory (tenant) ID. Leave it empty for a multi-tenant bot. Famulor treats a filled-in tenant ID as single-tenant.
  5. Turn on the Microsoft Teams channel on the bot.
  6. After the Famulor connection exists, set the bot’s Messaging endpoint to the Famulor webhook URL.

​
Connect it in Famulor

Your plan includes this channel. Open Settings → Channels, choose the card, name the connection, pick an assistant and save. The shared conversation settings — response delay (default 5 seconds) and inactivity timeout (default 30 minutes) — are described on the messaging channels page. Add to Teams is available on the Famulor platform domain, for a root workspace. An admin consents, and the connection menu then offers Download app package. Install that package in Teams so people can @mention the assistant. On a whitelabel domain, choose Show manual credentials and paste Microsoft App ID, App password / client secret, and optionally Azure AD tenant ID (optional, SingleTenant).

​
Point the provider at Famulor

After Add to Teams, install the downloaded app package in Teams. There is no messaging endpoint to paste for that path. For a manual bot, copy the Famulor webhook URL from the connection menu and paste it into the Azure Bot Messaging endpoint. Confirm the Teams channel is on. An @mention then appears in History.

​
History

Open History and filter by Microsoft Teams. The thread, the assistant reply and any analysis appear there. You can pause the assistant and answer manually.

​
API, MCP and command line

Create this connection in the dashboard. The public API and the command line cannot pass every value this card asks for, so they cannot finish this setup. The manual card needs the app password, and a public create call does not accept that value.