THE LOGS

LOG 010.5: Connecting OpenClaw to Microsoft Graph and Bringing Nine Online

This is Part 5 of the Nine / 9OS series — the final entry. Parts 1–4 built the infrastructure foundation, the M365 identity layer, and the 9OS workspace. This entry wires everything together: Graph API access, Nine's identity file, confirmation that the inbound webhook delivery via Cloudflare Tunnel (built back in LOG 010.2) is still live, and the live end-to-end test that confirms Nine is operational inside the Paragon9 M365 environment.

LOG 010.3: Setting Up a Dedicated M365 Identity for Nine

This is Part 3 of the Nine / 9OS series. Part 1 covered standardizing OpenClaw as a headless systemd service on a minimized Ubuntu Server. Part 2 covered connecting it to Microsoft Teams. This entry builds the identity layer — the M365 account, the dedicated static IP, and the access controls that lock Nine to exactly one machine.

LOG 010.2: Connecting OpenClaw to Microsoft Teams on a Headless Linux Server

This is a companion entry to the Nine / 9OS series. The series up to this point established the systemd service topology and the M365 identity layer. This entry builds the bot infrastructure: the Azure App Registration, the Cloudflare Tunnel for inbound webhook delivery, and the Teams app manifest that brings OpenClaw online as a bot you can DM and channel-message from anywhere in your tenant.