Getting Started
Before anything else
Connecting a customer’s Microsoft 365 or Google Workspace tenant to Hal is done in the portal chat, in one of two ways. With Hal-assisted onboarding, Hal creates the registration himself. Or you build the registration or service account yourself, as the manual and script pages describe, paste its credential into a box on Settings, and confirm it with Hal. The same pages show what the assisted flow creates in the customer’s tenant, so you can audit it.
Which page you need
Note
Universal prerequisites
A couple of Microsoft-side toggles aren’t exposed via API, so Hal cannot flip them on for you. He detects when they’re missing and links you to Audit Logging Prerequisites.
After the tenant is connected
Once Hal has stored a tenant’s credential, either way, the tenant lands in your MSP portal as a paused source. Activating it for ingestion is the last step before logs start flowing.
Your Anthropic API Key
Hal runs on your own Anthropic account, so you see every dollar. Set it up in the developer Console (not a Claude subscription), fund it, put guardrails on it, and hand Hal the key.
OpenAudit Logging Prerequisites (Microsoft 365 and Entra ID)
Hal automates everything he can, but two Microsoft-side capabilities need to be enabled in the customer’s tenant before sign-in and audit events can flow into Hal.
OpenHal-Assisted Onboarding
The fastest way to onboard a new MSP client. You ask Hal in chat, Hal walks through the steps, runs the API calls, and reports back.
OpenManual
Build the Microsoft 365 app registration or the Google Workspace service account yourself, step by step, and connect it by pasting its credential on Settings.
OpenOnboarding Tenants
You onboard every tenant through the portal chat, there’s no separate console or “add tenant” form.
OpenScript
Script-based token setup.
OpenSee what Hal surfaces on your own clients.
No deck. Ask us anything first. When you want to see Hal on your own tenants, we sign a short evaluation agreement and stand up your instance; you connect one tenant, Hal watches it for 14 days, and we walk you through what he found.
- 01You ask us your questions. No deck, no demo dataset.
- 02You sign a short evaluation agreement, and we stand up your own instance.
- 03You connect one tenant from your own admin console. Hal watches it for 14 days.
- 04We walk through what he found. Keep going month to month, or revoke the scopes yourself and stop.