xAI has published a setup guide for bringing its Grok Bot into Microsoft Teams. According to xAI’s documentation, a published Team Bot can now be mentioned in channels, messaged directly, and added to group chats. It behaves the way it does in Slack: “it acts for the person who asked, uses their usage, and asks before risky actions.”
This matters because AI assistants are moving into the chat tools where work already happens. Most large companies run on Microsoft 365, so Teams support puts Grok in front of a much bigger enterprise audience.
⚡ Quick Start
You’ll learn how to: enable Teams for your organization, connect a Team Bot, get admin approval, link your account, and fix common setup errors.
You’ll need:
- A published Team Bot that you own or manage as a Manager
- Microsoft Teams turned on for your Cursor team by a team admin
- A Microsoft account in the organization that uses Teams
🔐 Step 1: A team admin turns on Microsoft Teams
- 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.
Why it matters: This is the organization-level switch. Until it’s on, no bot owner can connect anything. Revoke turns it off again. Even after this step, a Teams admin still has to approve each bot separately.
🤖 Step 2: Connect your Team Bot
The owner or a Manager does this after publishing the bot.
- Open the bot’s details and find Bring to your team’s Microsoft Teams, or choose Manage and look under Channels. Choose Connect Microsoft Teams.
- Finish signing in with Microsoft in the browser window that opens. Make sure it’s the right account, and pick an organization if you belong to more than one.
- While the dialog says Waiting on admin approval, a Teams admin has to approve the bot in the Teams admin center under Teams apps > Manage apps > Pending approval.
Warning: Microsoft doesn’t notify the admin. Send them the link the dialog shows yourself. Choose Check again right after they approve, or Cancel request to stop.
After approval, Teams finishes setup on its own, which can take up to an hour. Then you’ll see Open in Teams. To use the bot in a channel, add it to a team from inside Teams. If an admin declines, read their note, make changes, and choose Resubmit.
🔗 Step 3: Link your Microsoft account
The bot needs to know who you are before it can act for you. The first time you message it, you’ll get a Link Account card that only you can see. Choose it and sign in.
You can also link ahead of time: Settings > General > Team Bots, then Link next to Microsoft Teams account.
Why it matters: Each person links their own account, so actions and usage belong to the person who asked. That’s the right design for enterprise accountability.
🛠️ What the bot can do
- Answer in channels and chats. Mention it in a channel, add it to a group chat, or message it directly.
- Read the conversation. It reads its current thread and the channels of the teams it joined.
- Work with files. It reads attachments and sends files through your OneDrive. If you ask for a file in a shared space, it asks you to message it directly instead.
- Act for you. It asks for approval before risky actions.
It can also join and transcribe Teams calls, which xAI covers in a separate meetings guide.
🔄 Updating or removing the bot
- Name or picture changes: choose Update in Teams. Some changes need admin approval again.
- Remove from Microsoft Teams: takes the app out of your organization.
- Disconnect your Microsoft account: this affects every bot you own in that organization, but bots already in Teams keep answering.
- Delete the bot: also removes it from Teams.
🧯 Troubleshooting cheat sheet
- “Microsoft Teams isn’t enabled”: go back to Step 1.
- “Publish this Bot to your team first”: the bot is still a draft. Choose Publish.
- “Microsoft Teams didn’t accept the app”: your org blocks custom apps. Choose Download app package and send it to your Teams admin.
- “Blocked by your organization’s Teams app policy”: a Teams admin needs to allow it.
- “Need admin approval”: send a Teams or Global admin the consent link, then reconnect.
- “Microsoft Teams stopped working”: the connection expired. A team admin should choose Reconnect Microsoft Teams.
- “Finishing setup in Microsoft Teams”: wait. It can take up to an hour.
If nothing matches, xAI says to contact support with the bot’s name, the exact message, and your Grok Bot version.
🚀 Next steps
- Start with one low-risk channel and watch how teammates use the bot before you roll it out wider.
- Read xAI’s approvals and security docs so you know which actions trigger a confirmation.
- Talk to your Teams admin about custom-app policy before you start. Most setup delays happen at approval.
What stands out here is how much the process depends on admins. Grok is clearly aimed at enterprises where IT stays in control. You’ll find the full details in xAI’s original documentation.