Microsoft Partner Incentives: What Changed in FY26

Dateline: July 16, 2026. Microsoft’s FY26 ran July 1, 2025 to June 30, 2026 and has now closed. FY27 began July 1, 2026. This post describes what changed during FY26 under the Microsoft AI Cloud Partner Program (MAICPP, formerly the Microsoft Partner Network), and which of those mechanics partners still have to manage going into FY27.

Direct answer: During FY26 Microsoft rebuilt its partner incentives: CSP incentives were rebuilt around three levers (a core baseline, a strategic-product accelerator and a growth accelerator) under Microsoft Commerce Incentives, with part of the earning paid as an automatic rebate and part accruing as claim-based co-op. Unusually, the new rules applied retroactively to July 1, 2025, with recalculations and clawbacks executed in February 2026. The practical message for partners: in this program, paid is not always final, and some of the richest dollars are gated by attribution that is easy to misconfigure.

Microsoft is the most complex incentive environment in the channel - a dozen-plus programs, each with its own attribution, caps and claim windows. Here is what changed and where the money actually moves.

The structural change: three solution areas, three CSP levers

Microsoft consolidated its commercial business from six solution areas to three: AI Business Solutions, Cloud & AI Platforms, and Security. Your Solutions Partner designation is earned through the Partner Capability Score, which is measured across performance, skilling and customer success and has to clear a minimum threshold to qualify. Since January 1, 2026 you must hold a designation to access Azure IP co-sell benefits and most partner-led incentives.

On the CSP side, the incentive rebuild mattered most for payouts. The old structure gave way to three levers: a Core baseline, a Strategic Product Accelerator on priority products, and a Growth Accelerator on eligible growth. And here is the part that changed behavior: the earning was split between an automatic rebate and claim-based co-op - meaning a substantial share of what a partner earned did not arrive as cash, but as funds it had to actively spend, evidence and claim, or forfeit. The rate on each lever and the size of that split are set by Microsoft per fiscal year and published in its partner portal.

Lever 1 leak: Partner Earned Credit and the attribution trap

The single most common way Microsoft partners lose money is not a rate cut - it is a configuration error.

Partner Earned Credit (PEC) is the credit you earn on the Azure consumption you actively manage under CSP. But it is paid only when attribution is correctly set - PAL or admin-on-behalf-of, configured per customer environment. If that attribution is missing or misconfigured, the credit is not paid. The eligibility was there; the attribution was not.

It is worth keeping the mechanisms straight, because they are not interchangeable. PAL and DPOR attribute managed Azure consumption. CPOR is a separate, claim-based mechanism: Microsoft’s own documentation describes it for Microsoft 365 and Dynamics 365 customers. Different plumbing, different incentives, different failure modes.

For a partner managing meaningful Azure consumption, this is one of the highest-value lines in the entire relationship, and one of the easiest to lose to a setup oversight. Auditing attribution coverage across every managed customer is one of the most profitable hours a channel team can spend.

Lever 2 leak: the co-op slice that expires

Because the FY26 model paid part of CSP incentives as co-op funds, a meaningful share of earnings was claim-based, and claim-based money expires if unused or improperly evidenced. Microsoft sets an earning threshold below which the co-op portion converts to all-rebate; above it, that portion has to be claimed with proof of execution. Both the threshold and the split are portal-gated and reset each fiscal year, so the number to work from is the one in your own incentive guide.

This is the same kind of leak as Dell’s MDF and most vendors’ marketing funds, but at Microsoft’s scale the slice partners may miss can be substantial. Partners who treat co-op as “marketing’s problem” rather than a tracked revenue line forfeit real money every period.

Microsoft MDF, and what Partner Center calls it instead

Partners search for Microsoft MDF. Microsoft’s own documentation does not use the term. The page that governs this money is Incentives Co-op and Claims Overview, where Microsoft defines it as “cooperative (co-op) marketing funds,” which are “funds that you earn through Microsoft Incentive Programs by claiming reimbursement for activities that support Microsoft product awareness.”

The confusion is reasonable, because MDF is the word the rest of the channel uses and most partners carry one vocabulary across every vendor they sell. Across the channel, MDF and co-op are two different instruments: MDF is discretionary money allocated in advance against demand you have not created yet, while co-op accrues out of revenue you have already transacted. At Microsoft, market development is not a separate pot at all. It is one of three categories of eligible co-op spend, alongside demand generation and partner readiness, and it is where telemarketing, seminars, tradeshows and customer offers sit.

So the translation is simple: if you are hunting Microsoft MDF in Partner Center, look under Incentives, then co-op.

The clock that forfeits the money is not the one most partners watch. Microsoft runs co-op on fiscal-half cycles and splits them into three windows that do not line up. You accrue in an earning period. You have to spend during the usage period that follows it. You file during a claiming period of its own. Microsoft’s wording on the deadline that actually bites: “If you don’t use your earnings by the end of the usage period, you forfeit them.” The expiry is tied to spending the money, not to filing the paperwork, so a partner can sit comfortably inside the claiming window with funds that are already gone.

