Microsoft changed what it takes to stay authorized in the Cloud Solution Provider program, with new authorization requirements taking effect on October 1, 2025 as part of the FY27 program year. The changes touch direct-bill partners, distributors, and indirect resellers, and they affect both whether you can transact and whether you earn incentives.
The requirements below are drawn from Microsoft’s published guidance as summarized by distributors and partner-community sources. Where those sources disagree, this post says so. Treat the table as a checklist of what to verify in Partner Center, not as a substitute for it.
| Area | Direct-bill partner | Indirect reseller |
| Revenue threshold | Reported as $1 million trailing-twelve-month CSP revenue. | A minimum trailing-twelve-month revenue requirement, reported in one source as $1,000. New resellers are not held to it until they complete 12 months. |
| Solutions Partner designation | At least one required. | Not required for authorization. |
| Security | Complete the mandatory Partner Center security requirements, including multifactor authentication for all administrative users and a named security contact. | Same mandatory security requirements. |
| Agreement | Accept the direct-bill Microsoft Partner Agreement. | Accept the indirect reseller Microsoft Partner Agreement. |
| Vetting and support | Capability assessment and an Advanced or Premier support plan, per partner-community summaries. | Business vetting. |
| If you fall short | Microsoft requires a transition to indirect reseller status. A partner that transitions must transact as an indirect reseller for twelve months before reapplying for direct bill. | A partner that does not meet all thresholds is not eligible to remain authorized and may reapply 12 months after offboarding. |
Sources: Work365, Ingram Micro, Kaseya, 4Sight, licenseq, and reseller.co.nz summaries of Microsoft guidance. The indirect revenue figure and support-plan details differ across sources. Verify in Partner Center.
Being authorized to transact is not the same as being eligible for incentives. For FY27 Microsoft tied incentive eligibility to revenue and to either a Solutions Partner designation or points on the Partner Incentive Capability Score. As summarized by partner-community sources, direct-bill partners need $1 million in trailing revenue plus a designation, and indirect resellers need $25,000 in trailing revenue plus either a designation or 25 capability score points.
The designation also has to match the solution area. Modern Work incentives call for a Modern Work or Security designation. Business Applications incentives call for the Business Applications designation. Azure incentives call for Data & AI (Azure), Digital & App Innovation (Azure), or Infrastructure (Azure).
Follow the chain and you can see why CSP compliance is not a licensing problem alone.
Each step happens in a different part of Partner Center, and each is owned by a different person. The Solutions Partner designations are explained in our post on the six designations. The point here is that the CSP program and the designations are one system, even though they are managed as two.
| Item | Cadence | Owner | Evidence to keep |
| Partner Center security requirements (MFA, security contact) | Continuous; check monthly | IT / security lead | Screenshot or export of status |
| Solutions Partner designation and score | Per Microsoft assessment | Practice lead | Score breakdown and certification list |
| Revenue against authorization threshold | Monthly | Finance or licensing lead | Trailing-twelve-month report |
| Incentive eligibility by solution area | Quarterly | Licensing lead | Designation or points per area |
| Microsoft Partner Agreement version | On change | Legal or operations | Accepted agreement and date |
| Subscription renewals | Monthly | Account manager | Renewal calendar by customer |
Microsoft’s partner programs generate a steady stream of announcements, and an equally steady stream of third-party summaries. When those summaries disagree, partners need a way to decide what to act on. Here is a process that works for any vendor, not only Microsoft.
Cloud Solution Provider status affects how you bill and support Microsoft customers, so changes carry commercial weight. Treat requirement changes as a project: identify what is affected, estimate the work, assign an owner, and set a date. A requirement you cannot meet by its effective date is a commercial risk, not an administrative one.
A habit worth keeping: Keep a running log of Microsoft partner announcements with the link, the date you read it, and the effective date. When sources disagree later, you can show what you knew and when.
Answering these four questions in writing turns a vague worry into a plan, and it gives you something to show leadership when they ask where you stand.
Secondary sources reported FY26 requirement dates inconsistently. Use Microsoft’s own Partner Center announcements as the authority and record the date you relied on.
No. They are related parts of Microsoft’s partner ecosystem with different requirements. Track each separately and note any dependency.
Check the current rules for transfers and any monitoring Microsoft applies, and confirm your own status before starting a move.
AltamIQ: AltamIQ connects the pieces Microsoft keeps in separate screens: certifications, designations, CSP requirements, and renewal dates, alongside every other vendor you carry. It is partner portfolio management for the firm holding the statuses, not a PRM for the vendor issuing them.