Grok Bot Microsoft Teams: Connect A Shared Bot In 5 Steps (2026)

Grok Bot Microsoft Teams support puts your team's shared Bot inside Teams, where staff can message it or @mention it in a channel and get the reply in that same conversation.

It only works for shared Bots on a Cursor team.

It needs two different admins to say yes.

And it does not join Teams meetings or calls.

Below is the order I'd run it in, the status messages you'll hit, and the fix for each, all taken from xAI's shared Bots docs and the teams and enterprises page.

Want a second pair of eyes on your rollout? Book a free SEO strategy session with my team.

What this connection does, and what it doesn't

The Teams channel is a shared-Bot feature, nothing more.

The admin page describes it as letting a team's shared Bots join Microsoft Teams.

A Bot that runs on your own computer can't be shared, because shared Bots always run in the cloud, so that kind of Bot never reaches Teams.

A personal Bot that you keep to yourself doesn't get a Teams button either.

Once it's in, teammates chat with it or @mention it in a channel of any team it joined, and the answer arrives in the same thread.

Nothing in the docs or the Grok Bot changelog says it joins meetings or calls.

So plan for chat and channels only: no live meeting notes, no voice on a Teams call.

If you want the general shared-Bot basics first (roles, sharing, Slack), read my Grok Bot teams walkthrough; this page stays on the Microsoft side.

The two-admin rule: who you need before you start

Line these people up before you touch a single setting.

A Grok team admin. Only team admins can switch Microsoft Teams on for the team.
A Microsoft account with Teams or Global administrator rights. The dashboard switch asks for that sign-in.
The Bot's owner or one of its Managers. One of them runs Connect on the Bot.
A Microsoft Teams admin who approves apps. They approve the Bot in the Teams admin center, and again after profile edits.

In a five-person business, one person might wear all four hats.

If your IT is outsourced, the last role usually sits with your managed service provider, so warn them on day one.

You also need Grok Bot on a Cursor team, since shared Bots are only for Cursor team members who have Grok Bot.

Step 1: Enable Microsoft Teams on the Grok Bot dashboard

Sign in as a team admin and open the Grok Bot page of the Cursor dashboard.
Find the Shared Bots section.
Choose Enable next to Enable Microsoft Teams.
Sign in with the Microsoft Teams or Global administrator account.
Confirm the row now reads Microsoft Teams enabled for your organization.

Revoke on that row switches it off again.

Manage Microsoft Teams accounts lists the members who have linked, which becomes your progress tracker for Step 5.

If the Microsoft sign-in fails, v0.79.3 (6 November) now shows Microsoft's own error with Try again and Back to dashboard, so read that message before you retry.

The dashboard's Setup Checklist has carried a "Slack or Microsoft Teams" step since v0.55.0 on 16 September, which is a handy reminder for new admins.

Step 2: Share the Bot first, then connect it

The Connect button belongs to shared Bots, so sharing comes before anything else.

Open the Bot's chat and choose Share at the top right.
Under Who has access, pick the whole team, or People you invite to keep it narrow.
Promote one or two people to Manager.
Leave everyone else as a Collaborator, who can chat but can't change how the Bot works.

Before you share, walk through its apps, secrets, skills and files.

All of that works in every teammate's chat, so strip out any key you wouldn't hand to the whole office.

Step 3: Connect and pick the teams

Open the Bot's details and find Bring to your team's Microsoft Teams, or go to Manage and look under Channels.
Choose Connect.
Complete the Microsoft sign-in in the browser window that pops up.
Tick the teams the Bot should join.

Pick narrowly at first.

One pilot team is far easier to watch than every team in the company.

🔥 Want the whole shared-Bot rollout on video? 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 comparing their Bot setups. → Join the AI Profit Boardroom

Step 4: Get the Teams admin to approve the pending app

After Connect, the dialog sits on Waiting on admin approval.

This is where rollouts stall, because Microsoft sends the admin no alert that anything is waiting.

Copy the link the dialog gives you.
Send it to your Microsoft Teams admin yourself, by email or chat.
They open the Teams admin center and go to Teams apps, then Manage apps, then Pending approval.
They approve the Bot, and setup completes without you doing anything else.

Press Check again if you want to confirm the moment they approve.

Cancel request stops the whole thing if you connected the wrong Bot.

Step 5: Have every teammate link their Teams account

Approval puts the Bot in Teams, yet every person still links their own account.

In the Grok Bot app, open Settings, then General, then Shared Bots.
Choose Link next to Microsoft Teams account.

I'd put those two lines in the first post of the Bot's channel.

Then check Manage Microsoft Teams accounts on the dashboard to see who has done it and who to nudge.

Reading the status messages, with the fix for each

What you see	What it means	The fix
Waiting on admin approval	The Bot is pending in the Teams admin center	Send the dialog's link to your Teams admin
Microsoft Teams didn't accept the app	Your organization may block custom apps	A Teams admin allows custom apps; hand them the file from Download app package
Not connected · Blocked by your organization's Teams app policy	A Teams app policy stops it	A Teams admin allows the app in the admin center
An update is waiting for your Teams admin	A name or avatar change needs sign-off	Ask the admin to approve the update
The admin declined the Bot	Approval was refused	Sort out their concern, then choose Resubmit

