Grok Bot Microsoft Teams earns a 6.6 out of 10 from me: a well-documented way to put a team's shared Bot in Teams chats and channels, held back by a two-admin approval chain and thin Teams-specific docs.
Every rating below is my editorial judgement from xAI's shared Bots page, the admin guide's Microsoft Teams section and the Grok Bot changelog.
No benchmark was run; the scores read the docs as written on 11 November 2026.
Weighing Bots for your own firm? Book a free SEO strategy session with my team.
The verdict in one paragraph
Pick it if your staff work in Microsoft Teams, you're on a Cursor team, and you can get a Teams admin to approve apps.
Skip it if you wanted a meeting assistant, a solo setup, or a rollout with no admin involvement.
The flow itself is spelled out button by button.
What's missing is detail on how approvals, files and compute behave once the Bot is inside Teams.
The scorecard: eight criteria rated out of 10
| Criterion | Score | Why, from the docs |
|---|---|---|
| Setup clarity | 8 | Every button, status and fallback is named, from Enable to Resubmit |
| Owner and admin control | 8 | Enable and Revoke at team level, a linked-accounts list, per-person roles |
| Staff privacy | 8 | One-to-one chats with a shared Bot are private from the owner and Managers |
| Ongoing maintenance | 7 | Two Teams fixes shipped in early November (v0.78.4 and v0.79.3) |
| Where it works in Teams | 6 | Direct chat and channel mentions; no meetings or calls are documented |
| Plan reach | 6 | Shared Bots need a Cursor team, so personal plans can't use it |
| Approval friction | 5 | Needs a Grok team admin and a Teams admin, with no Microsoft alert |
| Teams-specific documentation | 5 | Approval cards, compute and usage are explained for Slack, not for Teams |
The eight scores average 6.6.
What Grok Bot in Teams actually is
It's a channel for shared Bots, the Bots a Cursor team builds once and shares with colleagues.
A team admin turns it on from the Grok Bot page of the dashboard; then the Bot's owner or a Manager connects the Bot and chooses which teams it enters.
A Microsoft Teams admin approves it, each teammate links an account, and from then on people message it or @mention it in a channel and the reply comes back in the same conversation.
For the wider shared-Bot story, including Slack and roles, see my Grok Bot teams verdict.
Strength: the setup steps are spelled out (8/10)
Few admin features document their failure states this well.
The docs name what you'll see when the org blocks custom apps, offer a Download app package button for the admin, and name the app-policy block on the Channels screen.
Waiting states get Check again and Cancel request, and a declined Bot gets Resubmit.
That's a full map of the unhappy paths, which is why it scores high.
It misses a 9 because the happy path still depends on a person outside Grok Bot acting on a link.
The dashboard Setup Checklist, which gained a "Slack or Microsoft Teams" step in v0.55.0, also helps first-time admins find the switch.
Strength: the owner keeps control (8/10)
A team admin can switch Teams off with Revoke at any time.
Manage Microsoft Teams accounts shows who has linked.
Sharing can cover the whole team or only invited people and groups, and only Managers can change how the Bot works.
Name and avatar edits go back to the Teams admin through Update in Teams, so nothing changes in Teams unseen.
Owners can also decide whether Collaborators may set up routines, under the Bot's General settings.
Only the owner can delete a shared Bot, which removes it for the whole team along with its chats and routines, so that power is narrow by design.
Strength: one-to-one chats stay private (8/10)
Each person's chat with a shared Bot is private; the owner and Managers can't read it.
What the Bot learns about one person stays with that person, and what it saves for the team shows up for review.
It loses points because channel replies are, by nature, visible to the whole channel, so file choice matters.
🔥 Want to see shared Bots run in a real business? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members testing Bot rollouts. → Join the AI Profit Boardroom
Limit: two admins and no alert from Microsoft (5/10)
This is the biggest drag on the score.
Turning Teams on needs a team admin who can sign in as a Microsoft Teams or Global administrator.
Each Bot then waits in the Teams admin center's Pending approval list.
Microsoft doesn't notify the approver, so the person doing setup must send them the link from the dialog.
Any later name or avatar change waits for that admin again.
In a firm with outsourced IT, every one of those waits runs through a third party.
The 6 November release did improve the first hurdle: a failed admin sign-in now shows Microsoft's own error with Try again.
Limit: chat and channels only (6/10)
The docs cover two things: chatting with the Bot and mentioning it in a channel of a team it joined.
Nothing in the docs or changelog describes joining Teams meetings or calls.
So it can't sit in a meeting, transcribe it live or speak on a call, and buyers who assumed otherwise will be let down.
Within its scope it does the basics well: chats and channel mentions, with replies kept in the same conversation.
Limit: the Teams side of the docs is thin (5/10)
The shared Bots page answers three practical questions for Slack: which computer the Bot works on, whose usage pays, and how approval cards appear.
It doesn't repeat any of them for Teams.
File handling in Teams isn't covered either, and GCC or sovereign clouds aren't mentioned.
Until that changes, write "draft only" into a Teams Bot's instructions and add Ask first rules from the approvals page for anything that sends or deletes.
Limit: team plans only (6/10)
Grok Bot comes with every paid Cursor plan, an individual SuperGrok link or a self-serve Grok Business seat for individuals.
On Cursor Teams it's on for every member by default, and on Enterprise an admin enables it.
Only the team options give you shared Bots, so only they give you Teams.
No prices are given here; the plan pages carry them.
The other Teams link: the connected app
Separately, Microsoft Teams appears as a Microsoft 365 connected app on the security page, using graph.microsoft.com.
The changelog says routines can start from a Teams message (12 August) and pasted links in Teams messages keep their address (3 November).
It isn't in the main connected-apps list, so I don't score it.
If your team uses the network allowlist, that host has to be under Allowed destinations before the connector will work.
Keep the two ideas apart when you brief staff: the connected app reads Teams data for a Bot, while the shared-Bot channel puts the Bot into Teams as something people talk to.
How it compares with the shared-Bot Slack route
No official source compares the two, so this is my reading of the same docs page.
| Question | Slack | Microsoft Teams |
|---|---|---|
| Who connects it | Owner or Manager, after sharing | Owner or Manager, after sharing |
| Admin step | A Slack workspace admin may need to approve | A Grok team admin enables it, then a Teams admin approves every Bot |
| Which computer is used | Documented per DM and channel | Not documented |
| Approval cards | Review an action card in the thread | Not documented |
| Usage billing | Stated: the person being answered | Not stated by name |
| Teammate linking | Required | Required |
Slack wins on documentation today.
Teams wins if Teams is simply where your staff already are.
What would raise the score
- A Teams section that states which computer the Bot works on in channels and chats.
- A described approval card inside Teams threads.
- A clear line on files shared in Teams.
- A way to nudge the Teams admin from inside the flow, instead of copying a link by hand.
Any one of those would lift the documentation score, and the first two would lift approval friction too.
Who should use Grok Bot in Teams
A small architecture studio
- The practice manager loads the studio's drawing standards and project-start checklist into a shared Bot.
- It joins the Projects team after the Teams admin approves it.
- A junior @mentions it in the channel to ask the file-naming rule.
- It answers in the thread from the standards doc.
A bookkeeping firm
- The owner writes the instructions: answer office-process questions, draft only, never contact clients.
- Staff chat with it privately to check the month-end checklist order.
- Client records stay out of its files.
A dental practice's reception
- The manager adds the front-desk handbook and the cancellation policy text.
- Reception staff ask it for the wording of a reminder message.
- They review the draft and send it from their own system.
📞 Choosing between Bots, Slack and Teams? Book a free SEO strategy session and my team will help you pick where AI fits and how it supports your search traffic. → Book the free session
Who shouldn't use it yet
- Solo owners on a personal plan.
- Anyone who needs a meeting note-taker.
- Firms whose Teams policy blocks custom apps, with no admin willing to allow them.
- Teams that want a fully documented approval flow inside Teams today.
Final verdict: 6.6/10, solid for Teams-first teams
All of a user's Bots share one cloud computer, with a separate screen for each Bot, per the FAQ; the Teams channel doesn't change that.
What it adds is reach: your shared Bot meets staff where they already type.
The cost is admin effort, plus a few doc gaps you cover with your own rules.
Run it for a month on one team before you widen it, and score it again on what your staff actually asked.
If the Teams docs fill in approvals and compute, I'd expect the overall score to climb.
Members of the AI Profit Boardroom compare these trade-offs on the weekly calls.
If your staff live in Teams, connect one pilot team and judge it on real questions.
Also On Our Network
- 🌐 The five-step Teams setup with a fix for every stuck status
- 🌐 Whether a shared Bot in Teams is worth it for a small team
- 🌐 Five Agent OS prompts that carry a Teams rollout's paperwork
- 🌐 Which benchmark-ranked models to pair around a Teams rollout
FAQ: Grok Bot Microsoft Teams Verdict
What score does Grok Bot in Microsoft Teams get?
6.6 out of 10, the average of eight editorial scores based on xAI's documentation.
What is its biggest weakness?
Approval friction: it needs a Grok team admin and a Microsoft Teams admin, and Microsoft doesn't alert the Teams admin that a Bot is waiting.
Does it work in Teams meetings?
Not according to the docs. They cover direct chats and channel mentions only.
Is anything about Teams undocumented?
Yes. The docs don't say how approval cards, compute or file handling work inside Teams, though they explain these for Slack.
Who is it best for?
Small teams on a Cursor team plan whose staff already work in Microsoft Teams and who have a Teams admin ready to approve apps.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Want a second opinion before you commit? Book a free SEO strategy session or join the AI Profit Boardroom, then decide whether Grok Bot Microsoft Teams earns a place in your stack.
