MS Teams Integration - Feature Overview

The Microsoft Teams integration connects your organization’s Microsoft Teams environment to 15Five AI. It syncs channel conversations so agents can surface summaries, recurring themes, and alignment signals. Those insights can also be delivered back to you inside Teams.

 

Access and Availability

Role Requirement
15Five Company Admin, HR Admin, or IT Admin Required to initiate the connection
Microsoft Global Administrator or Privileged Role Administrator Required to grant tenant-wide admin consent for data-access permissions

Any user can start the connection, but data-access permissions remain pending until an eligible Microsoft admin approves them.

Note: To ensure the highest level of security, 15Five is continually investing in our overall information security program, resources, and expertise. To review 15Five's security documents, and how we handle your company data, see our Trust Website. 

Feature Structure

The integration is configured from Agents Hub > Integrations > Microsoft Teams.

Key concepts

Microsoft Teams operates on two levels: teams and channels, each with its own privacy settings. The integration's default behavior is designed around this structure.

Teams are the primary spaces within your organization, and a team's privacy setting determines who can join it. There are three types of privacy settings: public (anyone in the organization can join independently), private (joining requires an invitation or approval), and org-wide (everyone is added automatically).

Channels exist within a team and come in three types, determined by visibility.

Channel type Who can see it
Standard Everyone on the team.
Private An invited subset of the team's members.
Shared Invited members only, who can include people from other teams or, if your admin allows it, outside your organization.

A standard channel is open to the whole team, while private and shared channels are restricted to a smaller, invited group. The privacy of a team and the type of channel are not connected. A private team can have standard channels, and a public team can have private channels.

What it enables

  • Gives agents richer, more contextual insights by grounding them in how teams actually communicate across channels.
  • Detects recurring topics, friction points, and shifts in team focus over time.
  • Insights follow Teams permissions. People only see insights from channels they are already a member of.

Access model

  • Standard channels sync automatically once connected.
  • Private and shared channels are opt-in. Individual standard channels and entire teams can also be excluded.
  • You can adjust what's synced or disconnect entirely at any time from Agents Hub > Integrations.

Permissions and access

A few things to know about how 15Five AI works with your Teams content:

Insights are based on Teams permissions. Each person’s experience in 15Five AI matches their access in Microsoft Teams. If someone is part of a team or channel in Teams, they can see related insights in 15Five AI. If they are not part of a team or channel, they cannot see those insights.

You control what’s included. Standard channels are synced automatically. In the integration settings, you can add extra private or shared channels. You can also choose to remove standard channels and whole teams.

You can change what’s included at any time. You can adjust which channels and teams are connected in your 15Five settings or disconnect the integration altogether.

Teams and Channel Types

Microsoft Teams has two levels — teams and channels — each with independent privacy settings.

Level Types Who Can See It
Team Public Anyone in the org can join
Team Private Invited or approved members only
Team Org-wide All org members added automatically
Channel Standard Everyone on the team
Channel Private An invited subset of the team's members
Channel Shared Invited members only; can include people from other teams or outside the org

Team privacy and channel type are independent — a private team can contain standard channels, and a public team can contain private ones.

Sync Scope

Content Default Behavior
Standard channels Synced automatically once connected
Private channels Opt-in only
Shared channels Opt-in only
Individual standard channels Can be excluded
Entire teams (all channels) Can be excluded
Direct messages and group chats Not currently synced

What gets synced

15Five AI syncs content from channels included in the sync, such as:

  • Messages and threaded replies
  • Reactions
  • Channel names and descriptions
  • Member names and email addresses (used to attribute messages and match participants to 15Five accounts)

Configuring what's synced

From the integration's settings in 15Five, you control which channels and teams are included. Four controls shape the sync:

  • Exclude teams — leave out an entire team, along with all of its channels.
  • Exclude standard channels — leave out individual channels that would otherwise sync by default.
  • Include private channels — add private channels to the sync.
  • Include shared channels — add shared channels, including those with cross-team or external participants.

Backfill and Sync Cadence

On first connect, up to one month of history is backfilled per included channel. Backfill typically completes within 24 hours, after which sync continues on an ongoing basis.

Permissions Requested

The following application permissions are granted once at the organization level during setup, before any data is accessed:

Permission Purpose
Channel.ReadBasic.All Discover channels and read their names and descriptions
ChannelMessage.Read.All Read messages from included channels
ChannelMember.Read.All Read channel membership to scope insights correctly
Team.ReadBasic.All Discover the list of teams in the organization
TeamMember.Read.All Read team membership to scope insights correctly
Group.Read.All Identify the Microsoft 365 groups behind teams
Chat.Read.All Reserved for future opt-in chat functionality — no chat content is read or stored today

Key Rules

  • Standard channels sync automatically; private and shared channels require explicit opt-in.
  • Insights follow Teams permissions — users only see insights from channels they are already a member of.
  • Individual standard channels and entire teams can be excluded from sync at any time.
  • Direct messages and group chats are not currently synced, even though chat permissions are requested. No chat content is read or stored today.
  • Tenant-wide admin consent must be granted by an eligible Microsoft admin before any data is accessed.
  • The sync scope can be adjusted at any time from the integration's settings without fully disconnecting.
  • The integration can be disconnected from Agents Hub > Integrations, or revoked from the Microsoft Entra admin center and Teams admin center.

Common Questions

What Microsoft Teams data syncs to 15Five AI?

15Five AI syncs messages, threaded replies, reactions, channel names, channel descriptions, member names, and member email addresses from included Microsoft Teams channels. Member names and email addresses are used to attribute messages and match participants to 15Five accounts.

Do private and shared channels sync to 15Five AI?

Private and shared channels do not sync automatically. Private channels and shared channels sync only when they are explicitly included from the Microsoft Teams integration settings.

Can standard channels or entire teams be excluded from sync?

Yes. Standard channels sync by default, but individual standard channels can be excluded. Entire teams can also be excluded, including all channels inside them.

Are Microsoft Teams direct messages and group chats synced?

No. Direct messages and group chats are not ingested today. The integration requests chat access for future opt-in functionality, but no chat content is read or stored today.

Who can see Microsoft Teams-based insights in 15Five AI?

Users only see insights from Microsoft Teams channels they already belong to. If someone does not belong to a team or channel in Microsoft Teams, they cannot see related insights in 15Five AI.

Related Articles

Was this article helpful?

Sorry to hear that. Tell us what was missing →