Practical writing on cloud architecture, Microsoft 365, IT leadership, and the operational discipline it takes to run compliant, cost-efficient technology at scale — from someone doing the work.
Honest writing on cloud architecture, IT leadership, and keeping complex systems running.
Everyone thinks their Microsoft 365 environment is locked down enough to deploy AI tools. MFA is on. Permissions are set. What they haven't looked at is the sharing sprawl underneath — the Anyone links that never expired, the contractor guest...
Cloud architecture in healthcare isn't just about what works technically — it's about what holds up under a compliance audit, what your BAAs actually cover, and what you can defend to clinical leadership. Here's the framework I use.
Technical expertise gets you into IT leadership. The ability to think about business outcomes, own operational risk, and develop other people is what determines whether you succeed once you're there.
Most cloud cost problems don't start with architecture. They start with ownership. Here's the four-phase operational framework that actually delivers lasting results.
Organizations that need to collaborate closely across Microsoft 365 tenants have historically faced a frustrating choice: clunky guest access or full tenant consolidation. Cross-tenant synchronization and MFA trust policies offer a third path.
Every organization knows file servers are a problem. Most treat it as a storage or technology decision. The ones that successfully migrate to SharePoint treat it as a leadership and organizational design decision first.
The areas I actually work in.
