How to Connect Multiple Outlook Calendars to Grok
xAI does not document a second Microsoft account for Grok, and documents somebody else’s calendar as out of reach. The connector itself is self-serve at grok.com/connectors, carries no plan gate, and writes to your own calendar from the first Accept click. Several calendars inside one account are probably fine but undocumented. Connect each Microsoft identity to Carly and one conversation reaches all of them. Carly holds your Google calendars and every mailbox on both sides in the same place, so this setup covers the rest of what you own.
One orientation note. “Grok” now names three products: the consumer assistant at grok.com and in the mobile apps, Grok Bot for Slack and GitHub, and the Grok API. This page is about the first. Grok Bot has its own connectors and its own rules, and xAI’s own FAQ says it is not the same product as Grok on grok.com.
What one conversation can do afterwards
- Check every connected calendar before proposing a time.
- Compare two Microsoft accounts in one question.
- Book on the account that owns the meeting.
- Move or decline in the correct calendar.
- Reach a calendar someone else shared with you.
- Keep the routing running when you are not in the chat.
Nothing is merged. Each account stays separately authorized, and Carly keeps them individually addressable.
Outlook Mail and Outlook Calendar are two connectors
This is the single most common reason people think the calendar connector is broken. xAI’s connector documentation opens by stating that Outlook Mail and Outlook Calendar “are connected as separate connectors, each with its own OAuth sign-in and permissions.” Connecting the mail half gives Grok your mailbox and nothing else.
In the interface the two entries are named differently, which is easy to miss. The mail connector appears as Outlook. The calendar connector appears as Outlook Calendar. If you asked Grok what your Thursday looks like and it drew a blank, you almost certainly connected Outlook and stopped.
The plan gate that catches OneDrive and SharePoint does not apply here
Worth saying plainly, because it is a real point in Grok’s favour and it is easy to assume otherwise. Two of xAI’s Microsoft connectors are restricted: the OneDrive and SharePoint documentation pages each open with the line that they are available on Grok Business and Enterprise plans only. No other connector page carries that banner, and the Outlook page does not. The connector index states that connectors are available to all Grok users.
So Outlook Calendar is genuinely available on a personal consumer tier, at no extra cost, set up in about a minute. That is more than several rivals offer for a Microsoft calendar.
Two gates that are not plan gates still exist. On Grok Business and Enterprise a team admin has to provision the connector in the cloud console first, which needs Team Read-Write permission. And separately, xAI notes that some organizations require an Azure AD administrator to approve application permissions before users can sign in at all, which surfaces as a “need admin approval” error.
Which verbs are documented, and the two that are not
xAI lists five capabilities for Outlook Calendar: searching events by date range and keyword, viewing event details including attendees, location and body, checking availability across multiple attendees, creating and updating events with attendees, location, recurrence and reminders, and RSVP as accept, decline or tentative with optional comments.
Three of those beat the Google Calendar connector on the same site. xAI’s Google Calendar page carries no attendee language on create at all, describes availability as plain free/busy lookups rather than availability across multiple attendees, and does not mention RSVP comments. On top of that, the permission model is different: Google Calendar’s scope table has a “when requested” column and the page says the tiered model starts read-only, with write enabled progressively by an organization’s administrators. Outlook Calendar’s table has no such column. It requests Calendars.ReadWrite at the single Accept, so write is live immediately. Microsoft’s Graph permissions reference lists that delegated permission as needing no admin consent, which matches.
Two things run the other way, and they matter more here than the wins.
There is no documented verb that lists your calendars. The Google Calendar page documents “list calendars the account has access to.” The Outlook Calendar page documents nothing equivalent. That is the whole spine of the equivalent Google guide, and it is missing on the Microsoft side, so the reassuring claim that all six of your calendars are enumerated automatically cannot honestly be made about Outlook.
The scope is more encouraging than the verb list. Microsoft describes delegated Calendars.ReadWrite as full access to user calendars, plural, covering events in the signed-in user’s calendars rather than only the default one. So the secondary calendars sitting inside your connected mailbox are almost certainly reachable. Treat that as an inference from the scope rather than a documented feature, and test it before you build anything on it, because a granted scope is not the same thing as an exposed action.
Delete is not a documented verb. The scope permits deleting events and xAI’s own description of Calendars.ReadWrite says so, but the capability list stops at create and update. Do not plan on Grok cancelling anything.
A second Microsoft account is undocumented. Someone else’s calendar is not.
These are two different questions with two different answers, and the mail connector will mislead you if you conflate them.
On a second Microsoft account, xAI is silent. Nothing states whether adding Outlook Calendar twice attaches a second identity, replaces the first, or refuses. Nowhere in xAI’s documentation is a second account discussed for any connector. That is genuine silence rather than a documented refusal, and the difference is worth respecting: try it if you want to, and expect no support for whatever happens.
Note what the calendar section does not say. The mail half of the same page ends its permission table with an explicit sentence, that Grok can only access the mailbox of the signed-in user. The calendar half has no equivalent line. So the flat “no” that applies to multiple Outlook mailboxes is not the calendar answer.
On someone else’s calendar, xAI is not silent. The privacy section of the same page states that Outlook permissions are delegated to the signed-in user and that “Grok can only access your own mailbox and calendar, not those belonging to other users.” That is a documented limit, not a gap.
The missing scope is why sharing a calendar in does not work
For Google Calendar, the standard workaround is to share the second account’s calendar into the account you connected, and lean on the phrase “has access to” being broader than “owns.” On Outlook that workaround fails, and the reason is specific enough to be worth knowing.
Microsoft ships a separate delegated permission for exactly this case. Its Graph permissions reference lists Calendars.ReadWrite.Shared, described as read and write user and shared calendars, allowing an app to create, read, update and delete events in all calendars the user has permission to access, and it states that this includes delegate and shared calendars. It requires no admin consent, so any app can ask for it.
Grok does not ask for it. The documented scope list for Outlook Calendar is Calendars.ReadWrite, User.Read and offline_access. The narrower one.
Two vendors’ documentation agreeing is strong evidence, and it lines up with xAI’s own privacy wording about calendars belonging to other users. This is documents agreeing rather than a live test, so treat it as such. The practical read is that a calendar shared into your connected account from a second Microsoft account is outside what Grok asked permission to see, and sharing harder will not change that.
What survives natively is narrower and still useful: additional calendars you create inside the connected mailbox are your own calendars, and they sit within the scope Grok did request. If the goal is separating client work from internal work under one identity, do it with extra calendars in one account rather than with a second account.
One more nuance on account types, in Grok’s defence and against it. xAI’s documented sign-in is a Microsoft work or school account. Microsoft’s own reference says Calendars.ReadWrite is available for consent in personal Microsoft accounts, so the exclusion of Outlook.com addresses is xAI’s product decision rather than a platform limitation. That is an inference about intent, not a documented statement, and it means the restriction could move.
Nothing fires when the calendar changes
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.
Be precise about what that leaves for a calendar. Nothing fires when an event is created, moved or cancelled. An invitation usually arrives as mail, so an email trigger catches an invite indirectly on SuperGrok, but a colleague dragging your Thursday review into Friday produces a silent calendar update and reaches nothing.
The gap is visible in xAI’s own marketing. Its Automations announcement shows a morning brief whose output reads “2 calendar conflicts, 4 emails worth replies” and, on another run, that a deadline moved to Friday. So xAI advertises calendar-conflict detection, and it runs on a clock. A conflict created at 9pm waits for the 8am run.
The real native pattern is worth using anyway. Instructions can point at a connector directly: type @ in an automation’s instructions to mention Outlook Calendar and Grok uses it on every run. Set a weekday schedule, ask for conflicts and unconfirmed invitations, and you get most of the value a trigger would have given you, one batch late. Watches also expire, and the interface asks you to reconnect a connector to keep receiving events for an automation, so check yours after any password or tenant change.
1. Sort your case
| What you have | Native path in Grok |
|---|---|
| One Microsoft account, default calendar | Yes, documented |
| Several calendars inside that one account | Not documented, but within the requested scope |
| Creating and updating events, with attendees | Yes, from the first Accept |
| Deleting or cancelling an event | Not documented |
| A calendar shared in from a second Microsoft account | Outside the scope Grok requests |
| Two separate Microsoft accounts at once | Not documented either way |
| A personal Outlook.com address | Documented sign-in is work or school only |
| Reacting when an invite or a change lands | Email triggers only, SuperGrok only |
2. Connect Outlook Calendar in Grok
- Go to grok.com/connectors on the web, or Settings then Connectors on iOS and Android.
- Click New Connector.
- Select Outlook Calendar. Selecting Outlook connects mail instead.
- Sign in with your Microsoft work or school account.
- Review the requested permissions and click Accept.
- On Grok Business or Enterprise, ask an admin to provision the connector in the cloud console first.
Read the consent screen carefully, because its wording is gentler than the grant. Grok describes this connector as giving it access to search your calendar, and offers to check today’s schedule, find upcoming events and get meeting details. The permission you are approving is Calendars.ReadWrite, which covers creating, updating and deleting events. Nothing about that is hidden, but the screen talks about reading and the scope includes writing, so approve it knowing which one you granted.
The retention position is clear and better than average. xAI states that it does not use your Outlook calendar data for model training, that conversations using the connector do not result in your calendar data being stored on xAI servers, and that Grok searches Outlook Calendar in real time when you ask rather than keeping a copy.
3. Test the secondary calendar before you trust it
This step exists because the calendar-list verb is missing, so you are verifying an inference rather than a feature.
- In Outlook, pick one event that sits on a non-default calendar inside the connected mailbox.
- Note its exact title, date and start time.
- Ask Grok about that specific day and read what it returns.
- Ask it directly for the details of that event by title.
- If it finds the event, secondary calendars in the connected mailbox are reachable for you.
- If it does not, treat the connector as covering the default calendar and plan accordingly.
Do this before any scheduling instruction. An assistant that silently sees one calendar out of four will confidently tell you an hour is free.
4. Connect each Microsoft account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Outlook and click Connect.
- Authorize the first Microsoft identity and confirm the address that appears.
- Repeat for every other account, using a private window if Microsoft preselects the previous login.
- Confirm each connection in the list before you rely on it.
Tenants approve independently, so one company’s administrator declining does not affect the others. Personal Outlook.com addresses are accepted, which covers the case Grok’s documented sign-in path excludes. Unlimited connected calendars are included, so the number of Microsoft accounts does not change what you pay.
5. 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.
6. Test each account, then both at once
One account per prompt until routing is reliable:
On the calendar for
fictional.marcus.webb@volvo.com, list everything booked next week and flag anything after 6pm.
On the calendar for
fictional.marcus.webb@ikea.com, find the next free 45 minutes that is not adjacent to another meeting.
Then the question that needs two real connections rather than a sharing trick:
Compare the Volvo and Ikea example calendars for next Tuesday and list every hour genuinely free on both, naming the account each conflict comes from.
7. Reuse this routing prompt
Treat
fictional.marcus.webb@volvo.comas Main Company andfictional.marcus.webb@ikea.comas Client. Always say which account and calendar you are writing to before creating, updating or declining anything, and never write to a calendar I have not named.
Then name the target in each action:
Book the supplier review on Main Company for Thursday morning, invite the two names on that thread, and block travel time on Client.
Grok versus Carly on Outlook Calendar
| Need | Grok | Carly |
|---|---|---|
| Free connector on the entry tier | Yes, no plan gate | Yes |
| Create and update events with attendees | Yes, documented | Yes |
| Write enabled at first sign-in | Yes | Yes |
| List the calendars in the account | Not documented | Yes |
| Delete or cancel an event | Not documented | Yes |
| See a calendar shared in from another account | Outside the requested scope | Yes |
| Hold two Microsoft accounts as separate connections | Not documented | Yes |
| A personal Outlook.com address | Work or school documented only | Yes |
| Act when an event is created or moved | No calendar trigger | Yes |
Grok’s Outlook calendar connector is free on a consumer tier and creates events with attendees, recurrence and reminders on the account you connect, documented in more detail than its Google Calendar equivalent. It holds that one account, and nothing starts when an invite arrives.
Carly is built for the rows underneath. It authorizes per identity, so two Microsoft accounts sit side by side as separate connections and one question can span both without anyone granting anyone else permissions in Outlook. It enumerates the calendars it can see rather than leaving you to test for them, it will cancel as well as create, and it fires on the event instead of on a schedule: the invitation lands, the clash is caught, an alternative goes out before you have opened anything. If a Microsoft tenant of yours needs a route the standard connection does not cover, the API path is available and worth a conversation.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Outlook.
Quick fixes
| Problem | Fix |
|---|---|
| Connected Outlook, Grok cannot see the calendar | They are separate connectors; add Outlook Calendar as its own New Connector |
| Grok sees one calendar but not the others in the account | Undocumented territory; run the single-event test in step 3 and treat the result as your answer |
| Grok will not delete or cancel an event | Delete is not in xAI’s documented capability list, even though the scope allows it |
| A shared calendar from another account never appears | Grok requests Calendars.ReadWrite, not the Calendars.ReadWrite.Shared permission Microsoft provides for shared and delegate calendars |
| Sign-in fails with “need admin approval” | An Azure AD administrator has to consent to the xAI Grok application first |
| The connector is missing on a work plan | On Business and Enterprise an admin must provision it in the cloud console, which needs Team Read-Write |
| A personal Outlook.com address is rejected | Expected; the documented sign-in is work or school, so connect that address to Carly instead |
| An automation stopped firing | The interface asks you to reconnect a connector to keep receiving events; re-authorize it |
Frequently asked questions
Does Grok work with Outlook Calendar?
Yes. Outlook Calendar is a built-in connector at grok.com/connectors, separate from the Outlook mail connector, with its own sign-in. It carries no plan gate, unlike the OneDrive and SharePoint connectors, so it is available on consumer tiers. On Grok Business and Enterprise an admin provisions it first.
Can I connect two Microsoft accounts to Grok?
xAI does not document it either way. Nothing states whether a second Outlook Calendar connection adds an identity, replaces the first or fails, so there is no supported answer to plan around. Carly holds each Microsoft identity as its own connection if you need both in one conversation.
Will Grok see a calendar someone shared with me?
Not according to xAI’s own wording. The connector page states that Grok can only access your own mailbox and calendar, not those belonging to other users, and Grok requests Calendars.ReadWrite rather than the Calendars.ReadWrite.Shared permission Microsoft provides for shared and delegate calendars.
Can Grok invite people to an event it creates?
Yes, and this is where the Outlook connector is stronger than the Google one. xAI documents creating and updating events with attendees, location, recurrence and reminders, and checking availability across multiple attendees, none of which appears on its Google Calendar page.
Does Grok react automatically when my calendar changes?
No. Schedules run on a clock for everyone, and email triggers watch the inbox on SuperGrok, so an invitation arriving as mail is caught indirectly. Nothing fires when an event is created, moved or cancelled.
Related: Multiple Outlook accounts in Grok · Multiple Google Calendars in Grok · Grok connectors · Multiple Outlook calendars in Copilot · Outlook 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."
