The Microsoft MVP Award explained: contributions, nominations and keeping your record

Ask five people how someone becomes a Microsoft Most Valuable Professional and you'll get five answers, most of them folklore. I'm not an MVP; I'm writing this as someone working towards it who went back to the official program pages to separate the rules from the rumours. Here is what the award recognises, how a nomination becomes a decision, which contributions count, and the log I think every active community contributor should keep.

How it works: what the award is (and isn't)#

Microsoft describes the MVP Award as its way of thanking exceptional community leaders: people with deep knowledge of Microsoft products who share it in public and help others. Three things follow from that framing:

• It's an award, not a certification. There's no exam; a certification proves what you know to an examiner, while the award recognises what you did for other people, visibly.
• It's judged on the trailing twelve months. The official FAQ says only contributions from the past 12 months are considered, and it refers to "non-renewal" decisions, so the award is a yearly cycle rather than a one-time badge.
• Impact is the currency. Reviewers assess technical expertise, community leadership and influence, product feedback and community health, including the code of conduct.

Eligibility, per the FAQ and the MVP Program Agreement: at least 18, an individual rather than a company, not a Microsoft employee, and not a contractor currently working for Microsoft unless the Active Vendor Policy applies. If you work for or alongside Microsoft, read that wording first.

Award categories for Microsoft 365 and security people#

The program groups technology areas into award categories; you can apply for up to two areas, each mapping to one category. The FAQ points to the current "MVP Program Technology Structure" for the definitive list, so treat this as a snapshot from public MVP profiles:

• Intune-focused MVPs appear under the Security award category with Microsoft Intune as the technology area; Windows and Windows 365 sit under Windows and Devices.
• Microsoft Entra work shows as Identity & Access, and Microsoft Defender XDR and Microsoft Sentinel as SIEM & XDR, both under Security.
• Exchange, Outlook, SharePoint and Microsoft 365 Copilot sit under M365; Azure operations under Microsoft Azure.

Pick the area your content genuinely covers; every contribution in the application is aligned to a technology area.

What counts as a contribution, and what doesn't#

The official pages give plenty of examples: speaking at conferences and user groups, organising technical events, blog posts, articles and books, forum answers, social media posts, open-source contributions, live coding, podcasts, workshops, mentoring, and product feedback to engineering teams. The format matters less than being public and useful.

For each contribution the application asks for the technology area, the date or date range, the type, a verifiable working URL, and measures of community impact such as attendees, views, subscribers or engagements. That last item is why reach matters more than volume.

The FAQ is equally clear about limits:

• Paid work for your employer or your own business doesn't count.
• Contributions should be free to the public (no paywall or paid subscription); the stated exception is in-person events charging an entry fee for venue and logistics.
• You may not be paid for a contribution you list, such as a speaker's fee or payment for an article.
• Every contribution needs a verifiable link.

In practice: the tickets I resolve at work are my job, while a public post explaining the same fix is a contribution; a paid course I deliver as a Microsoft Certified Trainer is work, while a free community session on the same topic counts.

Step by step: from nomination to decision#

1. Someone nominates you. A referral must be submitted on your behalf by a Microsoft full-time employee or a current MVP. There is no self-nomination form.
2. You complete the MVP Application within 45 days. The invitation comes from an @microsoft.com address, tied to the email the nominator used. Choose up to two technology areas, enter each contribution with dates, type, URL and impact metrics, acknowledge the MVP Program Agreement, and submit; a saved application isn't reviewed.
3. Microsoft reviews it. Product leaders and MVP Program leaders assess the application. Reviews happen monthly, and the FAQ says a decision can typically take up to 90 days after submission.
4. Outcome and re-nomination. A nomination doesn't guarantee an award. After a decline or non-renewal, a new nomination is possible after a 45-day waiting period; if you didn't complete the form in time, after six months.

Keep your record: a contribution log you can copy#

Many long-standing MVPs recommend keeping a running record rather than reconstructing a year from memory. The application wants dates, links and numbers for every item; links rot, event pages disappear and view counts only mean something if captured consistently. This minimal log maps onto the form:

Or as a CSV header (add a technology-area column later):

Date,Type,Title,Audience/reach,Link

Then apply a few rules:

• Log it the week it happens. It takes a minute now and an afternoon of digging a year later.
• Make it public and measurable. Ask organisers for attendee numbers, publish recordings and slides, prefer Q&A platforms where an accepted answer is visible, and invite corrections in public.
• Verify quarterly. Open every link, confirm it's still public and free, and update the reach column. Every row should have a live URL and a number.
• Focus, then diversify. Stay in one product area for a full year, but mix formats within it: writing, speaking, answering questions and filing feedback.
• Be consistent for twelve months. A steady monthly rhythm counts for more than a burst around conference season.

A personal blog like this one is the easiest anchor for all of that: every post is dated, public, free and has its own URL and analytics, and talks, forum answers and feedback items can point back to it. It also forces you to explain things in your own words, which is where expertise shows.

Common misconceptions#

• "Certifications earn it." They don't appear in the published criteria; the award is about public contribution.
• "I can nominate myself." No; the referral must come from a Microsoft full-time employee or a current MVP.
• "Microsoft staff can be MVPs." Employees are excluded, as are contractors working for Microsoft unless the Active Vendor Policy applies.
• "My paid work counts." It's excluded, and you can't be paid for a contribution you list.
• "A nomination means I'm in." It means you're invited to apply; the review decides.

References#

• Microsoft MVP Program overview
• Microsoft MVP Program FAQ: eligibility, nominations, application and contributions
• MVP Communities: Become a Microsoft MVP