One fix in v0.78.4 (3 November) helps if you ever remove and reconnect a Teams Bot: it no longer leaves a duplicate behind in Teams search.

Changing the Bot's name or avatar later

Rename it in Grok Bot, then choose Update in Teams.

That edit goes back through the Teams admin, so the old name stays visible in Teams until they approve.

Settle the name and avatar before Step 3 and you skip a second round of approvals entirely.

What to load into a Bot that lives in a Teams channel

A shared Bot runs on its owner's apps and secrets for everyone who talks to it.

In a channel, its reply lands in the thread, so everyone in that channel can read the answer.

Build it for that audience.

Give it files the whole team may see: the staff handbook, service menus, process docs.
Keep client folders and finance keys out of a Bot that sits in a general channel.
Write its instructions as one sentence of purpose, then the limits: "answer from the files, draft only, never send email".
Check its Knowledge tab often: new team learnings wait under To review until you choose Approve or Reject.

Approvals, privacy and usage once it's in Teams

A shared Bot asks the person it's answering before risky actions, per the approvals docs.

The docs show how those cards behave in the app, in Slack threads and in group chats, but they don't describe a Teams-specific card.

So for anything that sends, publishes or deletes, I write "draft only" into the Bot's instructions and add an Ask first rule.

One-to-one chats stay private: the owner and Managers can't read a teammate's own conversation with the Bot.

A shared Bot reply uses the Grok Bot allowance of the person it's answering, and the docs confirm that for your own chat, Slack and group chats.

On compute, all of a user's Bots share one persistent cloud computer, and each Bot gets its own screen on it, according to the Grok Bot FAQ.

The docs explain which computer a shared Bot uses in Slack but give no Teams detail, so don't promise your staff either way.

The separate Microsoft Teams connected app

There's a second, different Teams link: Microsoft Teams as a connected app through Microsoft 365.

The security page lists it beside Outlook, Outlook Calendar and OneDrive, all sending requests to graph.microsoft.com.

If your team switched on the network allowlist, add that host under Allowed destinations or the connector gets refused.

The changelog adds two lines: on 3 November, pasted links in Teams messages the Bot reads kept their address, and since 12 August a routine can start from a Microsoft Teams message.

The main app list in the docs doesn't show Teams yet, so treat this side as lightly documented.

📞 Rolling Bots out across a whole team? Book a free SEO strategy session and my team will map where AI fits your business and your search traffic. → Book your free call

Three small-business setups, step by step

An IT support shop with a helpdesk team

The owner creates a shared Bot called "Runbook" and adds the internal runbooks to its Files.
They share it with the support group only.
They connect it to the Support team in Teams, then approve it in the admin center, since the owner is also the Teams admin.
A technician @mentions it: "What are our steps for a new starter laptop?"
It answers in the thread from the runbook.

An accountancy practice

A partner sets up "Practice Admin" with the office procedures and the internal deadlines document.
Its instructions read: answer process questions, draft only, never contact clients.
Staff chat with it in Teams to check the steps for onboarding a new client.
Client files never go into the Bot.

A plumbing and heating firm's office

The office manager builds "Office Desk" with the job-sheet template and the van-stock list.
She brings it to the Office team only, not the engineers' team.
Office staff ask it to draft a booking confirmation for a customer.
They copy the draft, check it and send it themselves.

My go-live checklist

Name and avatar final.
Files and secrets checked for the channel's audience.
Teams enabled on the dashboard.
Bot shared, Managers set.
Connected to one pilot team.
Approval link sent to the Teams admin.
Pinned post: how to link your account.
Ask first rules on send, publish and delete.

Inside the AI Profit Boardroom, members swap checklists like this one every week.

Run the list top to bottom and switch it on today.

Also On Our Network

FAQ: Grok Bot Microsoft Teams

Does Grok Bot join Microsoft Teams meetings or calls?

No. The docs and changelog only describe chatting with a shared Bot or mentioning it in a channel, so plan for chat and channel threads, not meetings or calls.

Why is my Bot stuck on Waiting on admin approval?

Microsoft doesn't tell the Teams admin a Bot is pending. Send them the link from the dialog so they can approve it under Teams apps, Manage apps, Pending approval.

Can I put a personal Bot into Microsoft Teams?

No. The Teams channel is for a team's shared Bots, and shared Bots need a Cursor team and always run in the cloud.

What does each teammate have to do?

Open Settings, General, Shared Bots in the Grok Bot app and choose Link next to Microsoft Teams account.

What happens if I rename the Bot after it's in Teams?

Choose Update in Teams. The change waits for a Teams admin to approve it, and the old name shows until they do.

📺 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

Need help deciding where Bots fit before you scale? Book a free SEO strategy session or join the AI Profit Boardroom, then get your Grok Bot Microsoft Teams setup live this week.