OpsPilot · Findings workspace
Every finding in one place, with a status you control
The findings workspace gathers findings from the reviews you ran in a session, lets you filter and search them, and lets you mark each as open, accepted or fixed. Marking a finding never touches your tenant.
In development
Built and tested with synthetic demo data. Statuses live in the page and are saved only as a small file you download; it has not been run against a real customer tenant.
Sample data
Findings (filter: open)
- HighAdministrator account without MFA
- MediumDisabled Conditional Access policy
- FixedLegacy sign-in blocked
What it does
- One list. All findings from the session's reviews, with severity, review and status filters and search.
- Fix guides. Each finding links to why it matters and the steps, in plain words, with the official Microsoft page.
- Status per finding. Open, accepted or fixed, held in page memory, with download and upload of a small JSON file so you can keep it.
- Trends beside it. A trends view shows grade, score and counts per review from the short history you may choose to save.
Where statuses are kept
Saved history stores grades, counts and titles only, so it cannot hold statuses. Statuses are not sent to a server. A server-side finding lifecycle with reasons and review dates is a Planned idea, not built.
What it reads
- Findings already produced by the reviews you ran in this session
- Grades, counts and titles from the optional saved history
What it never reads
- Anything new from your tenant: the workspace only reorganises results already on the page
- Passwords, keys and secret values
- The content of email, files or chats
Updated . Labels describe what is true now; see the roadmap for what is not built.