Skip to content

[Feature]: Feature Request: Native Microsoft 365 integration (like gog for Google Workspace) #30023

@PrantikLamichhane

Description

@PrantikLamichhane

Summary

Currently OpenClaw has gog, a seamless Google Workspace
integration for Gmail, Calendar, Drive, Docs, and Sheets
that requires minimal setup.

There is no equivalent for Microsoft 365 users.

The Microsoft Graph CLI (msgraph-cli) was archived by
Microsoft in August 2025 and is being retired in 2026,
so it cannot be used as a solution.

Request: A native Microsoft 365 skill similar to gog that supports:

  • Outlook Mail (read, send, search)
  • Outlook Calendar (events, reminders)
  • OneDrive (files, documents)
  • Microsoft Teams (messages)
  • Word/Excel/PowerPoint documents

This would make OpenClaw accessible to the large portion
of professionals and businesses that use MS Workspace
instead of Google Workspace.

Suggested approach: Similar OAuth flow to gog simple
authentication without requiring users to manually set up
Azure app registrations, API permissions, or client secrets.

Current workaround requires:

  • Manually registering an Azure app
  • Configuring Microsoft Graph API permissions
  • Managing client secrets manually
  • Very technical not suitable for non-developer users

Problem to solve

Microsoft 365 users have no simple way to connect their
workspace to OpenClaw.

Google Workspace users get a seamless experience via gog —
one command, browser login, done. Microsoft 365 users have
no equivalent. The only available path requires:

  • Creating an Azure app registration manually
  • Navigating Microsoft's complex developer portal
  • Configuring API permissions and scopes manually
  • Generating and managing client secrets
  • The Microsoft Graph CLI (only viable workaround) was
    archived in August 2025 and is being retired in 2026

This creates a two-tier experience where Google users get
a polished, beginner-friendly integration while Microsoft
users face a technical wall that most non-developers
cannot navigate.

For OpenClaw to be a true personal AI assistant for
professionals and founders, it needs to work equally
well regardless of which workspace ecosystem the user
is in. Right now it doesn't.

Proposed solution

Build a native Microsoft 365 CLI skill (e.g. "mswork" or "m365")
that mirrors the gog experience exactly:

  1. SIMPLE AUTHENTICATION

    • Single command: mswork auth add [email protected]
    • Opens browser for Microsoft OAuth login
    • No Azure portal setup required from the user
    • No manual client ID, secret, or tenant ID configuration
    • OpenClaw handles the app registration behind the scenes
      (similar to how gog handles Google OAuth)
  2. CORE COMMANDS (mirroring gog structure)

    • mswork mail search "is:unread"
    • mswork mail read
    • mswork mail send --to --subject --body
    • mswork calendar list
    • mswork calendar events --days 7
    • mswork drive list
    • mswork drive read
    • mswork teams messages --channel
  3. INSTALLATION

    • Available via openclaw configure (same as gog)
    • Listed in ClawHub
    • Works out of the box after single auth command
  4. AGENT USAGE

    • Agent can call mswork commands exactly like gog commands
    • No extra configuration needed after initial auth
    • Credentials stored securely in local config

TARGET USERS:
Professionals, founders, and enterprise users who use
Microsoft 365 as their primary workspace instead of
Google Workspace.

Alternatives considered

No response

Impact

Affected users: All Microsoft 365 users attempting to integrate
their workspace with OpenClaw. This includes a large portion of
professionals, founders, and enterprise teams who use MS Workspace
as their primary productivity suite.

Severity: Blocks workflow — without native MS 365 integration,
OpenClaw cannot read emails, access calendar, or interact with
files for Microsoft users. Core agent functionality like morning
briefings, email summaries, and document context is completely
unavailable to these users.

Frequency: Always — this is a missing feature, not an intermittent
bug. Every Microsoft 365 user hits this wall immediately when
trying to connect their workspace.

Consequence:

  • Microsoft 365 users cannot use OpenClaw as a true personal
    assistant without their workspace connected
  • Current workaround requires Azure portal setup, app registration,
    API permissions configuration — too technical for non-developers
  • Microsoft Graph CLI (the only available workaround) was archived
    by Microsoft in August 2025 and is being retired in 2026
  • Effectively limits OpenClaw's addressable market to Google
    Workspace users only
  • Businesses and enterprises (who predominantly use MS 365)
    cannot be onboarded as clients without this feature
  • Service providers building on OpenClaw (like agencies) cannot
    offer their services to MS 365 clients

Evidence/examples

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions