Microsoft has announced an important FY27 shift for Azure IP co-sell: the program is moving further away from broad partner-reported revenue motions and toward a Marketplace-first operating model. For software development companies that rely on Microsoft field alignment, seller engagement, and co-sell recognition, this is more than an administrative update. It changes where partners should focus their operational energy if they want co-sell activity to be visible, verifiable, and scalable during the July 1, 2026 through June 30, 2027 fiscal year.
The practical message is straightforward: if your Azure-based solution can transact through Microsoft Marketplace, treat Marketplace readiness as the default path for co-sell execution. If your current sales motion still depends on legacy partner-reported processes, now is the time to review gaps, clean up your Marketplace offer strategy, and align with your Microsoft contacts before pipeline momentum is affected.
What changed
Azure IP co-sell has historically helped qualified partner solutions connect with Microsoft sellers and customer opportunities. In many partner organizations, Partner Reported Azure Consumed Revenue, commonly known as PRACR, played a role in documenting partner-led Azure consumption impact. Microsoft is now signaling that this broad partner-reported approach is no longer the main co-sell mechanism for FY27.
Instead, Microsoft is making Marketplace the primary route for co-sell at scale. The reason is clear: Marketplace transactions provide a more standardized transaction record, better auditability, and cleaner alignment between the partner sale, customer purchase, and Microsoft seller engagement. Co-sell credit for Marketplace transactions continues to be recognized through Marketplace Billed Sales, or MBS.
This does not mean every customer scenario will instantly become simple. Enterprise procurement processes, private offers, channel involvement, custom contracting, and regional requirements can still introduce complexity. But Microsoft’s direction of travel is explicit: Marketplace is the expected foundation for scalable co-sell execution.
Why this matters for software partners
For software development companies, co-sell is not only a badge or program milestone. It can influence how Microsoft sellers understand your solution, how opportunities are prioritized, and how joint selling motions are measured. When the recognition model changes, sales operations, alliance teams, finance teams, and marketplace owners all need to adjust.
The biggest impact is that partners should no longer treat Marketplace as a side channel used only when convenient. In FY27, Marketplace readiness becomes a core go-to-market capability. If your offer is difficult to buy, priced inconsistently, missing private offer support, or disconnected from your sales process, those weaknesses can create friction in co-sell motions.
This also raises the importance of internal process discipline. A Marketplace-first model works best when sellers know when to route a deal through Marketplace, operations teams can support private offers quickly, and customer-facing teams can explain procurement benefits clearly. Partners that leave Marketplace execution to the end of a sales cycle may find themselves scrambling when a Microsoft-aligned opportunity needs a verifiable transaction path.
Default impact: less room for informal reporting, more value in verifiable transactions
The default behavior partners should expect is a stronger preference for transactions that can be validated through Microsoft Marketplace. Microsoft’s announcement emphasizes consistency, predictability, automation, and auditability. Those words matter. They indicate a reduced appetite for manual or broadly partner-reported methods as the central way to recognize Azure IP co-sell impact.
For partners that already transact through Marketplace, the immediate action is to scale and improve execution rather than reinvent the model. Review whether Marketplace is embedded in your standard sales playbooks, whether your field teams understand private offers, and whether your partner team can connect Marketplace activity to Microsoft co-sell motions.
For partners that are not yet Marketplace-ready, the update creates urgency. Gaps that once looked like back-office issues may now affect go-to-market performance. Common gaps include offers that are listed but not transactable, pricing that does not match enterprise buying patterns, insufficient documentation for customer procurement teams, unclear internal ownership, or a lack of repeatable process for custom deal terms.
Partner next steps
First, audit your current Marketplace posture. Confirm which offers are transactable, which are only listed, and which revenue scenarios still sit outside Marketplace. Pay special attention to the products or packages most often involved in Microsoft co-sell conversations.
Second, map your sales motion to Marketplace execution. For each typical opportunity type, identify when Marketplace should be introduced, who prepares the offer, who approves pricing and terms, and how the customer receives procurement guidance. The goal is to make Marketplace a normal part of selling, not a last-minute workaround.
Third, review private offer readiness. Many enterprise deals require negotiated pricing, custom terms, or customer-specific packaging. If private offers are slow or unfamiliar inside your organization, fix that now. Speed matters when Microsoft sellers and customer stakeholders are coordinating around a live opportunity.
Fourth, align with your Partner Development Manager or Microsoft contact team if you have scenarios that cannot currently transact through Marketplace. Microsoft’s guidance points partners with gaps toward their PDM for a path forward. Bring specific examples: customer type, offer structure, procurement blocker, geography, and the commercial reason Marketplace is difficult today.
Fifth, update reporting expectations internally. If leadership is used to PRACR-centered language, explain the FY27 shift and move dashboards toward Marketplace Billed Sales and Marketplace transaction health. This helps avoid confusion later when pipeline reviews, alliance scorecards, or Microsoft-facing discussions use different assumptions.
What partners should avoid
Avoid assuming that past co-sell recognition patterns will continue unchanged. FY27 is being framed as a transition to a more automated and Marketplace-first model, so old habits may create missed opportunities.
Avoid treating Marketplace as purely a procurement portal. It is increasingly part of Microsoft’s partner growth architecture: offer discovery, seller alignment, transaction validation, and incentive alignment all meet there.
Finally, avoid waiting until a deal is ready to close before testing Marketplace execution. The worst time to discover offer, pricing, tax, legal, or operational blockers is during final procurement.
Bottom line
Microsoft’s FY27 Azure IP co-sell update is a clear signal to software partners: Marketplace is now the primary path for scalable co-sell execution. Partners that already have mature Marketplace operations should focus on repeatability and seller enablement. Partners with gaps should treat Marketplace readiness as a near-term priority, not a future optimization project.
The winners in this model will be the partners that make Marketplace buying easy for customers, easy for their own sales teams, and easy for Microsoft sellers to understand and support.
Microsoft source: Azure IP co-sell updates