One Month Later

It’s been a month since that email landed — the one that made every late night, every draft blog, and every community chat feel worthwhile. I’d officially joined the ranks of the Microsoft MVPs.

For nearly two years, that goal hovered quietly in the background. Not as a badge of validation, but as a symbol of growth, proof that passion and persistence in the community could translate into meaningful impact.

Inspiration Close to Home

My motivation came from seeing others do what I aspired to do. Working alongside Australian MVPs and local content creators showed me what genuine community engagement looked like it’s collaboration over competition, learning over ego.

They weren’t chasing recognition; they were sharing because they loved what they did. That energy was contagious, and it helped me find my own rhythm.

A Look at the Numbers

The Microsoft MVP community might seem global and vast with around 3900 members around the world, but drill down to Australia where is only 122 (thats ~3.12%) current MVP’s whilst unsurprising for sum what it does suggest that a tight-knit group or people are making a significant local impact.

MVPs in Australia by Category

You can easily see where Australia’s MVP strength lies — M365 and Azure lead the way, reflecting how deeply those platforms run across local enterprises.

MVPs in Australia by State/Territory

I call NSW home and with around 8 Azure MVPs in the state

Writing with Purpose

For me, it all started with writing. Sharing what I learnt about Azure networking, infrastructure, and security wasn’t just about documenting my work it has become how I learned best.

Consistency was the real differentiator. I didn’t write because I had free time; I made time because I wanted to contribute. Even when writer’s block kicked in, even when posts didn’t land perfectly I showed up again the next week.

That’s what slowly turned effort into opportunity.

Burnout, Block, and Brewing Through It

There were definitely low points. Burnout crept in. Writer’s block hit hard. Some weeks I’d question whether the effort even mattered.

If you’re creating content or contributing to the community, a few lessons I learnt the hard way:

• Consistency ≠ relentlessness. You can take breaks. Sustainability beats speed.
• Batch your creativity. When you’re in the zone, create more than you need.
• Connect with others. Community thrives on collaboration, not just contributions.

Some of my best ideas came after a pause, not during the grind. Much like coffee — sometimes you need to let it brew.

Supported by Community

I owe so much to the people who encouraged me when they didn’t have to those who read early drafts, shared posts, invited me to speak, or simply said, “keep going”.

Behind every MVP announcement is an invisible network of encouragers and motivators. My success is as much theirs as it is mine.

Understanding the MVP Application Process

Since going through this process myself I have had others ask around how someone becomes an MVP, so let’s break it down.

To be considered for the Microsoft MVP program:

• You must be nominated — either by a current MVP or a Microsoft Full-Time Employee (FTE).
• You need to provide evidence of your community reach: blogging, public speaking, mentoring, open-source contributions, or any content that helps others.
• Your community work must be independent of your paid employment. For example, I regularly speak at webinars hosted by cubesys, but those can’t count toward my community metrics.
• Consistency matters. Doing one talk or a couple of posts a year won’t cut it. You need to show sustained engagement.
• Stay in your lane. Pick the category you genuinely live and breathe. I focused on Azure, it wouldn’t make sense for me to apply under “Software Development” when that’s not my craft.
• Find a mentor. Someone already in the program can be invaluable. They’ll have tips, advice, and nuances you won’t find written anywhere.

The process isn’t designed to gatekeep, it’s designed to recognise authenticity. Microsoft wants people who build community impact, not just technical trivia.

Encouraging Others to Chase Their Goals

If the MVP journey isn’t your thing, that’s okay. The real message here is to pursue what excites you.
Maybe that’s an AWS Hero, a Google Cloud Champion Innovator, or a VMware vExpert. Each has its own flavour, but they all celebrate the same principle: sharing knowledge and growing your community.

If you’re passionate about cloud, security, AI, or open source — start creating, start engaging, start small. You don’t need permission to make an impact.

As I learnt, the most meaningful journeys don’t start with “how do I get recognised?” — they start with “what can I share today that might help someone else?”

The Journey Doesn’t End Here

Becoming an MVP isn’t where it ends, it’s just a checkpoint.
There’s more to learn, more to build, and more to give back.

Now that I’ve earned the badge, the goal has shifted to helping others earn theirs, mentoring new contributors, and keeping that same curiosity that started all this in the first place.

Learn More

• Microsoft MVP Global Directory
• Become a Microsoft MVP
• AWS Heroes Program
• Google Cloud Champions Innovators
• VMware vExpert Program