What TrueRock does

Find it. Fix it. Prove it. For every client tenant.

TrueRock OutCrop assesses each client’s Microsoft 365 in layers, opens each finding on its curated runbook where TrueRock has one, and has agents prepare those fixes for your approval and check that they held. Then it shows the client what you fixed.

On the Microsoft 365 your clients already own

Works on every plan from Business Basic up, alongside the Copilot and E5 your clients may already have. What each layer shows follows the client’s plan, and where a plan carries richer signals and the client grants access, TrueRock reads them into the same Overview and the same runbooks.

Microsoft gives you the platform. TrueRock finds what needs fixing in it, hands you the runbook, and checks the fix held.

The Overview

Every client tenant, in 9 layers.

Each client opens on one Overview. Each layer is a tile with its findings, a Visual view, and a drawer for every finding behind it.

Overview

One Overview per client, in layers.

Each client tenant opens on one Overview: a tile per layer, worst first, each opening on the findings behind it.

  • Identity, Devices, Threats, Data & sharing, Email, AI agents, Licensing, Baseline and Compliance
  • Says what it could not read, and why, instead of showing an empty layer as clean
  • Every client side by side on the portfolio view, colored by its worst layer
Visual view

See each layer as a picture.

Every layer has a Visual view: the same facts as the list, drawn so the pattern is visible at a glance. In the identity attack path, you can click through from a box to the records behind it.

  • Opens over the Overview, so you never lose your place
  • Reads the same facts as the list, so the picture and the numbers agree
Portfolio Insights

Read your whole book four ways.

Portfolio Insights draws each client from its latest saved assessment, and every dot, cell and row opens that client in the dashboard, on the finding, check or layer behind it.

  • Where the book sits: pick any two measures; the shaded box counts the clients on the wrong side of both
  • Controls across the book: one cell per client per control, the failing count first
  • What changed: Secure Score over 30 and 90 days, with the next step of each client’s recorded fix plan
  • Same gap, many clients: the clients failing one control, with the evidence the assessment recorded
Drawers and runbooks

Open any finding. Fix it with a runbook.

A finding, or the user, device or app behind it, opens in a drawer: what it means, the evidence, and the curated runbook that fixes it. A finding with no curated runbook yet says so.

  • Paste-ready PowerShell, filled in for that client
  • A check-only copy that changes nothing, separate from the apply copy, wherever the script has both
  • The permissions, steps and rollback, as the runbook records them
Findings

Search every finding for a client.

The Findings tab lists everything the assessment found for a client. Search by finding, object, layer or fix and open the one you need.

  • Each result opens in the same drawer as the Overview
Quarry agents

Agents prepare the fix. You approve it on the Review Desk.

The Quarry agents read each client’s findings and prepare one card per change that has a curated runbook: the case, the evidence, the runbook with its dry run and rollback. Every agent on the crew is held to the record: where an answer must be exact, it follows a fixed playbook; where AI writes, every claim is checked before you see it. Obsidian is the investigator: for each open card it decides whether an earlier fix (it held, it didn’t hold, it came back) or the client’s last 30 days of assessments bear on the case, and every statement it writes is checked against the records it cites. With too little evidence, it says so rather than guess. A technician approves or rejects each card, and your own tool runs the approved change: the Review Desk does not change the client’s tenant itself.

  • Prepared cards, ranked and routed to the right person
  • Approve, then hand off: the client is checked for drift first, and the change goes to your tool or ticket
  • Plumb reads the client again to verify the fix, and checks later that it held
  • Cards retire on their own when a newer assessment no longer finds the problem
Client week

The week’s plan for each client.

Client week ranks the fixes for one client, with each runbook’s time and the standards it helps, then shows what changed in the last 30 days and whether it keeps happening.

  • Every fix opens its card in the same drawer
Security brief

Show the client what you fixed and verified.

A security brief for each client: where it stands, what you fixed, its top risks, the decisions you need from it and what you fix next.

  • Executive view for the client’s leadership, Technical view with control ids and runbook links
  • Every figure comes from a recorded card or a saved assessment
  • Copy it as text or print it
Ask OutCrop

Ask about any client, in plain English.

Ask OutCrop answers from the same assessment the Overview shows, with citations to the records behind it.

  • When an answer is about a finding with a runbook, the runbook opens in the same drawer
  • Shows how many of the answer’s claims are cited
Also included

The rest of what ships today.

Optional add-ons

TrueRock Managed AI, for the clients who want it.

Not needed for anything above. Switched on per client. More about Managed AI →

A governed AI workspace

For clients who want one: their people ask questions of their own documents, every answer cited to the file, sensitive data redacted first. Switched on per client.

Connect the AI your clients already use

Coming: your clients connect the AI they already use, signed in with Microsoft or with access tokens you issue. Each client sees only its own data, under your policy, within the credits you allocate.

See it on your own tenants

See it on one of your clients.

A read-only first look at one tenant, under the access you grant — it names every surface it read and every surface it could not, with the reason.