---
name: onenote-install-auth
description: >-
  Establish a least-privilege delegated Microsoft Graph connection for OneNote with tested consent and lifecycle controls. Use when registering or repairing OneNote authentication. Trigger with "set up OneNote auth", "register OneNote app", or "review Notes permissions".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<account-type> <tenant> <environment>"
version: 1.7.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, onenote, authentication ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live OneNote actions require network access, delegated authentication, and explicit approval"
title: onenote-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/onenote-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/onenote-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/onenote-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/onenote-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/onenote-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/onenote-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/onenote-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/onenote-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# OneNote Delegated Authentication Intake

## Overview

Establish a least-privilege delegated Microsoft Graph connection for OneNote with tested consent and lifecycle controls.. This workflow produces an auditable decision or artifact before any live action.

## Prerequisites

- Current first-party Microsoft Graph OneNote documentation and the selected integration's tested contract.
- Named identity, content, workload, security, and operations owners appropriate to the requested scope.
- Synthetic or approved non-production fixtures with secrets and real notebook content removed.

## Current Contract

The OneNote service-specific overview says app-only authentication is unsupported. Use a delegated authorization flow and choose Notes.Create, Notes.Read, or Notes.ReadWrite according to the operation; treat conflicting generic application-permission tables as documentation drift, not authorization to deploy client credentials. Recheck the dated evidence map before relying on mutable permissions, limits, SDK behavior, supported resources, or cloud availability.

## Authentication

Record app registration, account type, tenant, redirect URI, signed-in user, requested and granted delegated scopes, token-cache location, expiry, revocation, and reauthentication without storing secret values.

## Instructions

1. Classify the account as personal Microsoft or work or school and resolve the approved tenant boundary.
2. Register the application and exact redirect URI through the approved identity workflow.
3. Choose the minimum delegated Notes scope from the required read, create, or update operations.
4. Implement authorization-code or device flow appropriate to the client and protect token-cache material.
5. Run one synthetic read-only OneNote request and compare requested with granted scopes.
6. Document consent withdrawal, token-cache deletion, reauthentication, owner transfer, and production promotion.

## Tool Discipline

Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, delegated credentials, tenant or notebook content, consent, file transfer, deployment, writes, spend, sharing changes, or deletion.

## Approval Boundaries

Require the signed-in user for delegated consent and the tenant administrator when policy requires it. Require security approval for multitenant distribution, public clients, redirect changes, or production token storage.

## Error Handling

- Do not use client credentials or the default application scope for OneNote calls.
- Stop when generic permission metadata conflicts with the service-specific support statement.
- Never commit client secrets, tokens, or serialized caches.

## Output

Return the account and tenant model, app and redirect aliases, delegated scope matrix, consent evidence, synthetic check, lifecycle owners, and gaps. Identify assumptions, owners, expirations, and evidence gaps explicitly.

## Examples

- Onboard read-only access with Notes.Read and prove a write is unavailable.
- Revoke consent and verify the client enters a recoverable reauthentication state.

## Validation

Exercise and record these paths with expected and observed results:

- personal account
- tenant account
- consent denied
- wrong redirect
- revocation
- app-only rejection

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/onenote-install-auth/references/official-docs.md) — recheck dated sources before relying on mutable behavior.
- Treat observed tenant behavior as environment-specific evidence, never a universal OneNote guarantee.
