$ whoami
Hi, I’m Daniel Boring.
Cloud and infrastructure geek, home-lab tinkerer, and Chief Blogger at Virtually Boring. Based in Knoxville, Tennessee.

What I do
I’m an enterprise architect who enjoys making complex technology easier to understand, evaluate and put into practice. Over 20 years I’ve worked across infrastructure engineering, enterprise architecture and cloud delivery, in healthcare, banking, retail and federal government. Today I’m a Cloud Solution Architect at Microsoft, helping enterprise customers with Azure migration, landing zones, hybrid networking, virtual desktops and the infrastructure behind AI workloads.
My approach is simple: understand the business need, make the tradeoffs clear, and design something the people who run it can operate with confidence. Whether I’m leading an architecture review or chasing down a DNS problem, the goal is the same: leave people with a clearer picture and a useful next step.
Why this blog exists
Virtually Boring is my lab notebook. When I build something in my home lab, or solve a problem at work that’s worth sharing, I write down exactly what I did. That includes what broke and the fix that finally worked, so the next person doesn’t have to start from scratch. I started it in 2014 and I’m still at it.
Away from the keyboard
I’m a lifelong tinkerer. When I’m not working, you’ll find me in the home lab, at the 3D printer, or chasing whatever new technology caught my eye that week. Outside tech, I’m into Star Wars, Dungeons & Dragons, gaming, live music, theatre and museums. I’m a husband and a proud dad to an amazing daughter. Before she came along, my wife and I traveled as much as we could: Iceland, Ireland, Mexico, Canada and plenty of the US. The adventures look a little different now, but they’re no less fun.
Certifications
Microsoft







AWS

Expired

Expired



VMware






Other



The small print
Everything here is written by me, Daniel Boring. The views and opinions are my own and don’t reflect those of my employer. Test every procedure in a lab before you run it in production. Instructions and advice come without warranty or guarantees, just direction 🙂