The 2026 Microsoft Marketplace Partner of the Year award opens nominations through July 7, spotlighting partners who have embedded Marketplace in their go‑to‑market engine. This article breaks down the award criteria, compares Microsoft Marketplace with AWS and Google Cloud marketplaces, and shows how the recognition can influence pricing, migration plans, and joint‑selling models for ISVs.
What changed
Microsoft announced that the nomination window for the 2026 Microsoft Marketplace Partner of the Year award is now open and will close on July 7, 2026. The program, which celebrates software vendors that have made the Marketplace a central pillar of their go‑to‑market (GTM) and co‑selling strategy, now places a stronger emphasis on measurable outcomes: customer acquisition, Marketplace billed sales (MBS), Azure consumption revenue (ACR), and usage of Microsoft 365 Copilot. In addition, judges will look for sophisticated use of Marketplace features such as private offers, multiparty private offers, and CSP private offers.

The updated guidelines also require a publicly transactable offer that is Azure IP co‑sell eligible, or a creative co‑sell scenario that blends Marketplace solutions with Microsoft 365 Copilot or other Microsoft SaaS services. This shift signals that Microsoft wants partners to demonstrate not just presence on the store, but real revenue impact and cross‑product integration.
Provider comparison – Marketplace vs. AWS vs. Google Cloud
| Feature | Microsoft Marketplace | AWS Marketplace | Google Cloud Marketplace |
|---|---|---|---|
| Co‑sell model | Integrated with Microsoft’s co‑sell program; partners can tap into Microsoft sales teams and the Azure Marketplace “Co‑sell” dashboard. | Co‑sell primarily through AWS Partner Network (APN) and the “AWS Marketplace Sellers” portal; less direct sales‑force involvement. | Co‑sell via Google Cloud Partner Advantage; limited to joint solution listings rather than a dedicated co‑sell engine. |
| Private offers | Supports private offers, multiparty private offers, and CSP private offers that can be targeted to specific Azure customers or CSPs. | Private offers exist but are limited to volume discounts; no multiparty flow. | |
| Pricing flexibility | Ability to publish consumption‑based, license‑based, and hybrid pricing models, plus usage‑based discounts tied to Azure consumption. | Mostly subscription or hourly rates; custom pricing requires separate contracts. | |
| Integration with AI services | Direct tie‑ins to Azure OpenAI, Microsoft 365 Copilot, and Azure AI Studio, allowing usage‑based billing tied to AI consumption. | AI services are available but not as tightly linked to Marketplace billing. | |
| Marketplace billed sales (MBS) reporting | Real‑time MBS dashboard with breakdown by offer type, region, and co‑sell partner. | Sales data available through AWS Marketplace Management Portal; less granular for co‑sell attribution. | |
| Developer experience | Offers a unified publishing API, automated CI/CD pipelines via Azure DevOps, and a Marketplace SDK for packaging. | Uses AWS Marketplace Catalog API; requires separate packaging steps for AMI, SaaS, or container offers. | |
| Channel reach | Supports digital direct, channel sales, and CSP co‑sell in a single listing. | Primarily digital direct; channel sales require separate partner programs. |
Strategic takeaways
- If your solution already runs on Azure, Microsoft Marketplace provides the most direct path to joint selling with Microsoft’s global sales force.
- For partners targeting a hybrid‑cloud customer base, the ability to publish private and multiparty offers gives Microsoft an edge over AWS and Google, especially when negotiating enterprise contracts.
- The new focus on Azure consumption revenue (ACR) means that solutions that can tie usage to Azure services (e.g., data pipelines, AI workloads) will score higher in the award evaluation.
Business impact and migration considerations
1. Pricing strategy alignment
The award criteria require quantifiable growth in MBS and ACR. ISVs should therefore revisit their pricing models to ensure that a significant portion of revenue is captured as Azure consumption. For example, a SaaS analytics platform can shift from a flat‑fee license to a usage‑based model that bills per GB of data processed on Azure Data Lake. This not only improves the ACR metric but also aligns with Microsoft’s consumption‑first pricing philosophy.
2. Leveraging private offers for enterprise wins
Private offers let you present a customized price or bundle to a specific Azure customer or CSP. When preparing a nomination, include case studies where a multiparty private offer closed a multi‑year contract that would have been impossible with a public price list. This demonstrates both technical capability (offer packaging, entitlement management) and commercial acumen.
3. Migration pathways for existing customers
If your solution is currently hosted on AWS or GCP, the award’s emphasis on Marketplace‑centric GTM can be a catalyst for a cloud‑to‑cloud migration. Use Azure Migrate or the Azure Marketplace SaaS onboarding toolkit to move workloads while preserving existing contracts. Highlight the migration in the nomination by reporting metrics such as:
- % of customers moved to Azure within 90 days
- Incremental Azure consumption generated post‑migration
- Cost savings realized through Azure Reserved Instances or Azure Hybrid Benefit
4. Multi‑channel go‑to‑market execution
A strong submission will show activity across digital direct, channel sales, and co‑sell. Build a reporting framework that tracks leads generated from each channel, then map those leads to closed‑won opportunities and associated Azure consumption. This data not only satisfies the award judges but also provides a repeatable playbook for future GTM planning.
5. Copilot integration as a differentiator
Microsoft 365 Copilot usage is now a measurable criterion. If your solution can augment Copilot—e.g., a knowledge‑base plugin that surfaces industry‑specific data—track Copilot API calls per user and tie those to subscription upgrades. Including these numbers in the nomination demonstrates that you are extending Microsoft’s AI stack, which is a high‑value signal for the judges.
How to position your nomination
- Executive summary – One paragraph that states the business problem you solved, the Marketplace‑centric approach, and the headline results (e.g., “Generated $4.2 M in Azure consumption revenue and added 1,200 new Azure customers in FY 2025”).
- Technical depth – Describe the Marketplace features you used (private offers, CSP private offers, co‑sell dashboards) and how they were implemented (API calls, entitlement models).
- Quantitative evidence – Provide tables or charts showing growth in MBS, ACR, and Copilot usage. Use percentages to highlight year‑over‑year improvement.
- Customer stories – Include at least two brief case studies that illustrate the value delivered and the role Marketplace played in the sales cycle.
- Future roadmap – Outline how you will expand Marketplace usage (e.g., new AI‑driven modules, additional private‑offer bundles) to sustain growth.
Call to action
Prepare your nomination now and submit it by July 7, 2026. Detailed guidelines are available at the official portal: Award Guidelines. For judge‑specific expectations, review the Judges Guidance and the FAQ. A well‑crafted submission not only puts your company in the running for the Microsoft Marketplace Partner of the Year award but also creates a reusable narrative for future GTM and co‑sell initiatives.

Comments
Please log in or register to join the discussion