How Microclaw Works

Side-by-side

One request. Both paths.

Every step Microclaw takes, you could do yourself — open Outlook, ask Copilot, copy the names, open Calendar, ask Copilot again. Microclaw is the assistant that does all of that in one sentence, without you leaving Teams.

The diagram below shows both paths: left column — no Microclaw, using Copilot directly in each app. Right column — with Microclaw.

"Find my 3 most urgent unread emails, draft a reply to each, and book a 30-minute meeting with each sender before end of day Friday."

No Microclaw

Shared infrastructure

With Microclaw

Part 1 — Email

Outlook

In Outlook, find Copilot. Type: "Find my 3 most urgent unread emails and draft a reply to each."

Teams

In Teams, find Microclaw. Type: "Find my 3 most urgent unread emails and draft a reply to each."

↘

↙

Your Microsoft 365 data

reads your inbox · same permission either way

↓

Microsoft's AI

sorts by urgency · drafts 3 replies

↙

↘

3 replies drafted — in Outlook ✓

← same result →

3 replies drafted. Still in Teams. ✓

You switch apps Copy the three senders' names. Close Outlook. Open Calendar. Find Copilot in Calendar. Re-explain who you want to meet, and when. Calendar Copilot doesn't know about the emails.

The bot already has the names. It moves to the calendar step automatically — no input needed.

Part 2 — Calendar

Calendar

In Calendar, find Copilot. Type: "Book 30-minute meetings with [name], [name], and [name] before Friday." You supply the names — Calendar Copilot doesn't have them.

Teams

Still in Teams, still Microclaw. Nothing new to type — it carries the context from Part 1 and books the meetings automatically.

↘

↙

Your Microsoft 365 data

reads calendars · checks availability

↓

Microsoft's AI

finds open slots · drafts invites

↙

↘

Meetings booked. You're in Calendar. ✓

← same result →

Meetings booked. Still in Teams. ✓

Next task: find the right app, find Copilot, start over.

Next task: just ask.

Copilot is genuinely good at both parts. The gap isn't the AI quality — it's everything the user has to do between them. The bot eliminates that entirely.

Your data

Where does your information go?

Three options: Microclaw Standard, Microclaw Self-Hosted, and Copilot on its own. All three use the same AI and pull from the same data — only the middle step changes. Follow any row across the columns to see exactly where the paths match and where they don't.

No Microclaw

Self-Hosted plan

Standard plan

You, in any Microsoft 365 appType your request to Copilot.

You, in TeamsType your request to Microclaw.

↓ Microsoft routes your request within the app

↓ Microsoft routes your request to your private server

↓ Microsoft routes your request to our servers

Copilot, in the appNo separate server. Copilot is built directly into the app — Microsoft handles this step internally.

Your private serverThis is where Microclaw runs, in your own Azure subscription. Microclaw receives your request and fetches what's needed from Microsoft — emails, calendar availability. Nothing is stored here. You control this server — we can't access it.

Our serversThis is where Microclaw runs. Microclaw receives your request and fetches what's needed from Microsoft — emails, calendar availability. Nothing is stored here.

↓ fetches your data from Microsoft

Your Microsoft 365 dataStored by Microsoft.

↓ data returned to Copilot

↓ data returned to your private server

↓ data returned to our server

Copilot, in the appCopilot receives the fetched data from Microsoft. Packages it with your original request and sends it to the AI.

Your private serverMicroclaw receives the fetched data from Microsoft. Packages it with your original request and sends it to the AI. Nothing stored.

Our serversMicroclaw receives the fetched data from Microsoft. Packages it with your original request and sends it to the AI. Nothing stored.

↓ Copilot sends data to the AI

↓ server sends data to the AI

Microsoft's AIReads your data, drafts responses.

Microsoft's AIThe same AI as Copilot. Reads your data, drafts responses.

↓ AI response back to Copilot

↓ AI response back to your private server

↓ AI response back to our server

Copilot, in the appCopilot receives the AI's response and surfaces the result — draft replies and booked meetings — directly in the app.

Your private serverMicroclaw receives the AI's response and carries out the actions — books the meetings, assembles the draft replies — then delivers the result to you in Teams.

Our serversMicroclaw receives the AI's response and carries out the actions — books the meetings, assembles the draft replies — then delivers the result to you in Teams.

↓ result back in the app

↓ result delivered to you in Teams

You, in the same appDraft replies and booked meetings — still in Outlook or Calendar

You, in TeamsDraft replies and booked meetings

From start to finish, everything stays inside Microsoft. This is what you already trust every time you open Outlook. The Self-Hosted plan matches this path exactly — the only difference is your company controls the coordination instead of Microsoft.

Your data never leaves Microsoft's network — same as Copilot. The difference from Standard: no outside server. Everything runs inside Microsoft's network, in a space your company controls.

Our servers are the only stop outside Microsoft — just for the seconds your request takes to process. Nothing saved. The AI, the data, and the result are identical to the other two columns.

What happens when you ask
Microclaw something.

One request. Both paths.

Where does your information go?

One request. Every app.
Still in Teams.

What happens when you askMicroclaw something.

One request. Both paths.

Where does your information go?

One request. Every app.Still in Teams.

What happens when you ask
Microclaw something.

One request. Every app.
Still in Teams.