Connect Multiple Outlook Accounts to Grok Bot
Carly connects every Outlook mailbox you own, and one Grok Bot conversation works across all of them at once. Connect them at carlyassistant.com, add Carly to Grok Bot once as a plugin, and your personal, work, and client mailboxes each stay their own authorized identity. The same Carly account holds your Gmail inboxes and the calendars on both sides, so you set this up once for all of it. Grok Bot’s own Outlook plugin signs in a single Microsoft account, and every mailbox after that is a browser login on a cloud computer all of your Bots can drive.
1. Add your Outlook accounts to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Outlook, click Connect, and authorize the account.
- Click Connect again for the next one, and keep going for as many as you want.
Each one is an ordinary OAuth connection, so no credential is replayed from a browser session and no tenant sees a sign-in it did not expect.
Two things to watch. Microsoft silently reuses whichever account your browser already holds, so sign out between accounts or use a separate profile, then confirm the full address that comes back. And a managed tenant may route consent to an administrator, which is policy rather than failure, and worth clearing before you connect the rest.
Carly connects to thousands of apps, so while you are on that page add your calendars, files, and CRM too.
2. Add Carly to Grok Bot
- Select Plugins in the Grok Bot sidebar, or tap your avatar and choose Plugins on mobile.
- Add Carly’s remote MCP server,
https://carlyassistant.com/mcp/. - Finish authorization in the browser tab that opens. If it sits on Waiting for authorization, use Reopen.
- Sign in to the Carly account holding the mailboxes above.
- Confirm Carly appears under Installed.
Grok Bot takes remote MCP servers, and Carly’s is hosted, so it qualifies. Plugin connections belong to your Grok Bot account rather than one Bot, and team plans inherit Cursor’s MCP policy, so an admin can gate it.
What one conversation can do afterwards
- Search personal and work Outlook in the same question.
- Compare threads sitting in different Microsoft 365 tenants.
- Produce a daily summary grouped by mailbox.
- Draft or send from the exact address you choose.
- Move, categorize, or archive in the correct mailbox.
- Check several calendars while writing to only one.
Nothing is merged. Each mailbox keeps its own credentials and stays individually addressable, so an instruction naming a client account cannot quietly land in your work one.
What happened to the people who signed Outlook into a Bot
For its first two weeks Grok Bot had no Microsoft connector at all, and the documented answer was to have the Bot open Outlook on the web and sign in there. Three things came back from users who did.
One found the cloud session logging him out of Microsoft on his own machine every time, which killed the route before it started. Another had agents skimming mail through the browser and losing the session over and over. The third is the one to sit with: his Microsoft 365 account was locked after the same credentials showed up on a server and his PC at the same moment. That is not a bug. It is a tenant security control working correctly, because a mailbox credential replayed from a datacenter is what account compromise looks like.
Cursor added first-party Outlook, Outlook Calendar, and OneDrive plugins on Aug 27, 2026, which fixes the first mailbox. The plugin authorizes a single Microsoft identity. Mailbox two lands right back in the browser.
Why one Microsoft account is never enough
Microsoft identities are the ones people most need kept apart. A personal Outlook address, a work Microsoft 365 mailbox, and a client tenant you were guested into are three trust boundaries, and every admin behind them has opinions. Grok Bot gives you one slot and a shared browser for the rest, and xAI states plainly that browser cookies and signed-in sessions are shared across every Bot on the account, and that separate Bots are not a security boundary.
So the second mailbox is not merely inconvenient. It is the one that gets a tenant’s attention.
The plugin, the browser, and Carly
| Need | Outlook plugin | Shared browser | Carly |
|---|---|---|---|
| Reach one Microsoft mailbox | Yes | Yes | Yes |
| Reach the second one | No, one identity per plugin | Yes, as a session | Yes |
| Avoid a credential appearing from a datacenter | Yes | No, this is what locked an account | Yes |
| Keep your local Microsoft session signed in | Yes | Users report being logged out | Yes |
| Stop one Bot reaching a client tenant | No, plugins are account-wide | No, cookies are shared | Yes, per connected account |
| Say which mailbox an action ran in | Single account, so implicitly | Not reliably | On every action |
| Survive a handoff to another Bot | Inherited | The next Bot inherits every login | Routing stays by address |
| Start work when mail arrives | No | No | Yes |
That last row is the one that pays. Carly watches your mailboxes and calendars and acts on what arrives, so the reply that needs sending or the meeting that needs moving does not wait for someone to open an app and ask. Free Zapier-style workflows; AI agents from $35/month. Connect every mailbox at carlyassistant.com.
Quick fixes
| Problem | Fix |
|---|---|
| A Bot acted in the wrong mailbox | Name the full address in the instruction rather than the role |
| Your local Microsoft session keeps signing out | Stop using the Bot’s browser for mail and connect the mailbox to Carly |
| A tenant locked the account after agent use | Clear it with your admin, then reconnect as an authorized app rather than a browser login |
| Two Bots need different mailboxes | Route through Carly, which holds all of them and keeps each one separate |
| Microsoft reused the account you were already in | Sign out between connections, or use a separate browser profile |
| A work account stalls at consent | A Microsoft 365 administrator has to approve before authorization completes |
| Sends go out before you see them | Add a Require Approval rule for external email |
Frequently asked questions
Can Grok Bot connect two Outlook accounts at once?
Not through the plugin. The Outlook plugin added on Aug 27, 2026 authorizes a single Microsoft identity. A second mailbox has to be a browser session on the shared cloud computer, which is the arrangement that got one user’s Microsoft 365 account locked. Connecting each mailbox to Carly keeps them separate and individually addressable.
Do separate Bots keep my mailboxes apart?
No. Every Bot on your account shares one cloud computer, including its browser sessions and logins, and xAI advises against using separate Bots as a security boundary.
Will my Microsoft 365 admin need to approve this?
Possibly. Managed tenants often require administrator consent before an application can reach a mailbox. That applies to the connection you authorize, and it is the normal path a tenant expects, unlike a session signed in from a cloud machine.
Does connecting Carly give every Bot access?
Yes. Installed connectors in Grok Bot are account-wide rather than per-Bot, so plan access at the account level and use approval rules for the actions that matter. What changes is that each mailbox inside Carly is a distinct authorized connection, so instructions name a target address.
Can I mix Outlook and Gmail accounts?
Yes. Carly connects all of them, Outlook and Gmail together, and one request can work across the lot. Gmail in Grok Bot has its own authorization troubles worth reading before you rely on it.
Related: Grok Bot · Connect multiple email accounts to Grok Bot · Connect multiple Outlook calendars to Grok Bot · Connect multiple Outlook accounts to Grok · Best AI email assistants
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."
