Grok Bot Microsoft Teams support works two ways. A Bot can use Microsoft Teams as a connected app, so it can read Teams messages for a task. And a team's shared Bot can join Microsoft Teams itself, so teammates chat with it or @mention it in a channel and it replies in the same conversation. The second way needs three people to act: a team admin, a Microsoft Teams admin and each teammate.
📺 Watch: Grok Bot Just Took AI Agents to Another Level!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
This page covers both routes using xAI's docs, then walks through the shared Bot setup step by step, including the approval step that trips most teams up.
Grok Bot Microsoft Teams: the two ways it works
These two routes are easy to confuse, so start here.
Route A: Microsoft Teams as a connected app. This is a personal connection. You add Microsoft Teams under Connect apps, sign in with Microsoft, and your Bot can work with your Teams messages. xAI's security docs list Microsoft Teams alongside Outlook, Outlook Calendar and OneDrive, all talking to graph.microsoft.com. The xAI changelog adds two details: since 12 August a routine can start from a Microsoft Teams message, and since 3 November links pasted from Teams keep their address.
Route B: a shared Bot joins Microsoft Teams. This is a team feature. The docs say it "lets the team's shared Bots join Microsoft Teams." The Bot shows up inside Teams. Teammates chat with it directly or mention it in a channel of a team it joined, and it replies in the same conversation.
| Question | Route A: connected app | Route B: shared Bot in Teams |
|---|---|---|
| Who uses it | You, through your own Bot in Grok Bot | Teammates, from inside Microsoft Teams |
| Where you talk to the Bot | The Grok Bot app | Teams chats and channels the Bot joined |
| Who sets it up | You, under Connect apps | Team admin, Bot owner or Manager, Teams admin, each teammate |
| Admin approval in Teams | Not part of these steps | Yes, in the Teams admin center for each Bot |
| Plan | Not stated in the docs | A team plan with Shared Bots |
If you are working out how AI fits into how your team already talks, the AI Profit Boardroom is where Julian Goldie shares the systems and templates he uses, with weekly updates. You can also book a free AI strategy session to plan it with the team.
Route A: connect Microsoft Teams as an app
The docs describe the same flow for every connected app:
- Open Connect apps from the sidebar, or follow an in-chat Connect card. On the phone, tap your avatar on the top left and choose Connect apps.
- Search for Microsoft Teams and add it.
- When Grok Bot asks you to Authorize or Authenticate, finish the Microsoft sign-in in your browser.
- Check the app shows under Installed.
In chat, type @ to attach the app to a task. You can also just ask a Bot to add the app, and it shows a Connect card when you need to sign in.
The docs say app connections belong to the same account you used to sign in to Grok Bot. If your team uses a network allowlist, a team admin needs to add graph.microsoft.com, or the connector is refused.
For the bigger picture on apps, see Grok Bot connectors. For starting work from a Teams message, see Grok Bot routines.
📺 Watch: Grok Bot Just Turned AI Agents Into Real Teammates
Route B: put a shared Bot in Microsoft Teams
This is the route most teams mean when they search for grok bot microsoft teams. It has four stages.
Step 1: a team admin enables Microsoft Teams
On the Grok Bot page of the dashboard, under Shared Bots, a team admin chooses Enable next to Enable Microsoft Teams. They sign in with a Microsoft Teams or Global administrator account. The row then shows Microsoft Teams enabled for your organization. Revoke turns it off.
The docs say only team admins can enable it. The 6 November changelog notes that if the admin sign-in fails, the page now shows Microsoft's error with Try again and Back to dashboard.
Step 2: the Bot's owner or a Manager connects it
The Bot has to be shared first. Then its 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.
- Chooses Connect.
- Finishes signing in with Microsoft in the browser window that opens.
- Chooses the teams the Bot should join.
Step 3: a Microsoft Teams admin approves the Bot
This is the step that stalls. While the dialog says Waiting on admin approval, a Microsoft Teams admin needs to approve the Bot in the Teams admin center, under Teams apps, then Manage apps, then Pending approval.
The docs put it plainly: "Microsoft doesn't notify them, so send them the link the dialog shows." If nobody sends that link, the Bot just waits. Setup finishes by itself once they approve. Choose Check again to check right away, or Cancel request to stop.
A team admin enabling Teams in step 1 does not replace this. The docs say a Microsoft Teams admin still approves each Bot.
Three messages you might see, and what they mean:
- Microsoft Teams didn't accept the app. Your organization may not allow custom apps in Teams. A Teams admin can allow them, and the dialog offers Download app package for the admin.
- Not connected · Blocked by your organization's Teams app policy. A Teams admin needs to allow the app in the Teams admin center.
- Declined. If the admin declines the Bot, choose Resubmit.
Step 4: each teammate links their account
Every teammate who wants to use the Bot links their Microsoft Teams account. They open Settings, then General, then Shared Bots, and choose Link next to Microsoft Teams account. Team admins can see who has linked under Manage Microsoft Teams accounts.
Once that is done, teammates chat with the Bot or mention it in a channel of a team it joined, and it replies in the same conversation.
📺 Watch: Grok Bot just got 10X better
Changing the Bot later
If you rename the Bot or change its avatar, choose Update in Teams. Updates also wait for a Teams admin and show "An update is waiting for your Teams admin" until they approve. So send the admin a note each time.
The 3 November changelog fixed one annoyance: removing and reconnecting a Bot no longer leaves a duplicate in Teams search.
What the docs don't say is just as useful. They describe chats and channel mentions. They don't describe the Bot joining Teams meetings or calls, so plan around chat and channels.
Plans and where the Bot runs
Shared Bots and the Microsoft Teams channel are team features. On a team plan, Grok Bot is on by default for every member. On Enterprise, an admin turns it on from the dashboard. Individuals get access through a paid Cursor plan, a linked SuperGrok account or a Grok Business seat, but a personal account on its own cannot put a Bot into Teams.
Grok Bot runs on cloud computers hosted by Cursor. You sign in with your Cursor account, and Grok Business seats can use Sign in with Grok. All of a user's Bots share one cloud computer, with their own screen each. Those Bots share its files, browser sessions and logins, so they can hand work off to each other.
For shared Bots and team roles in general, read Grok Bot for teams. If part of your company lives in Slack, the Grok Bot Slack guide covers that channel, which needs a Slack workspace admin's approval in the same way.
Julian Goldie's team documents its whole AI setup in the Agent OS guide, and the Goldie Bench compares AI tools on real tasks. If you want help choosing where a shared Bot fits, book a free AI strategy session.
Quick setup checklist
- Team admin: Shared Bots, Enable Microsoft Teams, sign in with a Teams or Global administrator account.
- Bot owner or Manager: share the Bot, then Bring to your team's Microsoft Teams, Connect, pick teams.
- Send the approval link to your Microsoft Teams admin.
- Teams admin: Teams admin center, Teams apps, Manage apps, Pending approval.
- Each teammate: Settings, General, Shared Bots, Link next to Microsoft Teams account.
The xAI changelog for 16 September added a Slack or Microsoft Teams step to the setup checklist inside Grok Bot, so the dashboard prompts you as well.
FAQ
Does Grok Bot work in Microsoft Teams without admin approval?
No. A team admin enables Microsoft Teams in the Grok Bot dashboard, and a Microsoft Teams admin approves each Bot in the Teams admin center. Microsoft doesn't notify the Teams admin, so send them the link.
Can a Grok Bot join Teams meetings?
xAI's docs describe chats and channel mentions only. Teammates chat with the shared Bot or @mention it in a channel, and it replies in the same conversation.
Can I add a Bot to Teams on a personal account?
The Teams channel is part of Shared Bots, which is a team feature. On a personal account you can still connect Microsoft Teams as an app for your own Bot.
Why is my Bot stuck on "Waiting on admin approval"?
Microsoft doesn't send the Teams admin a notification. Send them the link the dialog shows. Once they approve under Pending approval, setup finishes by itself, or choose Check again.
To get the playbooks Julian Goldie uses to roll AI out across a team, join the AI Profit Boardroom. Or book a free AI strategy session and plan your grok bot microsoft teams rollout with us.