What a claim needs is defined per activity, not as one checklist. Proof of execution for a digital campaign is the screenshot, the landing page URL and a results summary. For a tradeshow it is the invitation, the agenda and a photo showing you were there. For telemarketing it is the script, the call volume and the campaign dates. Some activities, television and radio among them, additionally require pre-approval before the activity runs rather than after. And Microsoft can ask for original documents long after the activity, so a claim that was paid is not a file you can close.

Two things co-op does not cover, both easy to assume the wrong way. It is not the route for Online Services Advisory Sell or the Online Services Usage programs, which claim through CPOR instead. And below a Microsoft-set threshold the co-op portion converts to rebate at the end of the semester, so a smaller partner may find there is nothing to claim and no reimbursement to chase.

The exact windows, thresholds and eligible-expense caps are the ones in your own incentive guide in Partner Center. What does not reset is the shape: earn, spend, evidence, claim, in that order, on a clock you do not control.

The new risk: retroactive recalculation and clawback

This is the change partners should study hardest. Microsoft applied its FY26 rules retroactively to July 1, 2025, then in February 2026 re-ran earnings under the new rates - adjusting both over- and under-payments, with clawback for partners that failed to meet FY26 requirements. Two things are worth being precise about here, because the headline version overstates it: partners who met the requirements were not clawed back, and where the recalculation came out lower than what a partner had already received under FY25 rules, partners kept the higher amount. The exposure was real, but it was conditional.

The implication is still a mindset shift: you cannot model Microsoft incentives as money in the bank the moment it is paid. You have to model exposure - what could be recalculated or clawed back if a designation lapses or a requirement is missed. October and November 2025 payouts were also delayed to January 2026, which added a cash-flow planning wrinkle on top.

Two items already on the record

Partner University closed on June 15, 2026. Its assessments fed skilling points toward designations (notably Modern Work). With it gone, partners moved to exam- and certification-based skilling paths, and a skilling-path disruption can drop a Partner Capability Score below the designation threshold, taking incentive eligibility with it. If you have not re-checked the skilling paths that depended on it since it closed, that is the first place to look.

FY27 is already underway. It began July 1, 2026. Microsoft sets out each new year’s priorities at its MCAPS Start for Partners event (the FY27 theme: “Frontier Transformation”), with continued emphasis expected on AI, security and marketplace. Do not assume FY26 rates carried over into FY27; the rates that apply to you are the ones in the current, dated incentive guide in your portal. The direction of travel was already visible in March 2026, when the Sentinel Accelerator was restructured from a daily-ingestion model to a monthly-usage model with new qualification, activation and stabilization criteria - a sign of where the new money is being steered.

Where a registered deal sits in all of this

Microsoft’s incentive story is mostly about attribution and claims rather than deal registration, and that is itself the thing worth knowing. On most vendor programs an approved registration is the gate the incentive hangs on. Here the equivalent gate is usually who is attributed to the customer, through PAL, admin-on-behalf-of or CPOR, and it is a configuration state rather than a one-time form.

The practical consequence is a different failure mode. A partner used to the Dell or IBM pattern goes looking for a registration record to explain a missing payment, and on Microsoft the answer is more often an attribution that was never set, a designation that slipped below its threshold, or a co-op claim that was never filed. Same question, different plumbing: what condition was this money resting on, and is that condition still true?

And the designations behave like a ladder even though Microsoft does not present them as tiers. A Solutions Partner designation is earned per solution area through the Partner Capability Score, so a partner can hold one and not another, and each one carries its own access to co-sell and partner-led incentives. There is no single company-wide level to check. There are as many as you have solution areas, and any of them can lapse on its own, which is why the Microsoft AI Cloud Partner Program umbrella tells you so little about what you actually earn.

How to capture more now that FY27 has started

Four moves. First, audit PEC attribution across every managed Azure customer; this is the highest-value, lowest-effort fix. Second, track your co-op balance and claim deadlines so the claim-based slice does not expire. Third, model clawback exposure, not just earnings, against your designation and specialization requirements. Fourth, re-check your skilling paths now that Partner University has closed, so no designation slips below its threshold. Then pull your FY27 incentive guide and re-baseline every rate you were planning against, because none of the FY26 numbers can be assumed forward.

Doing this by hand across a dozen-plus Microsoft programs - each with distinct attribution, caps and windows - is where almost every partner falls behind. That is precisely the tracking Rebates-On centralizes: one view of every Microsoft incentive, attribution and co-op deadline, alongside every other vendor you sell - with the next action that earns or protects more.

Further reading: What changed is one question. What the money is actually paying you for is another, and the answer differs by vendor. Microsoft, Dell, HP and HPE, side by side

Vendor Program Watch tracks what changes in each vendor’s program and what it means for your rebate payouts. See the vendors we support →

See where Microsoft incentive revenue may be at risk: Get a rebate audit · Get the quarterly read: Subscribe to Vendor Program Watch

On sources: this post describes the structure of Microsoft’s partner program as reported through secondary channel sources - distributor and consultancy summaries such as Crayon and TD SYNNEX, plus Rebates-On’s own internal program research. It is not drawn from Microsoft’s own program documentation, and we do not publish Microsoft’s rates. Microsoft’s incentive rates, splits and thresholds are portal-gated, reset each fiscal year, and vary by region and product. For the figures that apply to your organization, use the dated incentive guide in Partner Center. This post describes mechanics, not rates.