Skip to main content
Telara

Integrations / Microsoft 365

Microsoft 365 logo

Microsoft 365

Microsoft 365 productivity suite via Microsoft Graph — OneDrive, SharePoint sites, and files (delegated OAuth).

OAuth 2.0
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

A Microsoft 365 tenant you can sign into.
A user who can open the sites and files Telara should see, or an admin who can consent for the tenant.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Microsoft 365. Approve access in Microsoft. You do not register an app or paste a client secret.
2
Admin consent when the tenant requires it
If Connect stops at an admin-approval screen, an Entra admin must accept. Re-consent later if this page lists extra Graph permissions you never granted.

Permissions Telara requests

  • offline_access
    OAuth 2.0
  • openid
    OAuth 2.0
  • profile
    OAuth 2.0
  • email
    OAuth 2.0
  • User.Read
    OAuth 2.0
  • Mail.ReadWrite
    OAuth 2.0
  • Mail.Send
    OAuth 2.0
  • Files.ReadWrite.All
    OAuth 2.0
  • Sites.ReadWrite.All
    OAuth 2.0
  • Calendars.Read
    OAuth 2.0
  • Chat.ReadWrite
    OAuth 2.0
  • Tasks.ReadWrite
    OAuth 2.0
  • Notes.ReadWrite.All
    OAuth 2.0
  • Group.Read.All
    OAuth 2.0
  • Team.ReadBasic.All
    OAuth 2.0
  • ChannelMessage.Read.All
    OAuth 2.0
  • Calendars.ReadWrite
    OAuth 2.0
  • Contacts.Read
    OAuth 2.0
  • Contacts.ReadWrite
    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.

Knowledge

What gets indexed

ResourceCoverage
DocumentPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
DocumentUp 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.

Excluded from semantic search: Document.

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 work tenant. That sign-in cannot cover company SharePoint.
Consent granted by a user without access to the sites you care about yields an empty view.