Skip to main content

Overview

OneCLI connects AI agents to Microsoft OneNote through Microsoft’s OAuth flow. Agents can read notebooks, sections, and pages, create new pages, and edit existing content. The gateway injects OAuth credentials into requests to the Microsoft Graph API automatically.
On self-hosted OneCLI, Microsoft OneNote needs your own Microsoft app first. See Self-hosted.

Setup

1

Go to Connections

Open the OneCLI dashboard and navigate to Connections > Microsoft OneNote.
2

Authorize

Click Connect Microsoft OneNote. You’ll be redirected to Microsoft to sign in and authorize OneCLI. Review the requested permissions and click Accept.
OneCLI connect window for Microsoft OneNote on Cloud, showing the Connect to Microsoft OneNote button.

The Microsoft OneNote connect window on OneCLI Cloud.

3

Verify

After authorization, you’ll be redirected back to the dashboard. The connection will show as Connected with your Microsoft account email.

Self-hosted: use your own Microsoft app

Skip this section on OneCLI Cloud. It’s only for self-hosted OneCLI without MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET set. One Microsoft app serves all four Microsoft apps in OneCLI, so you set it up once.

Set up your Microsoft app

Follow Self-hosted: use your own Microsoft app on the Outlook Mail page. If you already have one for another Microsoft app, it already works here. Then open Connections > Microsoft OneNote and select Connect Microsoft OneNote.
OneCLI Custom credentials card for Microsoft OneNote with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.

Custom credentials for Microsoft OneNote in OneCLI. The Microsoft app is shared, so the same client works here.

What agents can do

Use cases

  • Note-taking agents that create meeting notes from transcripts
  • Research agents that organize findings into structured notebooks
  • Agents that search across notebooks for relevant information
  • Content agents that create and update documentation in OneNote

Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches the Microsoft Graph API.