agentos.guide › blog

Grok Bot Microsoft Teams: Brief, Audit And Roll Out A Shared Bot With 5 Prompts In Your Agent OS

By Julian Goldie · 11 November 2026 · agentos.guide

Grok Bot Microsoft Teams rollouts go smoothly when your Agent OS does the paperwork: the Bot brief, the file audit, the approval request and the staff instructions.

Grok Bot handles the Teams side itself, but only for a team's shared Bot, only after a Microsoft Teams admin approves it, and never inside meetings or calls.

Below is a quick start, five copy-paste prompts for your agent and a weekly routine, built from xAI's shared Bots guide and admin page.

Planning this for a client or your own office? My team runs a free SEO strategy session where we map it out with you.

Quick start: the order that works

1. A Grok team admin opens the Grok Bot page of the dashboard, goes to Shared Bots and chooses Enable beside Enable Microsoft Teams, signing in with a Teams or Global administrator account.
2. The Bot is shared with the team (Teams only takes shared Bots).
3. Its owner or a Manager opens the Bot's details, picks Bring to your team's Microsoft Teams, chooses Connect, signs in with Microsoft and selects the teams.
4. A Microsoft Teams admin approves it under Teams apps, Manage apps, Pending approval. Microsoft won't alert them, so send the link from the dialog.
5. Each colleague links their own Teams account under Settings, General, Shared Bots.

Once that's done, people message the Bot or @mention it in a channel, and it replies in the same conversation.

What your Agent OS handles, and what Grok Bot handles

One point to brief your agent on: the Grok Bot FAQ says a person's Bots all run on a single persistent cloud computer, with a separate screen per Bot.

The FAQ also warns against treating separate Bots as a security boundary, so the file audit in Prompt 2 is your real control.

The wider shared-Bot rollout is covered in my Grok Bot teams guide; this one stays on Microsoft Teams.

Before you start: the four sign-offs

Teams rollouts fail on people, not settings, so list who signs off before any prompt runs.

• A Grok team admin, who is the only role allowed to switch Microsoft Teams on.
• Someone holding a Microsoft Teams or Global administrator account for that first sign-in.
• The Bot's owner or a Manager, who runs Connect.
• A Microsoft Teams admin, who approves the Bot and any later profile update.

Give your agent those four names first; every prompt below can then address the right person.

You'll also need to be on a Cursor team, because shared Bots belong to Cursor team members who have Grok Bot.

Prompt 1: write a brief that suits a Teams channel

I'm creating a shared Grok Bot for our [team name] team in Microsoft Teams.
Staff will chat with it and @mention it in channels, and channel replies are
visible to everyone in that channel.
Write: (1) a one-sentence purpose, (2) five rules it must follow, including
"draft only, never send or delete", (3) a list of the question types it should
answer, and (4) the questions it should refuse and send to a person instead.
Keep it under 200 words.

Paste the result into the Bot's instructions when you create it.

Keep the refusal list honest: if staff ask about meetings, the Bot should say it doesn't join them.

Rerun the prompt whenever the team's job changes, rather than letting the brief drift.

Prompt 2: audit files and secrets before you share

Here is the list of files, apps and secrets I plan to give a shared Bot:
[paste list]
Everyone the Bot is shared with will be able to use all of these, and anything
it says in a Teams channel is visible to the channel.
Mark each item KEEP, REMOVE or MOVE TO A PRIVATE BOT, with one line on why.
Flag anything that holds client data, payment details or passwords.

A shared Bot runs on its owner's apps and secrets for everyone, so this check matters.

Anything marked MOVE TO A PRIVATE BOT stays with your personal Bot, which never goes into Teams.

🔥 Run the full Agent OS behind your Bots

The AI Profit Boardroom gives you step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members rolling Bots out to their teams.

→ Join the AI Profit Boardroom

Prompt 3: draft the approval request for your Teams admin

Draft a short, friendly message to our Microsoft Teams admin, [name].
Explain that a Grok Bot shared Bot called [Bot name] is waiting for approval
in the Teams admin center under Teams apps > Manage apps > Pending approval,
that Microsoft doesn't notify them about it, and include this link: [link].
Say which teams it will join and what it will be used for.
Draft only. I will send it myself.

If the dialog instead says Microsoft Teams didn't accept the app, ask your agent to add a line requesting that custom apps be allowed, and attach the file from Download app package.

Prompt 4: write the pinned welcome post

Write a pinned Teams channel post introducing [Bot name] to staff.
Include: what to ask it, what not to ask it, and how to link their account
(Grok Bot app > Settings > General > Shared Bots > Link next to Microsoft
Teams account). Mention that their private chats with the Bot can't be read by
the owner or Managers, but channel replies are visible to the channel.
Say clearly that it does not join meetings or calls. Under 150 words.

Pin it in the first channel the Bot joins, then check the linked-accounts list on the dashboard a day later.

Anyone missing from that list hasn't linked yet, so send them the post again.

Prompt 5: build the weekly review

Every Friday, help me review our shared Teams Bot.
I'll paste: the items under To review in its Knowledge tab, and the members
listed in Manage Microsoft Teams accounts.
Return: which learnings to Approve or Reject and why, which staff haven't
linked yet, and one change to its instructions for next week.

Approving or rejecting learnings happens in the Bot's Knowledge tab; your agent only recommends.

Two worked examples

A small accountancy

1. Prompt 1 drafts "Practice Desk", a Bot that answers office-process questions and never contacts clients.
2. Prompt 2 removes the client folder and the bank-feed key from the plan.
3. The partner enables Teams, shares the Bot and connects it to the Office team.
4. Prompt 3 drafts the note to their outsourced IT firm, who approves it.
5. Prompt 4 becomes the channel's pinned post, and staff link their accounts.
6. Prompt 5 runs every Friday.

A plumbing firm's office team

1. Prompt 1 drafts "Office Desk": answer questions about booking steps and the van-stock list, draft customer confirmations, never send them.
2. Prompt 2 keeps the job-sheet template and stock list, and removes the accounts login.
3. The owner, who is also the Teams admin, connects it to the Office team and approves it.
4. Prompt 4 explains how office staff link their accounts.
5. Staff ask for a draft confirmation in a private chat, check it and send it from their usual system.

The engineers' team is left out on purpose until the office trial settles.

📞 Want a plan for AI across your business?

Book a free SEO strategy session and my team will map where Bots fit and how they support your search traffic.

→ Book your free call

Common snags, and what to tell your agent

• Stuck on Waiting on admin approval. Rerun Prompt 3 as a follow-up note; Check again confirms once they've approved.
• Blocked by your organization's Teams app policy. A Teams admin has to allow the app; ask your agent for a one-paragraph explanation for them.
• Renamed the Bot. Choose Update in Teams; it waits for the admin again, so batch name and avatar changes.
• Declined. Have your agent rewrite the purpose to address the admin's concern, then choose Resubmit.
• Admin sign-in failed. Since v0.79.3 the dashboard shows Microsoft's own error with Try again; paste that error to your agent.

Where the docs go quiet

The shared Bots page explains approval cards, compute and usage for Slack, but not for Teams.

So keep "draft only" in the brief and add Ask first rules from the approvals guide.

Microsoft Teams also shows up as a separate Microsoft 365 connected app on graph.microsoft.com, and the changelog says routines can start from a Teams message; that side is lightly documented.

The weekly workflow, end to end

1. Monday: answer any staff questions the Bot sent to a person.
2. Wednesday: check who still hasn't linked an account.
3. Friday: run Prompt 5 and update the instructions.

Members of the AI Profit Boardroom share their versions of these prompts every week.

Copy Prompt 1 into your agent now and start the brief.

FAQ

Can my Agent OS approve the Bot in Teams for me?

No. A Microsoft Teams admin approves it in the Teams admin center. Your agent can draft the request, but a person sends it and the admin approves.

Does the Bot join our Teams meetings?

No. The documentation covers direct chats and channel mentions, not meetings or calls.

Do staff need to set anything up?

Yes. Each person links their own Microsoft Teams account in the Grok Bot app under Settings, General, Shared Bots.

Can I connect a personal Bot to Teams?

No. Only a team's shared Bots can join Microsoft Teams, so share it first.

Final word on Grok Bot Microsoft Teams

Need a hand mapping the rollout? Book a free SEO strategy session or join the AI Profit Boardroom, and let your Agent OS carry the Grok Bot Microsoft Teams paperwork.

Related guides on agentos.guide

→ Grok Bot Teams: Plan, Audit And Roll Out A Shared Bot With 5 Prompts In Your Agent OS

→ Grok Bot Phone Calls: Brief, Approve And Log Calls In Your Agent OS

→ Grok Bot Connectors: Connect, Track And Reconnect Every App In Your Agent OS

→ Hermes Agent Slack: Run Your Agent In Slack From Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide