onenote-cost-tuning

# OneNote Cost Tuning ## Overview OneNote Graph API calls have no per-request cost — they are included in every Microsoft 365 E3/E5/Business license. However, rate limits create an effective ceiling that functions like a cost constraint: 600 requests per user per 60 seconds and 10,000 requests per app per 10 minutes at the tenant level. Exceeding these limits returns 429 errors with Retry-After headers, degrading user experience the same way budget overruns degrade service. This skill covers the practical optimization strategies that keep you well under those ceilings: metadata caching, JSON batch requests, delta sync, payload minimization with `$select`/`$expand`, and content deduplication. A naive integration that polls every user's notebooks every minute burns through the tenant limit in under 10 minutes. An optimized one handles thousands of users within the same budget. ## Prerequisites - Microsoft 365 license (E3/E5/Business) — OneNote API is included, no additional billing - Azure AD app registration with delegated permissions - Python: `pip install msgraph-sdk azure-identity` or Node: `npm install @microsoft/microsoft-graph-client @azure/identity` - Understanding of HTTP caching headers (ETag, If-None-Match) ## Instructions ### Licensing Model and True Cost | Component | Cost | |-----------|------| | OneNote API calls | Included in M365 license (no per-call charge) | | Rate limit: per user | 600 requests / 60 seconds | | Rate limit: per tenant | 10,000 requests...