Skip to content
FidelicRoster →

Setup · Microsoft Teams channels

Wire Teams channels and chats to your Fidelic agent

How the agent listens for @-mentions, posts threaded replies, and uses adaptive cards. Base wiring every other use case depends on.

← Back to Microsoft Teams

Prerequisites

  • · Microsoft Teams admin role to install the Fidelic app (or a per-team owner role for sideload)
  • · Teams policy allowing custom apps in the channels you want the agent in (Teams admin center → Teams apps → Permission policies)
  • · List of channels the agent should join — the agent stays out of channels it has not been added to

Permissions requested

  • · ChannelMessage.Read.All — read channel messages where the agent is mentioned
  • · ChannelMessage.Send — post threaded replies as the agent (no impersonation)
  • · Chat.Read — read direct messages addressed to the agent
  • · Chat.ReadWrite — reply in direct chats
  • · TeamsAppInstallation.ReadWriteForUser — detect when a user adds the agent to a new chat or channel

Step-by-step

1. Install the Fidelic app

From the Teams admin center, install the Fidelic app to your tenant. Either publish to the org-wide app catalog (admin-approved) or sideload via Teams apps → Manage apps → Upload new app for a single team while you evaluate.

2. Set the app permission policy

In Teams admin center → Teams apps → Permission policies, ensure the policy assigned to the relevant users allows the Fidelic app. The default global policy allows custom apps; restrictive policies need an explicit allow rule.

3. Add the agent to channels

@-mention the agent in any channel it should join. The first @-mention adds it to the channel — the agent reads only what it is invited to. To add the agent to a private team's channel, the team owner must invite it.

4. Test threaded reply

Post a question in the channel and @-mention the agent. The agent replies in-thread within a few seconds. The reply uses Teams' standard adaptive cards when the response includes structured data (a candidate list, a deal brief, a meeting recap); otherwise it posts as text.

How to verify it worked

@-mention the agent in a test channel with a simple question. You should see a reply within a few seconds, threaded under your message. The Teams admin center → Manage apps shows the Fidelic app as Active. The Microsoft Entra audit log records the channel and chat scopes under the Fidelic app registration.

Gotchas

Tenants with custom-app blocks. If your global Teams app permission policy is set to Block custom apps, the install fails silently for end-users. Either grant a permission-policy exception for the Fidelic app or assign affected users a policy that allows it.

Private channels and shared channels. Private channels under a team must invite the agent explicitly even if the parent team has the agent installed. Shared channels (cross-tenant) are not supported — use a regular team channel for cross-org work.

For the IT admin

Audit trail. Every channel and chat message the agent reads or writes is logged under the Fidelic app principal in the Microsoft 365 unified audit log. Filter by Workload = MicrosoftTeams and AppId = the Fidelic app's GUID.

Revocation. Removing the agent from a channel cuts off access to that channel; uninstalling the app from the tenant cuts off access tenant-wide. Both reversible without data loss.

Where to next