How to Connect Multiple Teams Accounts to Grok
Grok has a real Microsoft Teams connector, it is not plan-gated, and setting it up takes four clicks with no tenant ID and no admin console. That already makes it easier than Grok’s own OneDrive and SharePoint connectors, which are Business and Enterprise only and need a Microsoft 365 administrator before anyone can sign in. Teams needs none of that. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
Then you read the permission list against Microsoft’s own reference and the picture changes. Three of the eleven permissions Grok requests require an Entra administrator’s consent, and Microsoft applies consent to the whole bundle. So the connector that looks self-serve is, for most work tenants, gated on exactly the thing it leads with.
One orientation note. “Grok” names three products: the consumer assistant at grok.com, Grok Bot for Slack and GitHub, and the Grok API. This page is the first one.
Setup, and it genuinely is four steps
- Go to grok.com/connectors.
- Click New Connector and select Microsoft Teams.
- Sign in with your Microsoft work or school account.
- Review the requested permissions and click Accept.
That is the whole documented flow. There is no Azure AD tenant ID field, no console step, and no separate write application, all of which Grok’s SharePoint connector requires. Teams also carries none of the “Business and Enterprise plans only” banner that OneDrive and SharePoint each open with, so on paper it is available to every Grok user.
Note the account type though: work or school only. There is no path here for a consumer Microsoft account, which is consistent with the rest of Grok’s Microsoft surface.
The permission split nobody mentions, and it decides what you actually get
Grok requests eleven delegated permissions. Checked against Microsoft’s Graph permissions reference, they do not all behave the same way:
| Permission | What it does | Needs an Entra admin? |
|---|---|---|
Team.ReadBasic.All | List the teams you belong to | No |
Channel.ReadBasic.All | List channels within those teams | No |
ChannelMessage.Read.All | Read messages in channels | Yes |
ChannelMessage.Send | Send messages and replies in channels | No |
ChannelMember.Read.All | View channel membership | Yes |
TeamMember.Read.All | View team membership | Yes |
Chat.Read | Read one-to-one and group chats | No |
Chat.Create | Create new chats | No |
ChatMessage.Send | Send messages in chats | No |
User.Read | Read your profile | No |
offline_access | Stay signed in | No |
Read that table twice, because the shape of it is strange. You can post into a channel without an administrator’s involvement. You cannot read that channel without one. Sending is consent-free and reading is not.
The chat side is entirely consent-free. Every one-to-one and group chat permission, including creating chats and sending messages, needs no admin. So if your organization never approves the xAI application, the honest expectation is a connector that works in your DMs and group chats and cannot see a single channel message.
xAI does mention this, but as a footnote rather than a headline: “Some organizations require an Azure AD administrator to approve application permissions before users can sign in. If you see a ‘need admin approval’ error, contact your IT administrator.” That framing is accurate and it undersells the odds. Three admin-consent permissions in a bundle means the prompt is the default outcome in a managed tenant, not an edge case.
What it can do once it works
xAI’s documented capability list is unusually generous for this category, and worth crediting properly:
- Search messages across all your channels and chats by keyword
- Read channel messages including threaded replies, reactions and @mentions
- Read chat messages from one-to-one and group chats
- Send channel messages and reply to existing threads
- Send chat messages in one-to-one and group chats
- Create chats to start new conversations
- Browse teams and channels
- View team and channel members including roles and membership types
⭐ Sending is the part to notice. Across this whole category of assistant connectors, most read and very few write, and fewer still say so in a documented capability list rather than implying it through a scope. Grok documents posting to a channel, replying in a thread, and starting a new chat. That is a real capability and it is stated plainly.
Two limits are stated just as plainly. These are delegated permissions, so “Grok can only access teams, channels, and chats that the signed-in user already has access to,” and the privacy section repeats it: “Grok can only access teams, channels, and chats you are already a member of.” Nothing is stored on xAI servers, and your Teams data is not used for training.
A second organization: undocumented
Grok’s Teams documentation never mentions a second account, a second tenant, or switching between organizations. Not to permit it, and not to refuse it. That is genuine silence and it should be read as silence rather than as a no.
What the page does establish is that one connection carries one signed-in identity, and every capability is scoped to what that identity is already a member of. So the practical expectation is one organization per connection, with the second one’s existence simply unaddressed. Try it if you like and verify against a channel you know exists in the second tenant.
⭐ The comparison worth making is with Teams itself. Microsoft treats working across organizations as completely normal: the Teams client has an account and organization switcher precisely because consultants, contractors and agency staff live in several tenants at once. Microsoft solved this at the client level years ago. The assistant layer bolted on top holds one delegated token and does not switch. That gap is the whole reason this page exists, and it is not specific to Grok.
Shared channels are the workaround, and guest access is not
There are two ways Microsoft lets you work in someone else’s organization, and only one of them is any use to a connector holding a single token.
Guest access makes you a guest in the other tenant. You reach it by switching organizations in the Teams client, which is exactly the move a single delegated token cannot make. Assume this does not help.
Shared channels, Microsoft’s Teams Connect feature, work the other way round. Verified from Microsoft’s documentation: shared channels do not use guest accounts at all. “While shared channels with external participants don’t use guest accounts, you can invite people outside your organization to participate in a shared channel by using Microsoft Entra B2B direct connect.” Microsoft is explicit that the two mechanisms are separate, and that “guests, including those converted to members, can’t be added to a shared channel.”
So a shared channel is the one arrangement where another organization’s conversation is something you participate in as yourself rather than as a guest identity you have to switch into. Setting one up has real prerequisites, all documented: both organizations must configure cross-tenant access settings in Microsoft Entra ID, guest access in Teams must be enabled in order to invite external participants even though the channel will not use guest accounts, and only team owners can create shared channels.
Whether Grok’s delegated channel read then covers a shared channel is not documented by either vendor. It is the obvious place to look and the obvious thing to test, so treat it as an inference and check it against one known message before you rely on it. Note too that Microsoft documents several apps as unsupported in shared channels in GCC, GCC-High and DOD environments, so a government tenant should not assume parity.
Nothing fires when a message arrives
Since July 2026 Grok can start work on its own two ways: a schedule, or an incoming email that matches your filters. Email is the only event it watches. The connectors it has to Salesforce, Teams, SharePoint, and the rest never fire anything — they wait to be asked inside a conversation.
This is the sharper limitation for anyone whose actual goal is a Teams assistant rather than a Teams search box. Grok can post to a channel, and nothing in Grok will ever notice that a channel received something. An @mention at 9pm, a customer escalation in a shared channel, a handover note dropped into a project team, all of it waits until a person opens a chat window and asks.
A scheduled automation is the nearest native pattern: you can mention a connector with @ so Grok uses it on every run, which makes a morning Teams digest genuinely achievable. It is a clock, not a listener.
Connect every account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Microsoft Teams and click Connect.
- Authorize the first Microsoft account and confirm the address.
- Click Connect again for the next one, signing out of the preselected Microsoft session first so the right account is used.
- Repeat until every account appears in the connected list.
Each one is its own authorized connection, so two organizations stay two separately addressable things rather than shared sessions on one machine.
Add Carly to Grok
- Go to grok.com/connectors.
- Click New Connector, then select Custom.
- Enter
https://carlyassistant.com/mcp/. - Complete the authentication step.
- Sign in to the Carly account holding the connections above.
Grok discovers the tools Carly exposes and offers them in conversation alongside its built-in connectors. On Grok Business and Enterprise a team admin provisions connectors in the cloud console first.
Then name the target in every instruction, so the account being acted in is explicit rather than whichever session happens to be live.
Grok versus Carly on Teams
| Need | Grok | Carly |
|---|---|---|
| Read and search one organization’s Teams | Yes, with admin consent | Yes |
| Post to a channel or reply in a thread | Yes, no admin consent needed | Yes |
| Work in chats without an administrator | Yes | Yes |
| Read channel messages without an administrator | No, admin consent required | Yes |
| Hold two organizations as separate connections | Undocumented | Yes |
| Name which organization an instruction means | Not documented | Yes |
| Reach a second org without both admins configuring Entra | No | Yes |
| Act when a message arrives | No trigger | Yes |
Grok deserves the credit on the first three rows. A free, self-serve Teams connector with documented send verbs on every consumer tier is more than most assistants in this category offer, and the delegated-permission model is honest about never exceeding what you can already see. If you live in one organization and your IT department is cooperative, it is a good fit.
Carly is built for the part that stays hard. It authorizes per identity, so two organizations sit side by side as separate connections you can name in an instruction, rather than one token plus a cross-tenant Entra project. And it acts on the message rather than on a schedule: the mention lands, the escalation is spotted, the reply goes out before anyone has opened Teams.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Microsoft Teams.
Quick fixes
| Problem | Fix |
|---|---|
| Sign-in says “need admin approval” | Three requested permissions need Entra admin consent. Ask IT to grant consent for the xAI Grok application under Enterprise applications |
| Chats work but channels return nothing | Exactly what a refused admin consent looks like. Chat permissions are consent-free; reading channel messages is not |
| Grok cannot see a team you are in | Access is delegated to your membership. If you are not a member of the channel, neither is Grok |
| A consumer Microsoft account will not connect | Sign-in is work or school only |
| A second organization has nowhere to go | Undocumented. Use a shared channel rather than guest access, and expect both tenants’ admins to be involved |
| Nothing happens when you are @mentioned | There is no Teams trigger. A scheduled automation mentioning the connector is the nearest native pattern |
| You want access revoked now | Disconnect at grok.com/connectors, or revoke the app at myapps.microsoft.com |
Frequently asked questions
Does Grok work with Microsoft Teams?
Yes. Microsoft Teams is a built-in connector added at grok.com/connectors, and unlike Grok’s OneDrive and SharePoint connectors it carries no Business or Enterprise plan gate. Sign-in requires a Microsoft work or school account.
Do I need an administrator to connect Teams to Grok?
Probably, and this is the detail most write-ups miss. Three of the eleven permissions Grok requests require an Entra administrator’s consent: reading channel messages, viewing channel membership, and viewing team membership. Microsoft applies consent to the whole bundle, so a managed tenant will usually stop at an approval prompt. Every chat permission is consent-free.
Can Grok post messages in Teams?
Yes, and that is unusual in this category. It documents sending channel messages, replying to existing threads, sending chat messages, and creating new chats. Sending to a channel does not require admin consent, even though reading one does.
Can I connect two Teams organizations to Grok?
Not in any documented way. Grok’s Teams documentation never addresses a second tenant either way, and every capability is scoped to the single signed-in identity’s memberships. Plan on one organization per connection.
What is the best way to reach a second organization?
A shared channel rather than guest access. Shared channels use Microsoft Entra B2B direct connect instead of guest accounts, so the conversation reaches you as yourself rather than as an identity you have to switch into. Both organizations have to configure cross-tenant access settings first, and only a team owner can create the channel.
Related: Multiple Outlook accounts in Grok · Multiple SharePoint sites in Grok · Grok connectors · Grok and Microsoft 365 · Best AI assistants for Microsoft Teams · Microsoft Teams integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
