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.
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.
Users, admins and Conditional Access coverage: who can sign in, how, and which users a policy misses.
Managed devices against compliance, encryption and antivirus health, read from Intune and Defender.
The CVEs that match this client’s products, known-exploited ones called out, and the Defender alerts the tenant records.
Sensitive data, external sharing and who can reach it, across SharePoint and OneDrive.
Email authentication for each custom domain: SPF, DKIM and DMARC.
The apps and agents connected to the tenant, their permissions, owners and credentials.
Seats bought against seats used, and the license changes that close a security gap or reclaim waste.
The client against your security baseline: a CIS Level 1 starter you can edit, with per-client exemptions that record their reason.
Framework controls mapped to the tenant’s real configuration, each traced to the evidence behind it.
Each client tenant opens on one Overview: a tile per layer, worst first, each opening on the findings behind it.
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.
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.
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.
The Findings tab lists everything the assessment found for a client. Search by finding, object, layer or fix and open the one you need.
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.
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.
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.
Ask OutCrop answers from the same assessment the Overview shows, with citations to the records behind it.
Not needed for anything above. Switched on per client. More about Managed AI →
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.
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.
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.