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.
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
Publication
Find an answer
The command, the output, and what it proves, with the date it was last checked.
Open the Knowledge Base
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
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.
33 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 answers10 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 guide22 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
- 22
- Areas of Microsoft 365 begun
- 4
- Read from a real Microsoft 365 tenant
- 10
- Resting on Microsoft's own words
- 10
What is not established
- Every published question has a way to gather what it needs.
- 4 of the 13 areas have no established minimum permission: what they require has not been measured against a live directory. The other 9 were measured and need one permission each.
- 8 of the 12 Microsoft 365 areas this engine names have not started: no acquisition surface exists for them at all, and the catalogue says so rather than listing only what was built.
- 12 of the 22 questions rest on a convention rather than on something Microsoft wrote down. They are labelled as ours on every result, because a check that blurred its own authority would be worth less than the tools it argues with.
- A live read means the software read a real tenant. It does not mean a question was proved: one read saw everything it was pointed at and still produced no finding, because nothing in that tenant was in the state the question asks about. Reading it is established; answering it is not.
- A read is not the whole path. None of the 13 areas has yet been carried the whole way in one recorded run -- surface read, document produced, questions run on it, artefact built, and somebody independent opening that artefact. What was read is above; what has not been carried further is this.
- 2 areas have been reached and returned no positive read: a refusal, or a surface answered by something underneath rather than by the area itself. The refusal proves what happens when access is missing, and nothing about what is there.
- 1 area has never been run against a real tenant at all, and still publishes questions. It behaves as somebody believed the interface behaves, which is the gap this list exists to name.
- 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.0b8@2d4f5db76f21
Analysis
What the work turned up
Longer pieces from real engagements: what we measured, what surprised us, and what we would do differently. 24 published.
What we publish
Everything public, and who owns it.
Product
Publications
Tools
Service
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.
Where the work was done. Engagements delivered by João Tito Lívio, Microsoft MVP, over thirty years in the Microsoft stack. These are not installations of this product.
- 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
Stay current