Product
Everything an IT department would do — run through pre-approved workflows instead.
Handoff doesn't generate arbitrary scripts or hand out broad access. Pip, the in-app assistant, maps what you ask for onto a fixed set of Microsoft 365 workflows — and every one of them stops for your confirmation before anything changes.
The assistant
Meet Pip.
Pip speaks in plain English, first person, no jargon. Tell it what you need — "reset Amara's password," "Sarah starts Monday in Finance," "who can see the shared drive?" — and it either answers directly or proposes a plan. It never pretends to do something it can't; if a capability doesn't exist yet, Pip says so honestly rather than faking success.
The safety model
Plan → confirm → execute — structurally, not by promise.
This is the one property Handoff never relaxes: the AI model is never given a function that can change anything. Only read-only "propose a plan" tools are visible to it. The only thing that can trigger a real Microsoft 365 change is a human clicking Confirm on a plan card, which hits a separate, authenticated endpoint — completely decoupled from the conversation itself. There's no prompt injection or clever phrasing that gets around this, because there's no code path for the model to call an execute function directly, even if it wanted to.
Every step is disclosed
A plan built from a plain-English request shows exactly where each detail came from — what you said, a pattern from past hires, a policy you've set, or a sensible default. Nothing is silently guessed.
Undo, where it's honest
Reversible actions can be undone from the same run they came from. Irreversible ones (a password reset, a revoked session) are never offered a fake "undo" button.
The dashboard
Six screens, one health picture.
Everything Handoff can see and do lives in six places.
🏠
Home
An organisation health score, what's worth a look this week, and recent activity — the first thing you see, not a wall of menus.
◎
People
Every account, licence, and sign-in safety status in one place — onboard, offboard, or fix something with one click.
▣
Who sees what
Teams, shared mailboxes, drives, and connected third-party apps — with a live risk read on each one.
⚡
Automations
The built-in workflows (onboarding, offboarding, licence reports) plus any custom ones you've built, all running through the same confirm gate.
◷
History
Everything Pip has done, in plain English, with the reasoning behind it — not just a raw action log.
⚙
Settings
Team access, notification preferences, company policies, and the Microsoft 365 connection itself.
Key workflows
The things that actually eat an afternoon, automated.
- New starter → account, licences, and group memberships in one confirmed plan
- Leaver → sign-in disabled, sessions revoked, mailbox handed off, licences freed
- Idle licence cleanup → see who's sitting on an unused seat, remove it in one click
- Conditional Access → "Finance needs MFA" becomes a real policy, always created report-only first
- Enterprise app risk review → flags risky permissions, unverified publishers, and stale consent
- Office move / leave of absence → the less common HR events, handled the same structured way