Cost side: support is getting more expensive
Support is shifting to revenue-based pricing. Microsoft’s next-generation partner support offering, Unified for Partner (UfP), announced at Ignite 2025, modernizes partner support with pricing tied to a partner’s CSP cloud business revenue, rather than a flat fee. In practice, that means as a small partner’s revenue grows, their support costs scale up proportionally — support becomes a percentage tax on growth rather than a fixed, predictable line item a small shop can budget around.
It arrives alongside broader price increases. Microsoft’s July 2026 Microsoft 365 price hikes range from 5% to 43% depending on SKU, with frontline worker plans jumping 33%. These increases hit the CSP channel too, alongside Enterprise Agreement and direct web pricing, meaning partners face higher underlying product costs at the same time support economics are shifting.
Free training/enablement resources are being cut. Partner University — a resource partners used to qualify for Solutions Partner designations and specializations — is being retired effective June 15, 2026, affecting partners pursuing the Modern Work Solutions Partner designation and related specializations. Losing a free enablement pathway right as designation requirements tighten pushes partners toward paid alternatives to stay qualified.
Value side: support is thinning out
The “partner-first” model shifts the burden onto partners themselves. UfP is explicitly described as a partner-first model where partners lead support and Microsoft acts as a backstop — a structural change from Microsoft doing first-line resolution to partners fielding issues themselves before Microsoft engages, even though partners are paying for the privilege.
Response times remain slow relative to the stakes. On Partner Hub Support, users can expect a response within five business days of raising a ticket, with escalations taking up to eight business days. For a small partner with an urgent customer-facing issue, a business-week-plus wait is a significant gap between what’s being paid for and what’s delivered.
The rollout itself adds friction. UfP is being introduced through a phased approach — pilots with select partners now, gradual expansion in H1 FY27, and general availability only in H2 FY27 — meaning most partners are stuck in the older support model through at least a chunk of 2027, with unclear timing on when improvements (or cost changes) will actually reach them.
Compliance and administrative overhead has grown alongside stagnant support. The Partner Center Security Score is now a mandatory requirement for all CSP partners, covering things like MFA enforcement, and combines with new reconciliation processing changes (a new ReferenceId JSON format required before June 15, 2026) that partners must implement on their own — effectively unpaid support labor for interoperating with Microsoft’s systems, layered on top of what they’re already paying for.
The net effect small partners describe
Put together: pricing that scales with revenue rather than staying flat, fewer free enablement resources, a support model that pushes first-line resolution onto partners, and response-time SLAs measured in business days rather than hours. For a large partner with dedicated support staff, this is manageable — even beneficial, since revenue-based pricing may undercharge them relative to ticket volume. For a small partner, it looks like: paying more as they grow, doing more of the technical legwork themselves, and waiting longer for Microsoft to step in when they can’t solve it alone. That’s the “cost up, value down” complaint in a nutshell — though it’s worth noting UfP hasn’t fully rolled out yet, so its real-world track record is still unproven.