Integration · Microsoft Teams
Connect Microsoft Teams to meinGPT
Read Teams chats in the signed-in Microsoft user's context and turn selected conversations or transcripts into summaries, actions, and reply drafts.
The native Microsoft Teams connection reads chats, messages, and participants in the signed-in user's context. Selected chat history, transcripts, or meeting notes can be summarised and turned into actions or reply drafts. The connector is read-only and does not post messages or read channel conversations.
A person connects their Microsoft work or school account through OAuth. The assistant can list their accessible chats and read selected messages and participants. Meeting transcripts are available only when Microsoft and tenant settings provide them or when the transcript is supplied. Draft content remains in meinGPT for a person to review and post.
- Source
- Microsoft Teams
- Capability
- List chats, read messages and participants, and process selected transcripts or notes
- Connection
- Delegated Microsoft OAuth through the native Microsoft 365 connector
- Data residency
- Teams content is read only for the current task and remains limited by the connected user's Microsoft permissions.
Source, permissions, and data residency are documented separately for each connector.
Typical workflows
- Summarise a long chat
- Extract meeting actions
- Prepare a Teams reply
What the integration makes possible
01
Summarise a long chat
Turn a selected chat into key statements, decisions, open questions, and actions without posting anything back.
02
Extract meeting actions
Use a supplied transcript or meeting note to identify actions, owners, and dates for review.
03
Prepare a Teams reply
Draft a clear response or channel update that a person can check and paste into Teams.
Clarify before starting
- 01The relevant Teams chats or transcript sources are known.
- 02Delegated Microsoft Graph permissions are approved.
- 03A person is responsible for reviewing and posting drafts.
Review the prompt and result openly
Summarise the selected Teams chat about the Q3 rollout. List decisions, open questions, and actions with owners and dates where stated.
Result
The result separates three decisions, four actions, and two unresolved questions. It was generated read-only and no Teams message was posted.
Does this connection fit your use case?
We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.
Security and operations
Use delegated Microsoft permissions and expose only the chats required for the intended assistant. Keep posting with a person, because the connector itself is read-only.
Known limitations
- 01The connector reads chats, not channel conversations, and does not post messages.
- 02It cannot access content the connected Microsoft user cannot see.
- 03Meeting transcript availability depends on Microsoft and tenant configuration.
Frequently asked questions
No. The native connector is read-only. It prepares content that a person reviews and posts.