What we build
PilotSuite is our product family for Microsoft endpoint operations. GraphPilot is the first available product. It helps technicians and administrators collect Windows Autopilot hardware hashes, merge and normalize CSV data, review records, and prepare a clean handoff for Microsoft Graph or Intune. HashPilot and MergePilot describe the collection and merge workflows inside that larger product.
EnterprisePilot is a separate product in development. Its direction is endpoint diagnostics, identity posture, remediation context, and concise operator summaries. We describe work in development as such; we do not present roadmap items as available features.
The IT Admin Utility Hub is a free companion publication. Its lookup tools turn common Microsoft identifiers—permissions, roles, error codes, policy paths, lifecycle dates, capabilities, and licensing concepts—into a useful first answer. The utilities do not replace the target tenant, event log, current licensing terms, or Microsoft documentation. They are designed to help an administrator reach those sources with a better question.
Why the technical resources exist
Microsoft administration problems rarely fail at the obvious step. A CSV may have the right columns but a damaged hash. A device may look duplicated because two administrative systems represent different objects. A Graph request may have a valid token but the wrong resource permission. A Windows enrollment failure may begin with scope or identity before the enrollment client writes a useful error.
Our technical resources focus on those handoffs. Each guide tries to answer four operational questions: what does the evidence establish, what does it not establish, what should be checked next, and which authoritative source should be used to confirm the current behavior?
How we write and review
Guides are independently written by X EQUALS MASS SQUARED LLC. We begin with a task or failure state, not a search keyword. We reproduce the workflow in a safe test context when practical, separate direct observations from interpretation, and link to the relevant Microsoft Learn or product documentation. We summarize those sources in our own words and add the ordering, cautions, and decision points that make the material useful in the field.
- Primary sources first. Microsoft Learn, product references, service documentation, and official lifecycle information are preferred over third-party summaries.
- Scoped claims. We distinguish a file-format rule from a tenant setting, and a permission definition from what a particular application should receive.
- Operational caveats. Destructive cleanup, tenant ownership, privileged consent, licensing, and security boundaries receive explicit warnings.
- Review dates. Resource pages show when they were published or last reviewed. Because cloud behavior changes, readers should confirm time-sensitive details through the linked source.
- No paid placement inside conclusions. Product links are identified as related software, while technical conclusions are based on the evidence and cited documentation.
What our guidance cannot know
A public article cannot inspect your tenant configuration, licensing agreement, device ownership, conditional access policy, Graph application registration, or local logs. Examples use generic names and are not instructions to delete production objects or grant broad permissions. Verify the target tenant, preserve identifiers and logs, use a change process, and test with a limited scope before making a production change.
Microsoft product names and trademarks belong to Microsoft. x=mas2 is an independent company and is not Microsoft. Links to Microsoft documentation are provided as authoritative context, not as an assertion of partnership or endorsement.
Contact and corrections
If a guide no longer matches current Microsoft behavior, or a utility returns an ambiguous result, send the exact page, input, observed output, and the relevant Microsoft documentation through our support page. Specific evidence lets us correct the record without guessing.