Manage Azure Key Vaults
in seconds

I started my career as a developer… and honestly, I never felt like one of those “naturally gifted” engineers who just get everything instantly (impostor syndrome much?). I loved building things, but half the time I felt like I was guessing.

Then I moved countries, and everything flipped. The job I found wanted me to code in X++. And I thought: if I’m going to reinvent myself in a new country, it’s not going to be in X++. I didn’t have money to go back home, so I had to make this work. That’s how I fell into the cloud world.

I worked as an Azure admin and later as a cloud infrastructure engineer, and there I found something I actually enjoyed: solving problems quietly, without anyone breathing down my neck. But even there, one thing kept annoying me: Key Vaults. Searching for secrets, figuring out what was expiring, jumping between subscriptions, it was like playing hide and seek with my own infrastructure.

At one point I spent literal days building Power Automate flows just to get notifications for expiring app registration secrets. It worked… yay me. But also: why did something so basic require me to basically perform witchcraft? Maybe other people find it simple, but for me it felt absurd.

And there is another reason this project matters to me. I moved countries AGAIN, and I ended up spending a long period stuck in forced unemployment because of paperwork and residency bureaucracy. It is the kind of situation where your life feels paused and completely out of your control. Azure QuickOps became the thing that kept me learning, focused, and sane during all that uncertainty. It gave me something to build when everything else in my life was on hold.

So I built Azure QuickOps. Not because I'm trying to be the hero of the cloud world, but because I was tired of feeling like I needed a treasure map every time I wanted to find a secret.

If this helps someone else, amazing.