← home

You’re handing us the keys.
Here’s how we earn that.

A tool that can read your company’s accounts, mail settings and devices — and change them — should have to show its work. This page is the whole trust story in plain English: what we can touch, what stops us, what gets written down, and what stays locked no matter who asks.

the five doors

Nothing changes without a yes.

Every change — a license swap, a password reset, a device wipe — walks through the same five doors, gated in proportion to how much it could break.

1

See it first

The exact before-and-after, spelled out — on the real, current data.

2

Type to confirm

You type the name of what's changing. No accidental clicks, ever.

3

Second opinion

A different admin must approve what you proposed. Routines can require two sign-offs.

4

On the record

Who asked, who approved, what changed, when — written down, permanently.

5

Undo button

Most changes can be rolled back for 30 days. It tells you honestly when one can't.

And some doors stay locked no matter what: Unify365 will flat-out refuse to remove your last administrator or lock you out of your own company — even if you ask it to. No change it offers will disable, sign out or strip access from someone holding Global Administrator; no change may leave your company with fewer than two administrators; and no sign-in rule takes effect with every administrator shut out.
Plans & approvals, from the product design — the five doors
The five doors, as designed — steps, simulation, rollback, typed approvalfrom the product design
built to be trusted

Careful by design.

Starts look-only

When you connect, Unify365 can only read. The ability to change anything is a separate permission you grant later — if and when you’re ready, one area at a time.

Everything on the record

Every question asked and every change made is written down — who, what, when, and what it looked like before. Your records, exportable anytime, ready for any audit.

The 30-day undo

Changed your mind? Most changes roll back with one click for 30 days. And when something genuinely can’t be undone, Unify365 says so before you approve it — not after.

It even watches itself. Unify365’s own monitoring flagged a risky admin setup in our company — and separately spotted two forgotten app accounts still holding live keys. It found both on its own, told us plainly, and confirmed when we fixed them. That’s the product we’re selling you.

for your security reviewer

The questions they’ll ask. Answered straight.

What access does Unify365 get when we connect?
Read-only access, granted through Microsoft’s own consent screen — you see exactly what before you approve. The ability to change anything is a separate, explicit consent you grant later, if you choose to. Dropping a permission never breaks the product; the features it powered simply switch off and say why.
Could another customer ever see our data?
Which company you’re in comes from your sign-in itself — never from anything a request can claim. Tests that try to cross that boundary run automatically on every single release build.
Who can approve changes?
People you name, with roles you set — viewers can look, helpdesk can propose, approvers approve. Whoever proposes a change cannot be the one who runs it (when your company has more than one admin), and routines can require two different people. The rules are enforced at the moment a change is proposed, again when it runs, and again on any undo.
What gets logged, and can we export it?
Every question asked of your data and every change proposed, approved, run, or undone — who, what, when, and the before/after. It’s your record: export it anytime, or stream it continuously into the security tools you already run.
What can it never do?
Remove your last administrator. Lock you out of your own company. Every change Unify365 offers is refused outright when the person it touches holds Global Administrator. A change that would leave your company with fewer than two administrators — including taking a role assignment away, or deleting a group that carries the role — is refused as well, and refused just the same when Unify365 cannot prove another administrator would remain. A sign-in rule cannot take effect with every administrator shut out. And it will not act without a person’s yes unless you explicitly armed a routine — arming one is itself a recorded, deliberate act. These aren’t policies; they’re refusals built into the machinery, and they hold even if the person asking is us.
Where do credentials live?
Your sign-in stays with Microsoft — Unify365 never sees or stores your password. The keys the product itself uses live in encrypted, managed secret storage, never in code, and never on this website.

Bring your security reviewer.
We like those calls.

Unify365 is in development. Join the waitlist and you’ll hear from us first when it’s ready for your company.
Look-only until you decide otherwise.