Guide
Grok Bot in Microsoft Teams: add a Team Bot to your channels and chats
By Atlas AI Resources · Published November 22, 2026
A Team Bot can live in Microsoft Teams, where your team mentions it in channels, adds it to group chats, or messages it directly. This page starts with our own advice, then summarizes what SpaceXSI’s docs page Use Grok Bot in Microsoft Teams says about setup, linking your account, what the Bot can do there, and the error messages you might see.
1. Our advice: set it up so the right people say yes
Sections 1 and 2 are our own advice, not SpaceXSI’s.
- Line up three people before you start. Setup touches a team admin (to turn Teams on), the Bot’s owner or a Manager (to connect it), and a Microsoft Teams admin (to approve the app). If those are different people, tell them it’s coming.
- Send the approval link yourself. The docs say Microsoft doesn’t notify the Teams admin about a pending Bot. Copy the link from the dialog into a message to them rather than waiting.
- Give the Bot one job. A Bot named for one job tells teammates when to mention it. SpaceXSI’s Team Bots page gives the same tip: give each Team Bot one job and name it for that job. See what is a one-job Grok Bot.
- Treat channel posts as untrusted input. Anyone in a channel the Bot joined can mention it. What they ask is their request, not yours. See keeping AI agents safe from prompt injection.
2. Our advice: check what the Bot carries before it goes in
- Apps and files. SpaceXSI’s Team Bots best practices say to add only the apps, secrets, and files that everyone you share it with may use, and to share an account only when it holds nothing sensitive. In Teams, that audience can be a whole channel.
- A second Manager. The same page suggests adding a second Manager so suggestions don’t wait on one person.
3. Per the docs: what you need first
- A published Team Bot. You must be its owner or a Manager. A Bot that is still a Draft can’t be connected. Team Bots need a Team or Enterprise plan and at least one other person on your team (Team Bots). For sharing in general, see Grok Bot shared Bots.
- Microsoft Teams turned on for your team by a team admin (section 4).
- A Microsoft account in the organization that uses Teams.
- How it behaves. It works the way it does in Slack: it acts for the person who asked, uses their usage, and asks before risky actions.
4. Per the docs: the team admin turns on Microsoft Teams
- Enable. On the Grok Bot page of the team dashboard, under Shared Bots, choose Enable next to Enable Microsoft Teams. Sign in with a Microsoft Teams or Global administrator account and accept the permissions Microsoft shows. Only team admins can enable it.
- After that. The row shows that Microsoft Teams is enabled for your organization, and Bot owners on the team can connect their own Bots. Revoke turns it off. A Microsoft Teams admin still approves each Bot in the Teams admin center.
- Linked accounts. Per Grok Bot for teams and enterprises, Manage Microsoft Teams accounts lists the members who linked a Microsoft Teams account and lets an admin unlink one.
5. Per the docs: connecting a Team Bot
- Start. The owner or a Manager opens the Bot’s details and finds Bring to your team’s Microsoft Teams, or chooses Manage and looks under Channels. Choose Connect Microsoft Teams.
- Sign in. Finish signing in with Microsoft in the browser window that opens. Confirm it’s the right account, and choose an organization if you belong to more than one.
- Admin approval. While the dialog says Waiting on admin approval, a Microsoft Teams admin approves the Bot in the Teams admin center under Teams apps > Manage apps > Pending approval. Send them the link the dialog shows, then choose Check again right after they approve, or Cancel request to stop.
- Finishing. Once it’s approved, Microsoft Teams finishes setting up the Bot on its own, which can take up to an hour. The dialog then says the Bot is in Microsoft Teams, with Open in Teams. To use it in a channel, add it to a team from Microsoft Teams; the dialog lists the teams it’s been added to.
- Declined. If a Teams admin declines the Bot, the dialog shows their note. Make changes and choose Resubmit.
6. Per the docs: linking your own Microsoft account
- First message. The Bot needs to know who you are before it can act for you. The first time you message it, it replies with a Link Account card that only you can see. Choose it and sign in with your Microsoft account.
- Link ahead of time. Open Settings > General > Team Bots and choose Link next to Microsoft Teams account. If it says your admin hasn’t turned on Microsoft Teams yet, ask a team admin to enable it.
7. Per the docs: what the Bot can do in Teams
- Answer in channels and chats. Mention it in a channel of a team it joined, add it to a group chat, or message it directly.
- Read the conversation. It reads the thread it’s in, and the channels of the teams it joined.
- Work with files. It reads files attached to posts and sends you files through your OneDrive. If you ask for a file in a channel or group chat, it asks you to message it directly instead.
- Act for you. It uses your usage and asks you before risky actions. Usage and plan details are in our Grok Bot pricing, usage limits and cost guide.
- Teams calls. Joining and transcribing a Teams call is a separate feature. See Grok Bot in meetings.
8. Per the docs: whose computer, apps, and usage
From SpaceXSI’s Team Bots page:
- Shared memory, private chats. Everyone works with the same Bot, with one set of apps, secrets, skills, and files. Each person’s chat with it is private: the owner and Managers can’t read yours.
- Apps. A Team Bot uses the apps and secrets its owner added. In a shared chat, it uses its owner’s apps and asks before it uses yours.
- Computer and usage in a shared chat. It runs on one shared computer of the Bot’s own, never yours, and uses the usage of the person it’s answering. Only that person answers its approval cards.
- Shared connectors. If a Manager shares one account with the team, anyone who talks to the Bot can act as that account, changes included.
9. Per the docs: updating or removing the Bot
- Name or picture. After you change them, the dialog says so. Choose Update in Teams. If your Teams admin has to approve the change, it shows An update is waiting for your Teams admin.
- Remove it. Remove from Microsoft Teams removes the app from your Microsoft Teams organization. Teammates can’t reach the Bot there until it’s added again.
- Disconnect your Microsoft account. This disconnects it from every Bot you own in that organization, not only this one. Bots already in Teams keep answering there.
- Delete the Bot. Deleting a Bot also removes it from Microsoft Teams.
10. Per the docs: why your Bot isn’t in Teams
- Microsoft Teams isn’t enabled. A team admin needs to choose Enable Microsoft Teams on the team dashboard.
- Publish this Bot to your team first. The Bot is still a draft. Publish, then connect.
- Waiting on admin approval. Send your Teams admin the link in the dialog, then choose Check again.
- Your Teams admin declined. Read their note, make changes, and choose Resubmit.
- Microsoft Teams didn’t accept the app. Your organization doesn’t allow custom apps in Teams. A Teams admin can allow them, or choose Download app package and send it to your Teams admin to upload.
- Blocked by your organization’s Teams app policy. A Microsoft Teams admin needs to allow the app in the Teams admin center.
- Need admin approval. The Microsoft sign-in needs an admin’s consent. Send a Microsoft Teams or Global admin the link the dialog shows, then connect again.
- Microsoft Teams stopped working for your team. The team’s connection expired. A team admin needs to choose Reconnect Microsoft Teams on the dashboard.
- Finishing setup in Microsoft Teams. Teams is still setting up the approved Bot. This can take up to an hour and finishes on its own.
- A Link Account card. Your Microsoft account isn’t linked yet. Choose it and sign in.
If none of these match, the docs say to contact support with the Bot’s name, the exact message, and your Grok Bot version. Our Grok Bot troubleshooting guide covers the general fixes.
Sources
Requirements, the admin switch, connecting and approving a Bot, linking accounts, what it can do, updates, and the error table.
Plans, roles, whose apps, computer, and usage a Team Bot uses, and best practices.
Publishing a Team Bot and the short version of the Teams setup.
The admin switch and Manage Microsoft Teams accounts.
Related: Grok Bot shared Bots · Grok Bot in meetings · Grok Bot for Work · Running multiple teams of Grok Bots · Grok Bot troubleshooting · The standing rules my Grok Bots share