Most partners treat Microsoft's incentive money like the weather. It turns up, or it doesn't, and finance keeps half an eye on it. That's the mistake.
A big chunk of the money sitting inside these programmes only unlocks when marketing produces the right activity - and the right paper trail to back it up. No activity, no evidence, no claim. It really is that blunt.
And for FY27, the stakes just went up. Microsoft has reshaped the whole incentive model this year - fewer generic earning opportunities, a harder focus on AI and growth, and a stricter bar on proving what you delivered. So if you run marketing for a Microsoft partner, or you're the alliance lead trying to squeeze more out of the relationship, this one's for you. Not another list of programmes - Microsoft already documents those better than anyone. This is the bit nobody writes down: what your marketing has to actually look like to claim what's on the table.
Why partner incentives are a marketing problem, not just a finance one
Here's the bit that gets missed. The fund gets earned or allocated on paper, but you only convert it by doing marketing and proving you did it.
Take the two big marketing-linked pots. Co-op is money you've earned - a share of your Microsoft incentive earnings accrues into a fund that has to be spent on qualifying marketing in a set window, or you forfeit it. MDF is different: it's allocated ahead of revenue, usually on a cost-share, for campaigns Microsoft agrees to back up front.
Different mechanics, same trigger. Marketing activity, plus evidence, submitted before a deadline. That's not a finance task - finance can't screenshot a landing page or pull an attendee list.
And these funds don't roll over out of kindness. Co-op earned in one half of the year becomes available to spend in the next, and then it expires. So picture the all-too-common version: it's February, someone finally checks Partner Center, and there's a meaningful co-op balance sitting there with a few weeks left on the clock and no campaign planned against it. That money doesn't get a stay of execution. It just disappears.
The cost of getting this wrong is real, and it's widespread. Industry estimates suggest a large share of MDF - by some counts more than half - goes unclaimed every quarter across the channel. That's not a budgeting problem. It's a marketing planning gap, sitting there in plain sight, quarter after quarter.
Reframe it and the whole thing gets simpler. These channel incentives aren't a rebate that lands in an account. They're a marketing budget you've already earned, with strings attached. The strings are the marketing.
The FY27 programmes marketing actually touches
There are four worth knowing, and marketing has a hand in every one.
Co-op
The classic channel incentive. You earn it as a percentage of your incentive earnings - for CSP distributors, for example, the calculation runs on a rebate-plus-co-op split - and the co-op portion has to be spent on qualifying marketing and enablement in the following usage period. Microsoft has published a fresh FY27 Co-op Policy Guide, so check it before you plan, but the shape is unchanged: it's money you've already generated, yours to deploy on demand-gen, events, content and skilling, as long as you use it in time and prove it.
MDF (Market Development Funds)
Discretionary, forward-looking money for strategic campaigns Microsoft wants to see run. Typically a cost-share, though managed partners can qualify for more. The catch that trips marketers up: MDF usually needs a plan signed off before you spend, not after. So this one rewards teams who plan a quarter ahead, and quietly punishes the ones who improvise.
MCI and the FY27 investment programmes
This is where FY27 has changed most. The old single Microsoft Commerce Incentives guide has been split into separate, scenario-based investment programmes - AI Business Solutions, Cloud & AI Platforms (Azure), and Security - under Microsoft's "Frontier" banner. The engagements are fewer and broader, and the money is tilting hard toward growth, premium products and AI, and away from flat run-rate rebates. For marketing, that's a real shift. Generic "we support Microsoft" activity earns less and less. Your campaigns now have to map to a specific play - an AI or Copilot motion, a security posture story, an Azure growth push - to line up with where the funding actually sits.
ISV Success and Marketplace Rewards
If you're a software company, Marketplace Rewards comes bundled into ISV Success at no cost - listing optimisation from professional marketers, featured placement on AppSource and Azure Marketplace, co-branded campaign assets, social promotion through Microsoft's own channels. There's even a small piece of admin that's pure marketing: you have to assign a company marketing contact in Partner Center to switch the benefits on. Leave that blank and the perks just sit there unused. Worth switching on, mind - Microsoft's own figures put partners who use Marketplace Rewards at five times the billed sales of those who don't.
One timing note. FY27 went live on 1 July 2026, but Microsoft is still rolling the full detail out through its July partner kickoffs, so treat any specific rates you see floating about as provisional until the guides settle. And don't forget the tail: FY26 claim windows are still open well into 2027, so there's live money to close out even as you plan the new year.
Comparison: eligibility, what marketing produces, evidence needed
Here's the whole thing on one page. Notice the last column - it's the same story in four different costumes.
| Programme | Who it's for | What marketing has to deliver | Evidence needed to claim |
|---|---|---|---|
| Co-op | Partners who've earned incentives; co-op accrues automatically and expires if unspent | Demand-gen and awareness activity promoting Microsoft products - campaigns, events, content, skilling | Proof of execution: dated proof it ran, clear Microsoft attribution, invoices, results. Submitted in Partner Center |
| MDF | Managed or invited partners; funds allocated ahead of revenue, usually cost-shared | An upfront activity plan Microsoft signs off, then the campaign itself | Approved plan first, then proof of execution and reporting reconciled against that plan |
| MCI / FY27 investment programmes | Partners delivering qualifying engagements in AI Business Solutions, Cloud & AI Platforms, or Security | Marketing that generates and nurtures the pipeline for a specific solution play, not generic activity | Engagement-specific POE, increasingly weighted toward outcomes and adoption, not just the transaction |
| ISV Success / Marketplace Rewards | ISVs with an offer on Microsoft Marketplace, in the AI Cloud Partner Program | Listing content, co-branded assets, launch and demand-gen campaigns | A live, optimised Marketplace listing, an assigned marketing contact, and billed-sales performance to unlock higher tiers |
The evidence trail: what a claim-ready campaign looks like
This is where the value is won or lost, so slow down here - and in FY27 it matters more than ever, because the early reads of the new guide all point the same way: stricter proof, more focus on outcomes, tougher audits. The bar for "we did the thing" has gone up.
Proof of execution (POE) is what Microsoft actually checks before it pays. And the single biggest reason claims fall over isn't that the activity was bad - it's that nobody captured the evidence while it was happening. You cannot reconstruct a claim-ready trail six months later from memory and a vague feeling that "we did a webinar in March".
A claim-ready campaign keeps, as it goes:
- The plan - what you're running, against which product, mapped to a qualifying solution play.
- Dated proof it ran - screenshots, live URLs, email sends, registration and attendee lists.
- Clear Microsoft attribution - the right branding and product references, done to Microsoft's rules, not just a logo dropped in a corner.
- The money - invoices and spend, so the cost-share adds up.
- The results - leads, registrations, pipeline, and increasingly the adoption or outcome that followed. The so-what.
Let me make that concrete, because it's the difference between paid and rejected.
The version that fails: a partner runs a solid Copilot webinar, gets 90 registrations, and it goes well. Three months on, the claim gets built. The landing page has been taken down, so there's no live proof it ran. The registration export lives in someone's inbox who's since left. The invoice from the events agency is there, but nothing ties it clearly to a qualifying Microsoft motion. Good campaign. Dead claim.
The version that pays: same webinar, but the moment it's built, someone drops the plan, a screenshot of the live registration page, the dated email invite, the agency invoice and the final attendee-and-leads report into one shared folder, named for the campaign. When the claim window opens, packaging it takes twenty minutes, not a fortnight of archaeology.
So here's the test I'd apply to any activity before you run it. Could you prove, half a year from now, that this ran, that it promoted the right Microsoft product, and what it delivered? If the answer's no, it isn't claim-ready yet. Sort that before you spend a penny.
Where marketing teams get it wrong (three common failures)
One: finding out too late
Marketing hears about the fund when the window's already half gone. There's no activity planned against it, so it either gets rushed into a low-quality campaign or written off entirely. The fix is unglamorous - marketing and alliances need the fund position at the start of the quarter, not scrabbling for it at the end.
Two: running the activity, not capturing the evidence
The campaign goes out, performs fine, and then the claim quietly dies because nobody kept the proof. Great marketing, no payout - which is arguably worse than not running it, because you've spent the effort and the cost-share and got nothing back. Capture as you go, or don't bother claiming.
Three: generic, Microsoft-washed campaigns
Activity that name-checks Microsoft but doesn't meet the rules - wrong product, weak branding, or a motion that maps to no qualifying play. This one bites harder in FY27, now the money's organised around specific AI, Security and Azure-growth scenarios. "We mentioned Copilot once" won't cut it. The activity has to sit squarely inside a funded play.
Three different failures, one root cause: marketing and the incentive treated as separate projects that happen to overlap. Join them up and all three go away.
A quarterly rhythm for marketing plus alliances
You fix the lot with a simple cadence. Nothing fancy - just joined-up, and owned by named people.
- 1
Start of quarter
Alliances shares the fund position - what's accrued, what's allocated, which windows close when. Marketing maps planned activity straight onto it, and onto the right FY27 solution play. This is one short meeting, not a project.
- 2
Before you build
Scope each campaign to be claim-eligible first. Lock the product, the qualifying play, the Microsoft attribution and the POE checklist before anyone opens a design file. Get eligibility wrong here and no amount of good creative saves it later.
- 3
In flight
Capture evidence live. Screenshots, lists, spend, results - all filed into one named folder as it happens, not chased down afterwards.
- 4
End of quarter
Package the proof, submit through Partner Center, report the results back to alliances, and feed what you learned into next quarter's plan.
The ownership matters as much as the steps. Alliances owns the fund position and the submission. Marketing owns the activity and the evidence. A shared tracker - even a simple one - keeps both sides honest about what's been spent, what's been claimed, and what's about to expire.
Do that four times a year and you stop leaving money on the table. Simple as that.
FAQ
What are Microsoft Partner incentive programmes?
They're the funds and benefits Microsoft gives partners to grow the business - rebates, Co-op and MDF marketing money, activity-based investments under Microsoft Commerce Incentives, and ISV Success benefits. Most reward specific behaviour, and the marketing-linked ones only pay out once you've run qualifying activity and proved it.
What is the difference between Co-op and MDF?
Co-op is earned - a share of the incentives you've already generated accrues into a marketing fund you claim back by running qualifying activity. MDF is allocated ahead of revenue, usually on a cost-share, for campaigns Microsoft agrees to back up front. Co-op looks backwards; MDF looks forwards.
Who submits the claim, marketing or the partner alliance lead?
The partner submits it, through Partner Center, using someone with the Incentives admin or user role - usually the alliance or operations lead, not marketing. Marketing's job is to run the eligible activity and hand over clean proof of execution, so whoever submits has everything they need.
What counts as proof of execution for a Microsoft-funded campaign?
Dated evidence the activity actually ran and promoted the right Microsoft product: screenshots or live URLs, event and registration lists, the campaign assets, invoices for spend, and results. FY27 leans harder on outcomes and adoption, not just the transaction, so capture the impact too - and capture it as you go.
Can a marketing agency submit claims on our behalf?
No. The partner submits the claim in Partner Center - an agency can't do it for you. What a good agency does is scope the activity so it's eligible before it runs, execute it, and package the proof of execution so your claim goes through cleanly the first time.
How often do Microsoft incentive programmes change?
Expect a major refresh every fiscal year, starting 1 July - and FY27 is a bigger shift than most, moving to scenario-based AI, Security and Azure-growth investment programmes with a stricter proof bar. There are smaller mid-year updates too. Rebuild your marketing plan around the new guide each summer, and re-check eligibility before you commit spend.
Getting incentive money claimed isn't really about knowing the programmes - Microsoft publishes all of that. It's about running marketing that's eligible by design and evidenced as it goes, and in FY27 that discipline is worth more than ever. That's exactly the gap we plug at Resultful: scoping partner activity so it qualifies, executing it, then packaging the proof so the claim actually lands.