What is the Grok Microsoft Teams connector?
xAI’s Microsoft Teams connector is a built-in OAuth integration that gives Grok controlled access to a user’s Teams conversations. It sits alongside other built-in Grok connectors such as Gmail, Google Drive, OneDrive, Outlook Mail and Calendar, SharePoint and Salesforce.
The Teams connector is not read-only. xAI currently documents both retrieval and action capabilities: Grok can search and read messages, send new channel messages, reply to existing threads, send one-on-one or group-chat messages, and create new chats.
Because the connector uses delegated Microsoft permissions, Grok does not become a tenant-wide superuser. It acts with the signed-in user’s existing access. If that Microsoft account cannot see a private channel or chat, the connector does not grant access to it.
Official source: xAI Microsoft Teams Connector.
Grok Teams connector vs a Grok bot inside Microsoft Teams
This distinction prevents the most common setup mistake.
| Approach | Where you talk to Grok | What it does |
|---|---|---|
| xAI built-in Teams connector | Inside Grok or a Grok workflow | Lets Grok search, read and act on Teams conversations the connected user can access. |
| Teams-native Grok bot | Inside Microsoft Teams | Requires a Teams app/bot architecture so users can message or mention the bot directly in Teams. |
If your goal is “let Grok summarize our Teams channels and send updates,” the built-in connector is the easier path. If your goal is “install Grok as an app inside Teams so coworkers can open a chat with it or @mention it,” that is a separate developer deployment.
What you need before connecting Grok to Teams
- A Grok account with access to connectors.
- A Microsoft work or school account. The built-in Teams connector is designed for Microsoft organizational accounts.
- Permission to access the Teams data you want Grok to use. Delegated access means the Microsoft account remains the boundary.
- Admin consent if your tenant requires it. Some organizations block user consent for enterprise applications.
- For Grok Business or Enterprise: the xAI team admin must provision Microsoft Teams in the xAI cloud console before individual members can connect their accounts.
If you are using Grok Bot specifically, you also need an eligible Grok Bot plan and the Grok Bot app or supported mobile setup. xAI currently describes Grok Bot as a persistent AI teammate running on a cloud computer with a browser, filesystem and terminal, with approvals when sensitive actions need user confirmation.
See xAI Connectors and Grok Bot: Get started.
How to connect Microsoft Teams to Grok
- Open
grok.com/connectors. - Click New Connector.
- Select Microsoft Teams.
- Sign in with the Microsoft work or school account whose Teams access you want Grok to use.
- Review the Microsoft permission screen carefully.
- Click Accept if you are comfortable with the requested delegated permissions.
- Return to Grok and test with a narrow request such as “Summarize the latest messages in the Project Alpha channel.”
- Before enabling write-heavy workflows, test sending or replying in a low-risk channel or chat.
Once the connector is active, Grok can use the Teams tools automatically when the request relates to Microsoft Teams. You do not need to paste channel transcripts manually every time.
Grok Business and Enterprise need an admin provisioning step first
For individual Grok use, the user can add a built-in connector directly through grok.com/connectors. The process is different for Grok Business and Enterprise.
xAI says a team admin must first provision the connector in the cloud console:
- Sign in to console.x.ai.
- Select the relevant team.
- Open Grok Business → Connectors.
- Click + Add Connector.
- Select Microsoft Teams and complete any organization-level setup or Microsoft admin consent required.
- After provisioning, team members can connect their own Microsoft accounts from
grok.com/connectors.
Adding or removing connectors requires xAI team management permissions. Provisioning the connector makes it available to members; it does not silently sign every employee into Microsoft Teams or grant them access to other users’ conversations.
Admin setup: xAI Connector Management.
Microsoft Teams permissions Grok requests
xAI currently documents the following delegated Microsoft permissions for the built-in Teams connector:
| Permission | Purpose |
|---|---|
Team.ReadBasic.All | List the teams the signed-in user belongs to. |
Channel.ReadBasic.All | List channels inside those teams. |
ChannelMessage.Read.All | Read channel messages the signed-in user can access. |
ChannelMessage.Send | Send channel messages and replies. |
ChannelMember.Read.All | View channel membership. |
TeamMember.Read.All | View team membership. |
Chat.Read | Read one-on-one and group-chat messages. |
Chat.Create | Create one-on-one and group chats. |
ChatMessage.Send | Send messages in chats. |
User.Read | Read the signed-in user’s profile. |
offline_access | Maintain authorization without forcing a fresh Microsoft sign-in every time. |
These are delegated permissions. xAI explicitly says Grok can only access teams, channels and chats that the signed-in user already has access to.
Permission design matters: connect a normal user account whose access matches the work you actually want Grok to perform. Do not solve a workflow problem by granting a human account broader Microsoft access than the employee should have.
Scope list: xAI Microsoft Teams Connector → Required permissions.
How to fix “Need admin approval” when connecting Teams
Some Microsoft Entra tenants prevent ordinary users from granting consent to enterprise applications. In that environment, the OAuth flow can stop with a “need admin approval” message.
xAI’s documented fix is to contact your IT administrator and ask them to grant consent for the xAI Grok enterprise application in the Microsoft Entra/Azure AD admin portal under Enterprise applications.
The administrator should review the scopes before approving them. Because the connector can both read and send Teams messages, this is not a trivial read-only permission set.
If consent is approved but the user still cannot connect, verify that the correct Microsoft tenant and work account are being used and that the user is allowed to sign into the enterprise application.
What Grok can currently do with Microsoft Teams
xAI’s connector documentation currently lists these capabilities:
- Search messages across accessible channels and chats by keyword.
- Read channel messages, including threaded replies, reactions and @mentions.
- Read one-on-one and group chats.
- Send new channel messages.
- Reply to existing channel threads.
- Send messages in one-on-one and group chats.
- Create new chats to start a one-on-one or group conversation.
- Browse teams and channels to understand where conversations are happening.
- View team and channel members, including roles and membership types.
Because the connector can write as well as read, prompts should specify whether you want Grok to draft a message or actually send it. For consequential communication, keeping an explicit approval boundary is safer than assuming every generated update should be posted immediately.
Practical Grok Bot + Teams use cases
| Use case | What the Bot can do |
|---|---|
| Morning channel brief | Summarize overnight messages from selected project or operations channels and surface unresolved questions. |
| Decision finder | Search chats and channels for where a decision was made, then return the relevant thread and context. |
| Project status summary | Collect updates from a project channel, identify blockers and prepare a concise status report. |
| Unanswered-question scan | Find questions or requests that did not receive a meaningful reply and prepare a follow-up list. |
| Incident coordination | Create a group chat, pull the latest relevant context and prepare an incident update for approval. |
| Meeting preparation | Summarize recent Teams conversations relevant to an upcoming meeting before building the agenda. |
| Management digest | Combine updates from several teams or channels into an executive summary with links back to source conversations. |
| Sales handoff | Read internal Teams discussion around an account, combine it with connected CRM context and prepare a handoff brief. |
| Customer escalation brief | Collect discussion, decisions and owners from Teams before producing a structured escalation summary. |
| Draft and send status updates | Prepare an update from current Teams context and, when explicitly authorized, send it to a channel or chat. |
| Cross-tool workflow | Use Teams as one source inside a larger Grok Bot task that also touches files, email, CRM, browser research or documents. |
Grok Bot is designed for this kind of multistep work. xAI describes each Bot as a durable AI teammate with a persistent cloud computer, its own role, working context and access to the tools it needs.
Grok Bot architecture and working model: Grok Bot overview and Create and manage Bots.
Turn a successful Teams workflow into a Skill or Routine
xAI recommends starting with a one-time task, making it reliable, saving the method as a Skill, and only then automating it as a Routine.
A Skill can preserve the source channels, definitions, expected output, decision rules and approval boundaries. A Routine tells a specific Bot when to run that workflow — for example, every weekday morning or on another supported schedule/event.
A useful Teams routine might say:
Example routine design
Every weekday morning:
1. Review the Project Alpha and Operations channels.
2. Summarize decisions, blockers, deadlines, and unanswered questions.
3. Link the source threads.
4. Draft a management update.
5. Do not send or post anything without approval.That last rule matters. xAI’s own guidance for Bot roles encourages explicit approval boundaries for external actions.
Automation guidance: Grok Bot Skills and routines.
Privacy, storage and access boundaries
xAI’s current Teams connector page makes three notable claims about the built-in connector:
- Teams data is not used for model training.
- Teams connector data is accessed in real time and not retained afterward on xAI servers, according to the connector documentation.
- Access is scoped to the signed-in Microsoft user. Grok can only use Teams resources that account is already allowed to access.
You can disconnect the connector from grok.com/connectors, and xAI also points users to Microsoft’s My Apps portal for revoking the application’s access from the Microsoft side.
Grok Bot itself has a broader architecture than a simple connector. xAI documents a persistent cloud computer for each user and separate security/approval controls for Grok Bot. Teams and Enterprise admins should therefore review both the connector documentation and the Grok Bot security/admin documentation before deploying automation around sensitive work.
Connector privacy statements: xAI Teams connector. Grok Bot team controls: Grok Bot for teams and enterprises.
Why the Teams connector may not work
| Problem | What to check |
|---|---|
| Microsoft Teams is missing from a Business/Enterprise user | Ask the xAI team admin whether the connector has been provisioned in the cloud console. |
| “Need admin approval” | Your Microsoft Entra tenant may require an admin to consent to the xAI Grok enterprise application. |
| Grok cannot find a private channel | Confirm the connected Microsoft user is actually a member of that channel. |
| Grok can read but a send fails | Check the connected account’s Teams permissions and whether the relevant Microsoft scope/admin policy allows the action. |
| Wrong conversations appear | Confirm which Microsoft account and tenant were used during OAuth. |
| Connector was removed by the organization | Business/Enterprise admins can remove connectors centrally, making them unavailable to members. |
| Grok Bot plugin is disabled by team admin | On Grok Bot team deployments, check the organization’s connector/plugin policy and marketplace restrictions. |
What if you want employees to talk to Grok directly inside Teams?
The built-in connector is not the same as a Teams-native conversational app. If employees need to search for “Grok” in Teams, open a bot chat, install it as a Teams app or @mention it in a channel, you need to build and deploy a Microsoft Teams bot/app that calls the xAI API.
Microsoft’s documented bot architecture requires a Teams app plus bot registration. A conventional Azure-managed implementation involves an Entra app registration, an Azure Bot resource, a messaging endpoint, the Microsoft Teams channel, and a Teams app package/manifest. Production bots should be distributed as Teams apps rather than added only by bot GUID.
If the Teams-native bot needs to access protected Microsoft resources on behalf of the user, Microsoft also documents OAuth 2.0 authentication flows for Teams bots.
| Goal | Best path |
|---|---|
| Let Grok read and act on my Teams conversations | Use xAI’s built-in Microsoft Teams connector. |
| Let a Grok Bot use Teams in a larger workflow | Use the connector plus Grok Bot skills/routines and explicit approval rules. |
| Let coworkers chat with Grok inside Teams | Build a Teams-native bot/app that calls xAI. |
| Use a custom internal system alongside Teams | Consider an xAI custom MCP connector or a Teams-native app depending on where the interaction should happen. |
Microsoft bot deployment: Connect a Bot Framework bot to Microsoft Teams. Authentication: Add authentication to a Teams bot.
Fast setup checklist
- Decide which architecture you need. Connector from Grok, or a bot that lives inside Teams.
- For the built-in connector, open
grok.com/connectors. - If you use Grok Business/Enterprise, have an admin provision Microsoft Teams first.
- Sign in with the correct Microsoft work or school account.
- Review the delegated permissions before accepting them.
- If Microsoft says admin approval is required, send the request to your Entra administrator.
- Test read-only retrieval first. Ask Grok to summarize a known channel.
- Then test a low-risk write action. Draft or send a message in a safe test conversation.
- For Grok Bot, save successful procedures as Skills before scheduling Routines.
- Keep explicit approval boundaries on consequential external messages and actions.
BeeVaults takeaway: the easiest official integration today is the xAI Microsoft Teams connector. It gives Grok read and write access within the signed-in user’s existing Teams permissions. Use that for summaries, searches, status updates and Grok Bot workflows. Only build a separate Microsoft Teams bot if you specifically need Grok to appear as an interactive app inside the Teams client.