Getting Started
Getting Started
Connecting a customer’s Microsoft 365 or Google Workspace tenant to Hal takes one of three methods. Each one produces the same end-state credentials — pick whichever fits your operation.
Pick a method
Tell Hal in chat what you want; Hal walks the steps and runs the API calls on your behalf. One flow covers both M365 and Google Workspace. No clicking through the customer-side admin portals.
Run an open-source PowerShell script that does the same API calls as the assisted flow, but on your machine. Audit the source before you run it. Picks per platform inside.
Click through the customer’s Azure / GCP / Workspace consoles yourself. Use this path if you’d rather drive the admin portals by hand. Picks per platform inside.
The three methods are alternatives, not stages. You only need one.
Each path produces the same Azure app registration / Google Workspace
DWD authorization at the end.
Universal prerequisites
A couple of Microsoft-side toggles aren’t exposed via API, so neither path can flip them on for you. Hal detects when they’re missing and links here.
After credentials are issued
Once you’ve completed any of the three methods, the configured tenant lands in your MSP portal as a paused source. Activating it for ingestion is the last step before logs start flowing.