Skip to main content
Telara

Integrations / Microsoft Teams

Microsoft Teams logo

Microsoft Teams

Microsoft Teams collaboration platform

OAuth 2.0
Indexes
Actions

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Microsoft 365 tenant with Teams.
A Teams / Entra admin who can consent to the Telara app.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Microsoft Teams. Sign in with an admin that can grant tenant consent.
2
Grant admin consent
If Entra asks for admin consent, that step is required. A member login without consent will not finish.

Permissions Telara requests

  • openid
    OAuth 2.0
  • profile
    OAuth 2.0
  • email
    OAuth 2.0
  • User.Read
    OAuth 2.0
  • User.Read.All
    OAuth 2.0
  • Organization.Read.All
    OAuth 2.0
  • Team.ReadBasic.All
    OAuth 2.0
  • Channel.ReadBasic.All
    OAuth 2.0
  • Chat.ReadBasic
    OAuth 2.0
  • Chat.Read
    OAuth 2.0
  • Chat.ReadWrite
    OAuth 2.0
  • ChannelMessage.Read.All
    OAuth 2.0
  • ChannelMessage.Send
    OAuth 2.0
  • ChannelMember.Read.All
    OAuth 2.0
  • ChannelMember.ReadWrite.All
    OAuth 2.0
  • TeamMember.Read.All
    OAuth 2.0
  • TeamMember.ReadWrite.All
    OAuth 2.0
  • OnlineMeetings.Read
    OAuth 2.0
  • OnlineMeetings.ReadWrite
    OAuth 2.0
  • Calendars.Read
    OAuth 2.0
  • Calendars.ReadWrite
    OAuth 2.0
  • offline_access
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Tenant Id
Bearer token

Pre-issued Microsoft Graph delegated token for benchmark and local indexing harnesses.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Access token
Bearer token

Pre-issued Microsoft Graph delegated token stored under the generic static-token field.

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Token
Multiple fields

Microsoft Bot Framework credentials for Teams bot activities

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for
  • Microsoft App Id
  • Microsoft App Password
  • Tenant Id

Knowledge

What gets indexed

ResourceCoverage
ChannelsExpected to cover the resources this credential can see

Sync

Freshness & sync

ResourceLagDeletions
ChannelsUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Personal Microsoft accounts are not a Teams tenant.
Channel messages Telara never received a consent grant for will not appear, even if you can see them in the Teams client.