If you’re planning FY27 co-op spend, here’s what’s different and what still hasn’t changed.
Microsoft has updated several parts of the co-op funding programme for FY27. Many partners are now trying to work out whether the rules have fundamentally changed or whether this is mostly a documentation and governance refresh.
This blog is here to help you navigate the changes and plan ahead.
Co-op funding is earned from eligible Microsoft incentive activity. Under the Microsoft Commerce Incentives co-op model, 40% of eligible incentive earnings are accrued as co-op funding, while the remaining 60% are paid as a rebate. The co-op portion is accrued every six months and deposited into Partner Center, where it can be used for approved marketing and enablement activities.
Microsoft still applies the same minimum earning thresholds: $1,500 for Surface and $10,000 for Cloud Solution Provider (CSP) and Hosting. If a partner does not reach the threshold, the amount generally does not become a usable co-op balance and is instead converted into a rebate payment.
Funding earned in H2 FY26 (January–June 2026) is available for use in H1 FY27 (July–December 2026), while funding earned in H1 FY27 becomes available in H2 FY27.
For funding used in H1 FY27 (July–December 2026), claims must be submitted by 15 February 2027, and Proof of Execution (POE) must be approved by 31 March 2027.
For funding used in H2 FY27 (January–June 2027), claims must be submitted by 15 August 2027, and POE must be approved by 30 September 2027.
The approval deadline is the one that matters most. A claim submitted on time can still fail if invoice corrections, missing evidence, or POE clarifications are not completed before the approval window closes.
The biggest operational change is the updated activity-category structure. The FY27 activity categories are not a one-to-one match with older FY26 definitions. A campaign that was previously submitted under one category may now belong under a different category, so copying last year’s mapping is no longer a safe approach.
Microsoft has also introduced tighter spend caps for specific categories. Marketing Automation is capped at 3%, Partner Organisation Incentives at 2% and Sales Performance Incentive Funds (SPIFFs) are capped at 2%. These caps do not change the total amount of co-op funding you have earned. They restrict how much of that earned balance can be allocated to each capped activity type.
The most significant day-to-day change is the stricter POE standard. Third-party invoices now need to clearly show the vendor, the specific deliverable, the campaign or activity, the date and the amount. Generic descriptions such as ‘marketing services’ are becoming increasingly difficult to defend during review.
One thing that has not changed is the Allocated Resource cap, which remains at 50% for FY27. Microsoft has already indicated that this cap is expected to shrink in FY28, so partners relying heavily on internal-resource claims should start planning for a lower limit in the next cycle.
Before any co-op-funded campaign goes live, ask these five questions:
- Is the activity mapped to a valid FY27 category?
- Will the supplier invoice clearly describe what was delivered?
- Are expenses broken out into clear, itemised line items that match the claim categories?
- Does any category exceed its FY27 spend cap?
- Can all POE be submitted and corrected before the approval deadline?
If the answer to any of these is ‘no’, do a bit more planning before you launch the campaign or submit the claim.
This is where a lot of confusion is happening.
Microsoft’s newer performance-gated investment programmes are not the same as traditional co-op funding. They are funded through separate investment mechanisms and are not simply replacing or reducing the co-op pool.
Traditional co-op funding is still earned from eligible CSP, Hosting and Surface incentive activity and validated through POE. Performance-gated programmes, by contrast, are tied to customer usage, adoption, revenue growth or consumption metrics after deployment.
So if you’re hearing that ‘Microsoft now cares about usage’, that conversation relates to those newer investment programmes, not to the traditional co-op claims discussed in this blog.
We unpack that distinction in detail in our blog: [Why Microsoft Is Starting to Care About Usage After Deployment].
FY27 is not a complete reinvention of co-op funding. The earning model remains familiar, but the compliance and audit layer has become much stricter.
For most partners, the real challenge is structuring campaigns, invoices and claims correctly the first time.
That’s exactly where Blacfox helps.
We help partners plan FY27 campaigns that are both claim-compliant and commercially effective. That means aligning activities to the correct FY27 categories, structuring claims and POE for smoother approval and resolving issues before submission. But we don’t stop at the paperwork.
We also execute the funded campaigns, deliver the marketing assets and activities that generate measurable pipeline and provide the evidence needed to support the claim. In practice, we handle both the co-op mechanics and the campaign delivery, so your team can focus on converting opportunities rather than managing funding administration.
In other words, you don’t need to spend hours decoding policy updates or second-guessing claim structure. We handle the funding mechanics so your team can focus on running campaigns that generate pipeline.
