Grok Bot Integrates with Microsoft 365, Sparking Industry Discussion

Grok Bot can now work for you.

On September 1, the Grok Bot quietly announced a message that sent shockwaves through the tech community:

The Grok Bot can now directly connect to your Microsoft account to read, write, and perform actions. With the new plugin, your AI assistant can seamlessly integrate with Outlook, Calendar, and OneDrive.

A few hours later, Musk retweeted with just one sentence: Grok Bot has been upgraded.

No launch event, no demo video. But behind this post are real, tangible changes:

The always-on AI employee, Grok Bot, has now been granted access to your email, calendar, and cloud storage. It can send emails on your behalf, reschedule meetings, and upload files to OneDrive.

The comment section quickly became lively.

Statements like “Copilot is panicking” and “Microsoft has opened the door to Musk” have rapidly gone viral.

However, reviewing xAI’s official documentation reveals one thing: as early as May this year, the Outlook and OneDrive connectors were already listed in Grok’s documentation.

In other words, Grok has been able to read and write to Microsoft accounts for over three months.

What’s new in this update?

The answer lies in the word "Bot": the permissions have never changed; it's the person holding the key that has.

First, break down "read, write, act" down to the action level to see exactly how far the new plugin can go.

The Outlook email plugin has the most comprehensive features.

Searching emails, reading body text and attachments are basic functions; it can also draft, send, reply all with one click, and forward; even organizing emails by moving them to other folders, it can do that for you too.

Files generated by Grok can also be directly attached to drafts.

The most critical permissions requested in the background are Mail.ReadWrite and Mail.Send, along with offline_access, which means you won't need to log in repeatedly after granting authorization once.

The calendar is a separate connector with separate authorization.

It can look up events by date, check multiple people’s availability, create and modify meetings with attendees and recurrence rules, and even accept, decline, or tentatively respond on your behalf.

OneDrive is getting a discount.

The official documentation lists three tasks: browsing folders, reading documents, and uploading content generated by Grok. To perform full-text searches on files in OneDrive, you need to connect an additional SharePoint connector.

It is only available to Grok Business and Enterprise accounts; personal accounts are not included in the official integration process.

So, more accurately: you can receive and send emails, organize them, create and modify calendars, respond to calendar events, and view and upload files to cloud storage.

Email and calendar provide a key; cloud storage is only half a key.

Since the connector was ready in May, why is Musk announcing it now?

In May, these connectors served traditional chat scenarios.

Ask Grok.com, “What did the supplier’s email last week say?” and it will check your Outlook and read the result to you.

Conversation ended; no one touched the permissions.

On August 11, Grok Bot entered early testing in a completely different form.

It doesn’t live in the chat box—it resides on a dedicated cloud computer equipped with a browser, file system, and terminal. It can log into websites, save sessions, run tasks in parallel, and continue operating even after you close your laptop.

This update essentially turns the May batch of connectors into plugins on this cloud computer.

Thus, the same set of permissions has changed in usage.

Previously, it was “Check my emails for me”; now, it reads through all your emails overnight, determines which ones need replies, drafts responses, and saves them in your drafts folder, waiting for your approval in the morning.

The executor has changed from a chat box waiting for your questions to an employee who never clocks out.

In this transformation, Microsoft's role is the most subtle.

The Grok Bot integrates precisely with the core Microsoft 365 scenarios of Copilot.

Six days ago, Grok 4.6 was announced to be available on Microsoft Foundry, hosted and sold by Azure.

Some people linked these two events together, joking that Microsoft is giving Musk a green light.

But these two lines are technically completely independent.

Foundry is where enterprises buy models—it has nothing to do with you.

The Outlook plugin follows Microsoft’s standard authorization process, which is open to all third parties—just like granting login access to any app. The key is handed over when you personally click “Agree,” not when Microsoft does it for you.

Microsoft didn’t help Grok attack its own products; this is simply the cost of an open platform: when you leave your door open, people will always walk into your core territory.

In contrast, Google is much more cautious.

The Google Account help page clearly states that the following situations will prevent login:

The browser is controlled by automation software rather than a human, or is embedded within another application. The browser running on Grok Bot's cloud computer happens to fall right on this line.

Some users encountered a blocking prompt when logging into Google via the Grok Bot.

But this does not mean that Google has banned Grok.

The xAI official documentation still lists OAuth connectors for Gmail, Google Drive, and Google Calendar.

Google blocks "bots logging in like humans in a cloud browser" and allows "users logging in via official OAuth authorization."

Two giants, two paths:

Microsoft uses standard authorization to let you in, while Google constantly checks whether it's really a person knocking.

Grok Bot isn't the only one crowding into these three entry points.

Microsoft’s own Copilot already resides within Outlook, and at the Build conference, it introduced Autopilot 'Scout,' a feature designed to permanently monitor emails in Outlook—fighting on home turf.

Anthropic’s Microsoft 365 connector, available in the full plan, can read SharePoint, OneDrive, Outlook, and Teams.

Actions such as sending emails, updating calendars, or creating files require approval from the tenant administrator and are restricted to work accounts only—personal email addresses like @outlook.com cannot be connected.

OpenClaw is open-source and follows a community-driven approach.

ClawHub features numerous Microsoft Graph skills; the official Outlook skill has been downloaded over 6,600 times, and Microsoft 365 skills covering OneDrive have also seen thousands of downloads. However, users must independently register applications in Azure and manage their own tokens.

All three are trying to embed their agents into your Microsoft account.

What sets Grok Bot apart this time is that it ties together "persistent cloud computers" and "first-party plugins."

Later that day, Musk added: “Grok Bot runs 24/7 on its own cloud computer, so whether you turn your laptop off or not doesn’t matter.”

No need to set up Azure yourself or keep your computer on—authorize once, and the bot runs automatically in the cloud.

Although the scope of delegated permissions is limited to individual accounts, these accounts contain actual business communications; accidentally sending an email or deleting an important meeting can result in real losses.

Fortunately, xAI left approval points in the product.

In the official demo, a bot called Inbox Manager finishes running at night and leaves you a message in the morning: “Inbox cleared, 5 drafts saved for you to review.”

Another bot, called Sales Outbound, better illustrates the issue.

Give it this task: Screen potential leads from a Google Sheet, conduct online research, and enrich the data using Hex, Sumble, and Salesforce; then draft email and LinkedIn outreach sequences in my voice.

It ran overnight and returned a list: 52 customer accounts, 3 similar customer segments, 4 recently contacted individuals manually skipped, 36 drafts queued up, 0 sent.

Take a quick look, reply with “The first 10 look good—send them, and set this up as a weekly routine,” and only then will it be sent, along with saving this task as a weekly routine.

The final decision always rests in your hands.

For the average person, entering the agent era raises four more pressing questions than model benchmark scores:

Before it was sent, did it ask me for confirmation? Can I check what it did? Can I instantly revoke access if I want to reclaim my key? If it sent the wrong thing or deleted the wrong thing, can it be recovered?

Email, calendar, and cloud storage are the three fundamental entry points for knowledge work.

The first one to obtain authorization will secure the default position in the workflow.

The AI employee’s “onboarding process” is hidden in the authorization button you click without a second thought.

Before clicking, make sure you understand exactly what you're giving up. Amid the excitement, don’t lose this clarity.

Reference materials:

https://x.com/elonmusk/status/2094577304647164374

https://docs.x.ai/grok/connectors/outlook

https://x.com/bot/status/2094543253811183943

This article is from the WeChat public account "New Intelligence Yuan," authored by ASI Revelation, edited by Yuan Yu.