pH7x Systems · engineering on Microsoft 365

Microsoft 365 decisions
you can defend.

We work out how Microsoft 365 actually behaves, prove it against real tenants, and publish the working. What can be established is written down; what cannot is written down as well.

  1. Product

    Govern a tenant

    Read a tenant with an open-source engine and ship an Assessment somebody else can re-check.

    See what the Engine publishes
  2. Publication

    Find an answer

    The command, the output, and what it proves, with the date it was last checked.

    Open the Knowledge Base
  3. Guide and tool

    Plan a migration

    A method that goes in order, and a two-minute read on where your estate stands.

    Read the Field Guide
  4. Service

    Work with pH7x Systems

    A readiness review that ends with a destination you can defend, and what will stop you.

    See what a review includes

Useful now

Published work you can take and leave

None of this asks for anything first. It exists because we needed it ourselves, and publishing it is how the reasoning gets checked.

  • 28 answers

    Knowledge

    Verified answers to Microsoft 365 questions

    Each one says how it was established, against which version, and on what date. Where something could not be established, it says that instead of filling the gap.

    Read the answers
  • 10 chapters

    Field Guide

    A SharePoint migration method, in order

    Written for the person who has to recommend a destination and defend it: what to gather, what decides, and what does not cross as it is. Free, in English, version 0.2.0. No email required.

    Open the guide
  • 20 published rules

    Tools

    Things that answer a question today

    The SharePoint Compass turns a decision into a defensible recommendation, and the governance engine is open source: the rules are files you can read, argue with and change.

    See the tools

What we build

Microsoft 365 Governance as Code

An open source engine that declares what kind of claim each check is making, shows the evidence behind every result, and says plainly when it could not reach an answer. It is in active development, and the numbers below are read from the contract it publishes rather than written here.

Questions it answers
20
With evidence it can gather
20
Proved against a real tenant
20
Areas of Microsoft 365
11

What is not established

  • Every published question has a way to gather what it needs.
  • 4 areas have no established minimum permission. Nine of the eleven reads were measured against a live directory and need one permission; two were refused, and what they require is not yet known.
  • No percentage appears anywhere, deliberately. A single number gets read instead of the detail, and the detail is what answers the question.

Read from capability-manifest/1.0.0 at 1.0.0b6@ea616d0b87f6

Analysis

What the work turned up

Longer pieces from real engagements: what we measured, what surprised us, and what we would do differently. 23 published.

  • 2026-08-11

    The confident wrong answer is worse than missing evidence

    Read it
  • 2026-08-11

    The green test that measured nothing

    Read it
  • 2026-08-05

    Why SharePoint Framework still runs on React 17

    Read it

Every piece of analysis

What we publish

Everything public, and who owns it.

All free tools

01 · Who we are

We publish what we had to work out

pH7x Systems builds software and publishes the engineering knowledge that came out of solving hard problems in real tenants. The answers here are the ones we needed ourselves: each says how it was verified, when, and what it does not cover.

Everything published as a capability is derived from a proven run, never from what the code could in principle do. Where we cannot establish something, the page says so instead of filling the gap.

European Commission
Global SharePoint farm · DG Trade
Irish Government
Publishing intranet · DECLG
Banking
Tenant security, governance, migrations
Fortune 500
On-premises to SharePoint Online, rebuilt in SPFx

06 · Stay current