Hermes BibleUnofficial Docs
← All docs Docs / Guides & Tutorials

Register a Microsoft Graph Application

The Teams meeting pipeline reads meeting transcripts, recordings, and related artifacts from Microsoft Graph using app only (daemon) authentication — no user si

Guides & Tutorials
Section
Guides & Tutorials
Source
hermesbible.com/docs/guides/microsoft-graph-app-registration

The Teams meeting pipeline reads meeting transcripts, recordings, and related artifacts from Microsoft Graph using app only (daemon) authentication — no user si

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Prerequisites
  2. Step 1: Create the App Registration
  3. Step 2: Create a Client Secret
  4. Step 3: Grant Graph API Permissions
  5. Required for transcript-first summaries
  6. Required for recording fallback (when a transcript is unavailable)
  7. Required for outbound summary delivery (Graph mode only)
  8. Not recommended
  9. Step 4: (Recommended) Scope the App with an Application Access Policy
  10. Step 5: Write the Credentials to Your Env File
  11. Step 6: Verify the Token Flow
  12. Rotating the Client Secret
  13. Next Steps

Section map

Prerequisites

Maps prerequisites to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 1: Create the App Registration

Maps step 1: create the app registration to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 2: Create a Client Secret

Maps step 2: create a client secret to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 3: Grant Graph API Permissions

Maps step 3: grant graph api permissions to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Required for transcript-first summaries

Maps required for transcript-first summaries to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Required for recording fallback (when a transcript is unavailable)

Maps required for recording fallback (when a transcript is unavailable) to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Required for outbound summary delivery (Graph mode only)

Maps required for outbound summary delivery (graph mode only) to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Not recommended

Maps not recommended to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Prerequisites, Step 1: Create the App Registration, Step 2: Create a Client Secret, Step 3: Grant Graph API Permissions, Required for transcript-first summaries. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: register, microsoft, graph, application, teams. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitGuides & Tutorials documentation

Use when you need orientation for register a microsoft graph application before applying exact upstream commands.

Verify firstPrerequisites

Open the source anchor for Prerequisites and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
  2. Start with the source section for Prerequisites; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Step 1: Create the App Registration if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page