Microsoft Graph Webhook Listener
Microsoft Graph Webhook Listener
Start with meaning, then move to detail.
This lesson explains Microsoft Graph Webhook Listener as part of operating Hermes with explicit security boundaries. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Prerequisites, Quick Start, Configuration, then verify failure modes and version compatibility.
You only need to know which files and accounts the agent may access.
A clear outcome before you read.
- Understand Microsoft Graph Webhook Listener without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Approval & sandbox
- Approval pauses a sensitive action before execution; sandboxing limits impact if something goes wrong.
Receive Microsoft Graph change notifications (meetings, calendar, chat, etc.) in Hermes
What does the source say, and in what order?
- 01Prerequisites
Start here to understand the core idea or structure.
- 02Quick Start
Read this after the foundation, then connect it to the previous step.
- 03Configuration
Read this after the foundation, then connect it to the previous step.
- 04Security Hardening
Read this after the foundation, then connect it to the previous step.
- 05clientState is the primary auth check
Read this after the foundation, then connect it to the previous step.
- 06Source-IP allowlisting (production deployments)
Read this after the foundation, then connect it to the previous step.
- 07HTTPS termination
Read this after the foundation, then connect it to the previous step.
- 08Response hygiene
Read this after the foundation, then connect it to the previous step.
- 09Troubleshooting
Read this after the foundation, then connect it to the previous step.
- 10Related Docs
Finish here to verify the result and special cases.
Copy only after you understand the effect.
platforms:
msgraph_webhook:
enabled: true
extra:
host: 127.0.0.1
port: 8646
client_state: "replace-with-a-strong-secret"
accepted_resources:
- "communications/onlineMeetings"MSGRAPH_WEBHOOK_ENABLED=true
MSGRAPH_WEBHOOK_PORT=8646
MSGRAPH_WEBHOOK_CLIENT_STATE=<generate-with-openssl-rand-hex-32>
MSGRAPH_WEBHOOK_ACCEPTED_RESOURCES=communications/onlineMeetingshttps://ops.example.com/msgraph/webhookRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.