Built for the teams who run Microsoft 365 for other people.

Who it is for

Managed service providers running Microsoft 365 for more than one customer — the technicians, administrators and owners who carry a book of customers and have to decide, every morning, which one to open first.

The workspace has four roles: owner, administrator, technician and viewer. The division of labour is deliberate and it runs through the whole product: HawkView reads; the technician acts in Microsoft’s own tools.

Why it exists

Multi-tenant Microsoft 365 work spreads the evidence thin. The records exist — sign-ins, directory audit, administrative change — but they sit behind a different portal for every customer, and comparing them means signing in again and holding the last one in your head.

HawkView collects those records into one place so the comparison can be made on a screen instead of from memory.

The part we care most about

A dashboard that cannot read something has two honest options: say so, or show a zero. Most of the engineering here is about taking the first option.

The rule the product is built around is written into its own source: never turn missing, stale, failed, unlicensed or concealed data into healthy empty data. A check that could not run reports that it could not run. A count that is a lower bound is shown as a lower bound. A comparison with Microsoft that could not be completed says so on the finding itself.

That is also why findings are described as investigation leads rather than verdicts. HawkView can tell you that an account was locked out after repeated failed sign-ins, and show you the events it counted. It cannot tell you whether that account is compromised, and it does not pretend to.

Who builds it

HawkView is built by a small team who run Microsoft 365 for other people. That is where the product came from: the views exist because the work needed them, not because a roadmap called for them. When you write to us, the reply comes from someone who works on the product — there is no sales desk in between.

It is in pilot. That is a statement about the operating model rather than a marketing stage — there is no production service level yet, some capabilities are switched off by default, and the Security page says which.

What it is not

HawkView does not manage, remediate or write customer Microsoft configuration. It does not replace Microsoft 365, Entra, Purview, a SIEM, a ticketing system or a backup product. It does not guarantee every dataset for every Microsoft licence or permission set.

And it does not yet provide a supported broad-production service level. The operating model is pilot-grade, and the Security page sets out what that means in practice rather than leaving you to find out.