How to win a Microsoft Partner of the Year award in the AI era 

How to win a Microsoft Partner of the Year award in the AI era You’ve done the work. You’ve built and delivered solutions with Foundry, Copilot, and Data Fabric. And you’ve helped a customer transform something real – whether that was to cut costs, accelerate revenue, or modernize infrastructure that was holding them back.   Now […]

How to win a Microsoft Partner of the Year award in the AI era

You’ve done the work. You’ve built and delivered solutions with Foundry, Copilot, and Data Fabric. And you’ve helped a customer transform something real – whether that was to cut costs, accelerate revenue, or modernize infrastructure that was holding them back.  

Now you need a Microsoft Partner of the Year submission that reflects it. Judges are reading hundreds of entries that will all mention AI. The ones that standout and have better chances of winning will lead with business impact and measurable change.  

That’s what this guide is about. 

Business outcomes are the primary differentiator

Judges look for evidence of transformation. That evidence needs to be concrete. Revenue growth, cost reduction, risk mitigation, productivity gains, adoption rates, time to value, operational efficiency. Those are the signals that stand out. Vague claims about optimization or innovation are easy to skip. Specific numbers anchored to real business priorities aren’t. 

Your submission needs to quantify before and after states. Show what was happening before your engagement, what changed, and why that change mattered strategically. If your customer reduced processing time by 47 percent or increased forecast accuracy by 32 percent, say so. If your solution improved collaboration or unlocked insights without measurable proof, it’s going to be forgettable. 

AI is expected. Differentiation is not.

AI is embedded across Microsoft’s ecosystem. Saying your solution uses AI doesn’t differentiate you. What matters is how you applied it to solve a specific business constraint for a specific customer. 

Strong submissions will explain why Microsoft AI was the right call for that customer, at that moment. They describe the decision process, the constraint that required intelligence at scale, and the operational shift that followed. Your job is to make that argument clearly. 

Ultimately, AI should appear as an enabler within a broader transformation story.  

The customer story must carry the submission

The customer story is the central narrative of your submission. Judges want to understand your customer’s challenges, the stakes involved, and the measurable shift that occurred after your engagement. 

    • Build a clear transformation arc.  
    • Describe the business tension in practical terms.  
    • Show why existing approaches weren’t working.  
    • Then demonstrate how your work changed trajectory with numbers to back it up. 

To strengthen your submission, get the customer voice in. Direct quotes grounded in outcomes and operational change carry far more weight than generalized praise. A testimonial that describes a 25 percent reduction in downtime is stronger than one that calls you “trusted” or “innovative.”  

Alignment with Microsoft priorities must be explicit

Microsoft award categories evolve each year to reflect strategic focus areas. Security, AI integration, data modernization, and industry-specific innovation continue to receive attention. 

Make this alignment practical, not performative. Judges know Microsoft strategy. They’re looking for evidence you advanced it in a meaningful way. Showing co-sell motion, marketplace integration, or measurable Azure Consumed Revenue (ACR) is far stronger than simply claiming alignment. 

Clarity here strengthens credibility. 

Structure influences readability

Judges are reading a lot. Dense paragraphs packed with technical detail make their job harder. Clear organization makes your strengths easier to find. 

Guide the reader logically: problem, solution, impact. Cut unnecessary background. Prioritize measurable results and ecosystem relevance. When your submission is easy to follow, your strengths become easier to recognize. 

Preparation begins long before submission deadline

Every year, Microsoft award submission creation is a sprint. There’s typically about eight weeks between guideline release and the deadline. The best approach is to build a steady pipeline of documented customer outcomes throughout the year, so when the window opens, you’re not scrambling to recall what happened. You already have the metrics, the testimonials, and the story.  

When you start early, the quality shows. The writing gets sharper because the evidence is already in hand. The story gets stronger because it reflects sustained impact, not reconstructed memory. 

Choosing the right category matters as much as the story you tell

Microsoft adds, removes, and repositions award categories each year to reflect current strategic priorities. Before you start writing, spend time evaluating which category actually fits your work.  

Ask three questions.  

    1. Does the customer story you’re planning to use map naturally to this category’s evaluation criteria?  
    2. Is your Solutions Partner designation or specialization aligned with what the category rewards?  
    3. And how competitive is this space — are there categories where your work would stand out more clearly?  

A compelling story in the wrong category is still a disadvantage. The right category amplifies everything else you do well.  

It’s also worth knowing that category guidelines often specify what evidence types are weighted most heavily. Some categories prioritize customer impact above all else. Others weight partner ecosystem contribution, co-sell activity, or marketplace presence. Read those guidelines carefully before you commit to a direction. They tell you what the judges are looking for before you have to guess. 

You may find you have a strong story for one category. That one can be your focus. But that doesn’t stop you from revising your core submission for other categories you also fit. This is a common approach many partners take. 

Winning reflects strategic clarity

In 2026, AI capability is a baseline expectation. What judges are evaluating is clarity of business transformation, measurable results, and ecosystem impact. Your submission needs to demonstrate all three, clearly and precisely. 

The strongest submissions have clear outcomes, verified metrics, a coherent transformation arc, and explicit alignment with Microsoft priorities. 

When those components are present and tightly articulated, the submission earns attention for the right reasons. 

If your work deserves a win, let’s make sure your submission reflects it. Talk to us about your 2026 approach. Send us an email at awards@mercermackay.com or learn more at our Microsoft Awards page.