Microsoft Teams
An experimental in-development integration that brings your Microsoft Teams meetings, chats and channel messages into Omniscio through the Microsoft Graph API. Meetings are read-only. Chats and channels can be read and replied to when you press Send, but they are separate optional permissions that need a work or school account and often an IT admin's approval, managed in Settings → Channels → Microsoft Teams.
On this page
What it is
Experimental, in-development integration that pulls your Microsoft Teams online meetings into Omniscio via Microsoft Graph API. Read-only: Omniscio lists, displays, and syncs meetings; it never creates or modifies them in Teams.
Where to find it
Once it is switched on, a Microsoft Teams tab appears in the sidebar and everything happens there: the meeting list, the meeting detail view, the Join Meeting link and the Sync Now button, with the disconnect control in the tab's Settings. Turning it on is a two-step settings job — Settings > Lab to enable Microsoft Teams, then Settings > OneDrive to enter your Microsoft Client ID.
How it behaves
How to turn it on
- Settings > Lab > enable Microsoft Teams (hidden until you flip it because the feature is still in development).
- Settings > OneDrive > enter your Microsoft Client ID (Teams and OneDrive share the same Azure app registration).
- A Microsoft Teams tab appears in the sidebar. Open it and click Connect Microsoft Account.
- A Microsoft consent popup opens. Sign in with a personal or work/school account and grant calendar-read access. (Teams chat is a separate step: see "Teams chat and channels" below.)
- Meetings sync automatically every 15 minutes (configurable in settings).
What you can do
- Browse meetings -- the panel lists synced online meetings grouped by recency (Upcoming, Today, Yesterday, This Week, Earlier), with subject, time range, and organizer.
- View meeting details -- selecting a meeting shows the full detail: subject, date/time, organizer, location, body preview, join URL, and attendee list with response statuses (accepted, declined, tentative).
- Join a meeting -- if the meeting has a join URL, a "Join Meeting" link opens it in the browser.
- Sync on demand -- click "Sync Now" to pull the latest meetings immediately instead of waiting for the next poll.
- Disconnect -- in the Settings tab, disconnect your Microsoft account. This clears all stored credentials and synced meeting data.
Teams chat and channels
Teams chat has its own card in Settings → Channels → Microsoft Teams, next to Slack. It shares one Microsoft sign-in with meetings, so Disconnect there ends both.
- Connect your Microsoft account (if you have not yet).
- Press Allow on the Chats row, and on the Channels row if you want channels. Each is its own permission, so a blocked one never blocks the other, and your meetings keep working either way.
- If your organization needs an IT admin to approve, the card shows an approval link with a Copy link button. Send it to your admin, then press Allow again.
- Open the Chats or Channels tab in the Microsoft Teams panel to read, and write a message and press Send (or Ctrl+Enter) to reply. The box always says who the message goes to.
What to know:
- Work or school accounts only. A personal Microsoft account gets a plain note and only meetings.
- New messages arrive by a check about once a minute, not instantly.
- Nothing is sent unless you press Send. If Teams gives an unclear answer, you are told "it may not have been sent. Check Teams" and nothing is retried for you.
- Your chat text stays on this computer, and the copy is deleted when you disconnect or remove a permission. Copied messages older than 90 days are also deleted on the app's regular cleanup, so mirrored chat never lingers indefinitely.
- Desktop only. Meetings, chats, channels and history import are not served to the paired phone or the web app: those channels are refused over that bridge and answer "only available in the desktop app", because the mirror returns other people's names and message text.
- Every part has its own switch in the same Settings card: Teams chats, Sending, Teams channels, Show Teams messages in my inbox, Alert me about new Teams messages, and Allow importing Teams history.
- Inbox rows and alerts. With the inbox switch on, new Teams messages appear as inbox rows like Slack. Alerts name the sender and the chat, never the message text.
- Import Teams history… copies chosen chats and channels (up to the last year) into the active Team Chat workspace. Teams is only read, never changed, and stopping an import keeps what already arrived.
- Omni can read them too, and only while they are switched on. An Omni session reads the same synced copy through the CLI (
GET /teams/chats,/teams/chats/:id/messages,/teams/channels,/teams/channels/:id/messages). Turning Teams chats or Teams channels off stops that read everywhere, the CLI included, and turning the permission off still deletes the stored text. Omni never sends, replies or marks anything read.
Meeting transcripts for What Next
- A third permission, next to Chats and Channels. The same card in Settings → Channels →
Microsoft Teams has a Meeting transcripts for What Next row. Pressing Allow asks Microsoft
for two more read permissions (
OnlineMeetings.ReadandOnlineMeetingTranscript.Read.All) on top of the ones you already have. An ordinary connect never asks for them, and a personal Microsoft account gets the same plain note as for chat. - Allowing one permission never drops another. Pressing Allow on Chats keeps transcripts on, and the other way round: every sign-in asks again for everything you already allowed, and what is recorded is what Microsoft's answer actually holds.
- When your company needs an IT admin. The card shows one approval link covering every permission still waiting for approval, with Copy link. The admin opens it, signs in with an admin account and approves; you then press Allow again.
- What your IT admin also needs to know. Omniscio signs in with your own Azure app registration
(the Microsoft Client ID in Settings → OneDrive). For work accounts the app registration must accept
"Accounts in any organizational directory and personal Microsoft accounts", and the tenant must allow
Graph access to meeting transcripts. The approval link names the client ID, the permissions and the
loopback redirect
http://127.0.0.1:19520/teams/callback. - What it is used for. Once allowed, the AIPM What Next Investigator's meeting recordings source can read the newest transcript of up to three Teams meetings in its date window, after the person says yes, and keeps only a short excerpt for that answer. Nothing is stored.
- If Microsoft withdraws a permission later, the next token refresh keeps every permission that still works and marks only the refused one as off; the connection itself stays. Only Microsoft refusing (a 400 or 401 from the token endpoint) does that: a refresh that fails for any other reason, such as Microsoft being busy or no network, changes nothing and simply fails that one refresh. Remove on the row turns transcripts off yourself.
Omni reads your Outlook calendar
- Off until you turn it on. The same Microsoft sign-in lets Omni read your Outlook calendar, but only after you turn on Omni can read your Outlook calendar in Settings → Mission Control → What Omni can access. The switch belongs to the Omniscio account that is signed in.
- A personal Microsoft account works. The sign-in asks only for calendar and profile reading, which Microsoft allows for personal accounts, and no Teams licence is involved: the calendar lives in Outlook. Chats and channels still need a work or school account.
- What Omni sees. Each event's title, start and end time, the organizer's name and its link. Never the event notes or who is invited. Omni can only read; it never creates, changes or answers an event.
- When it cannot read. Omni is told why in plain words: the switch is off, nobody is signed in to Omniscio, Microsoft Teams is off in Settings → Lab, no Microsoft account is connected, or the sign-in expired.
Omni reads your Outlook mail
- Off until you turn it on, and the switch is the only thing that asks for mail. Turn on Omni can read your Outlook mail in Settings → Mission Control → What Omni can access. That is the one moment Omniscio asks Microsoft for read-only mail access (Mail.Read): the Microsoft window opens, and the switch turns on only after you approve. Closing the window leaves it off.
- A personal Microsoft account works, with no Teams account. Microsoft lets a personal Outlook.com account approve Mail.Read itself. The mail switch needs a Microsoft account already connected under Settings → Channels → Microsoft Teams → Connect Microsoft Account (that card appears once Microsoft Teams is on in Settings → Lab); if none is, the switch stays off and says where to go.
- What Omni sees. The subject, the sender's name and address, Microsoft's short preview, the received time and a link, for inbox mail. Never the full message, attachments or who else got it. Omni only reads: it never sends, moves, deletes or marks mail.
- Turning it off stops Omniscio asking Microsoft for mail access on its next refresh, once no account on this computer still has the switch on. The Teams chat, channel and transcript permissions are untouched.
- If Microsoft refuses the sign-in because your Microsoft app registration accepts personal accounts only, Omniscio says so and names the fix: set the registration's Supported account types to "Accounts in any organizational directory and personal Microsoft accounts". This applies to every Microsoft sign-in under Teams, the calendar's included.
What it does NOT do (yet)
- Download or stream cloud recordings
- Schedule or create meetings from Omniscio
- Show Teams presence or status indicators
- Receive Teams messages instantly (it checks about once a minute)
- Send or show Teams attachments and images
- Inject meeting context into Claude sessions
- Cross-reference with Google Calendar
Related
The comparable calendar and meeting surfaces are covered on Google Meet and Meetings, and the Microsoft account this integration authenticates against is shared with OneDrive integration. The wider set of Google-side integrations, which this feature deliberately does not cross-reference, is on Google integrations.
Last verified 2026-10-28