onenote-reference-architecture

# OneNote Reference Architecture ## Overview OneNote notebooks live in three completely different storage backends — personal OneDrive, SharePoint team sites, and Microsoft 365 Groups — each with its own Graph API path, permission model, and behavioral quirks. Building an integration that "just works with OneNote" means handling all three locations, because users do not know (or care) where their notebook is stored. The API path `/me/onenote/notebooks` only returns personal notebooks; SharePoint and Group notebooks require different endpoints entirely. This skill maps the full architecture: storage locations, API paths, the object hierarchy (and its gotchas), and a service abstraction layer that normalizes all three locations into a single interface. ## Prerequisites - Azure AD app registration with delegated permissions (`Notes.ReadWrite` minimum) - Familiarity with Microsoft Graph API URL structure (`https://graph.microsoft.com/v1.0`) - For SharePoint notebooks: `Sites.Read.All` or `Sites.ReadWrite.All` permission - For Group notebooks: `Group.Read.All` or `Group.ReadWrite.All` permission - Python: `pip install msgraph-sdk azure-identity` or Node: `npm install @microsoft/microsoft-graph-client @azure/identity` ## Instructions ### System Architecture ``` ┌─────────────┐ ┌──────────────┐ ┌─────────────────┐ │ Your App │────>│ MSAL Auth │────>│ Azure AD │ │ (Client) │ │ (Delegated) │ │ Token Service │ └──────┬──────┘ └─────────────...