What I work on
Most of my time goes on Microsoft 365 estates that have grown faster than anyone documented them: Intune device policy that drifted, Exchange Online mail flow rules nobody dares delete, and Copilot rollouts that surface a decade of sharing decisions in a single week. The writing follows the work, so if a post exists it is because the problem cost me a day.
On the development side I build in .NET, mostly services that have to talk to Microsoft Graph without becoming a liability. That is also the subject of the book I am writing with Apress on enterprise Copilot architecture.
How I test hardware and software
Hardware runs the same workload set in my rack for at least ninety days before it gets a score: three compute nodes, a sustained backup window, and one deliberately hostile firmware update. Power is measured at the wall. Software gets a real rollout in a tenant with real users, in rings, with a rollback plan.
Review units are bought or loaned, loaned hardware goes back within thirty days of publication and says so on the page, and nothing here is sponsored or carries a referral link.
What this site is for
It is a place to publish what I work out, so the next person searching the same error string finds a real answer instead of a three-year-old forum thread. There is no service pitch on this site and nothing is gated.