Let’s get this out of the way: AWS is like that one overachieving kid in class who has 900 extracurriculars, speaks six languages, and somehow still gets perfect attendance. Impressive? Yes. Overkill for most of us? Absolutely.
So when it came time for me, a solo IT administrator, to pick a cloud platform for our small but mighty public utility, I asked myself a very important question:
“Do I want to spend my weekends figuring out AWS billing just to run one virtual machine and a SQL database?”
No. No, I do not.
Reason 1: Azure Is Just… Easier for Windows Nerds Like Me
I work in a Windows-heavy environment. Our servers run Windows Server. Our endpoints? Windows. Our users? Still trying to Ctrl+Alt+Delete their way into Teams.
Azure just fits. It speaks fluent Active Directory, Group Policy, and PowerShell. Setting up hybrid identity with Azure AD Connect took less time than figuring out AWS’s IAM policies, which felt like solving a Rubik’s Cube blindfolded, underwater, in Klingon.
Need a VM? Azure says, “Windows Server 2022 with preconfigured networking and auto-patching?” and I say, “Yes, thank you.” AWS says, “Here’s a t3.nano instance with a YAML cloud-init script and 17 tabs to configure.” I don’t have time for a part-time DevOps internship.
Reason 2: Azure Works With What We Already Have
We already use:
- Microsoft 365 for email and collaboration
- Windows Defender for Endpoint
- Azure AD for SSO
- Group Policy for user control (because, no, Sharon, you still can’t install Chrome extensions)
So Azure? It’s just the next logical step. Integration is smooth. No duct tape required.
Reason 3: Billing Doesn’t Induce Existential Crises
Azure’s pricing may not be cheap, but it’s understandable. AWS makes you feel like you’re buying airline tickets—there’s always a mystery fee, and you need a calculator, a translator, and a hug.
Azure even gives you cost alerts and budgeting tools that don’t feel like they were bolted on by interns. I get one consolidated invoice, not 14 line items explaining how I was charged $7.23 for “Elastic IP Attachment Sprawl.”
Reason 4: I Don’t Need 800 Services—I Need 8 That Work
I don’t need:
- AWS RoboMaker
- AWS Ground Station (why yes, let me spin up a satellite)
- AWS Snowball (no, I’m not shipping servers on ice)
I need:
- VMs
- Storage
- SQL
- Azure AD
- Security Center
- Defender
- Backup
- VPN
Azure does all that—and does it in a way that doesn’t make me feel like I need a certification just to turn it on.
Reason 5: One Throat to Choke (Thanks, Microsoft)
If something breaks, I call one vendor. I don’t have to navigate a jungle of “contact your support plan partner” or “refer to the community forums.”
Microsoft already controls half my IT stack anyway. If it’s all in one ecosystem, at least I can hold one support team accountable when something goes sideways.
Final Thought
AWS is great if you’re running a startup, a Fortune 500 company, or a secret AI lab inside a volcano. But I’m running a utility district, managing everything from the firewall to the fiber, and I have enough on my plate.
Azure gives me what I need, works with what I have, and doesn’t make me hate life every time I log into the dashboard. That’s a win in my book.