Microsoft Teams integrates chat, video meetings, and file storage within Microsoft 365, providing virtual collaboration and communication for distributed teams
What your AI can do hereConnector snapshot 2026-08-23
Connect Microsoft Teams to ChatGPT or Claude with your own Microsoft Teams login or an API key, and your AI can run 157 of its actions. 67 of those only read and change nothing. 22 can delete or send something that cannot be undone, so those need a boundary you set before anyone runs them.
Microsoft Teams also publishes its own MCP server, which is a second way in. Vendor documentation
This describes what Microsoft Teams supports, which is one half of the picture. Where you
start depends on the task and on how much you have handed over before, and no page can
tell you that from a count.
Things you could hand over
Checked 2026-08-22
Candidates, not recommendations. These are things Microsoft Teams supports once connected.
Whether any of them is right for you depends on your own work, which this page knows
nothing about.
What did I miss in that channel while I was away?No prior practice needed
Your assistant can list the teams and channels you belong to, read the messages in the ones you name, and follow each thread down into its replies, which is where the actual decisions usually sit. It reports back in one piece instead of leaving you to scroll upward for twenty minutes.
What you end up with. A written catch-up on the channels you named, with the threads that carried decisions called out.
Start with it bringing you the information and you deciding.
Never without. Open anything that reads as a decision or a disagreement in the thread itself. A summary flattens tone, and tone is half of what a channel carries.
Built on: List Teams / List team channels / List channel messages / List channel message replies
Someone said it in Teams and I cannot find it. Can it search properly?No prior practice needed
Teams search through the connector takes real query syntax, so an assistant can ask for messages from one person within a date range, or with attachments, across every chat and channel you have access to. It can search the files the same way, then read back the specific message and the replies under it.
What you end up with. The actual message, dated, with the thread around it, instead of a list of near misses.
Start with it bringing you the information and you deciding.
Never without. It searches only what your account can already see, so an empty result means not found in your access, not that it was never said.
Built on: Search Teams messages / Search Teams files / Get Teams channel message / List channel message replies
Turning the meeting transcript into notes I would keepAssumes some practice with AI
Start by handing it the join link from the calendar invite. The meeting lookup here is not a search: Microsoft Graph will only find an online meeting by its join URL or join ID, so the link is how the assistant identifies which meeting you mean. From there it lists the transcripts on that meeting, pulls the raw text, and writes the decisions, the open questions and the actions with owners. The transcript is the evidence, so you can check any line it wrote against what was said.
What you end up with. Draft notes with decisions and owners, each traceable back to a line in the transcript.
Start with it doing the work and checking with you.
Never without. Read the notes before they go anywhere. A transcript records everything said, including the off-hand remark that nobody meant to put in writing.
Built on: List user online meetings / List meeting transcripts / Get meeting transcript content
Who is covering next week, and what is still open?No prior practice needed
For teams running Shifts, the schedule, the assigned shifts, the unclaimed open shifts and the pending time off requests are four separate reads, and an assistant can do all four and put them next to each other. That is the whole question a scheduler asks on a Friday afternoon.
What you end up with. Next week's coverage in one view, with the unfilled shifts and pending requests listed against it.
Start with it bringing you the information and you deciding.
Never without. Check the pending requests against the coverage yourself before you tell anyone they are approved. A request that is still pending is not time off.
Built on: Get schedule / List shifts / List open shifts / List time off requests
Half of next week is uncovered. Building the schedule from hereAssumes some practice with AI
The write side of Shifts is available too. The assistant can read what is already scheduled, create the assigned shifts, publish open shifts for people to claim, adjust an open shift's slot count or times, and enter approved time off so the schedule reflects who is genuinely unavailable. Describe the pattern you want covered and it builds the rows.
What you end up with. Next week's schedule filled in, with the shifts nobody is assigned to published as open for people to claim.
Start with it doing the work and checking with you.
Never without. Read the shift list back before anything is published, and check it against people's approved time off yourself. A published shift is a commitment somebody sees on their phone, and entering time off through this route records it as approved rather than requested.
Built on: Get schedule / List shifts / List open shifts / Create team schedule shift / Update team schedule shift / Create open shifts / Update open shift / Create time off
Setting up the meeting and the group chat for a new piece of workAssumes some practice with AI
It can create the online meeting, create the group chat, look up people by profile so the right accounts are added rather than the right-looking names, and set the chat topic. The connector requires the account it is acting as to be one of the chat members, so you will be in it.
What you end up with. A meeting scheduled and a named group chat created with the right people already in it.
Start with it doing the work and checking with you.
Never without. Check the member list before the chat is created. Adding someone to a group chat gives them everything said in it from that point, and people rarely re-read who is in the room.
Built on: Get User Profile / Create online meeting / Create Chat / Add chat member / Update Chat
A digest of the channels I care about, without reading all of themAssumes you have done this kind of handover before
It searches your messages for the window you name, reads the channels you listed, and posts the digest into a chat with only you in it. Because the digest is the output, you see the result of every run without having to go and check on it. The recurring part is not something Teams does here: whatever schedules your assistant is what makes it happen every morning, and this connector only supplies the read and the one post.
What you end up with. A dated digest sitting in your own chat, covering the channels you chose for the window you asked about.
Start with it doing the work and showing you when it is done.
Never without. Point it at a chat only you are in, and keep it to reading and posting there. A version that replies to people on your behalf is a different task and starts again lower.
Built on: Get User Profile / Get all chats / Search Teams messages / List channel messages / Send message to Teams chat
Someone has left. Can it pull their Teams access?Assumes you have done this kind of handover before
It can list every team the account belongs to, which is the part nobody does thoroughly by hand, and remove them from the ones you name, singly or in a batch. Removal takes away access to that team's channels and its files together, so the listing step is what makes the removal step safe.
What you end up with. A written list of every team the account could reach, and the removals you approved carried out.
Start with it doing the work and checking with you.
Never without. Removal cuts access to a team's channels and files at once, so confirm the directory account rather than matching a display name, and check that no team is left without another owner before you approve the batch.
Built on: List users / List user joined teams / List team members / Remove team member / Remove team members
What we could not establish
Transcript access covers meetings that are backed by a calendar event and that actually produced a transcript. A standalone meeting created through the connector alone returns an error rather than a transcript, so the notes candidate does not apply to every meeting.
Cloning an existing team to stand up a new one is exposed and is not covered by a candidate here. The clone runs asynchronously and returns a location to poll, and how long it takes or what it copies in practice was not established.
Editing and soft-deleting channel messages are exposed and are not covered here, so what a thread looks like once its opening post is removed was not established.
What any of this reaches is decided by your Microsoft 365 tenant settings and your own account's permissions, and that was not checked here. The connector acts as you, so it inherits both.
Nothing in this connector schedules anything. The shift and scheduling actions manage staff rotas, not recurring runs, so any candidate here described as happening every morning depends on whatever schedules your assistant rather than on Teams.
No time saving is claimed for any candidate on this page, because none has been measured.
BUILT-IN AI Some AI exists, but it is narrow, gated to a higher tier, or hard to find.
No event triggers. Every win in this app is invoked: you or an agent asks, an action runs.
Capabilities
READPull records, messages, and content out on demand.
WRITECreate and update records from an instruction.
ADMIN-PROVISIONINGManage users, access, and configuration.
SEND-MESSAGESend messages and notifications on your behalf.
SCHEDULECreate and manage scheduled items.
BULK-OPSRun one instruction across many records at once.