Why "Review Failed" on Azure Marketplace Co-Sell Doesn't Always Mean Something's Broken

A "Review failed" badge on Partner Center's Solutions overview under IP Co-sell Eligible Revenue Validation usually just means your product hasn't crossed $100,000 in billed Marketplace revenue yet — not that a document or configuration is broken. That threshold is Policy 3000.2.2, a hard revenue gate for the IP Co-sell Eligible incentivized status, separate from and above plain "Co-sell Ready." It's easy to miss that distinction and burn real time chasing the wrong problem.

Why does a complete submission still show a low document count?

The rejection notice pairs the "Review failed" badge with a document count that looks incomplete — something like "3/6" — and the instinct is to assume a document didn't upload correctly or a field is misconfigured. But Partner Center's Documents section has exactly 6 named slots: a solution one-pager and pitch deck (required), a reference architecture diagram (required for SaaS offers only), and three optional slots (customer case study, verifiable customer wins, channel pitch deck). Anything uploaded outside those exact named types — a "Solution Overview" doc, a "Pilot Deployment" doc, anything with a name Partner Center doesn't recognize — lands in a separate "Other documents" bucket and never increments that counter, no matter how complete your actual document set is. So a real, thorough submission can still show "3/6" forever, which looks exactly like a broken upload even when nothing is wrong.

What should you actually check first?

Open the real rejection email or in-app notification and read the specific policy number it names. If it says 3000.2.2, there's nothing to fix on your end — it resolves itself once billed Marketplace revenue crosses the $100K threshold, and importantly, failing this policy does not demote your existing Co-sell Ready status. You keep what you already have; you just don't advance to the next tier yet.

This is worth knowing before it happens to you, because the fix for a genuinely broken document (a stale Solution Play dropdown, a missing required file, a formatting rejection) looks completely different from the fix for "you haven't hit $100K yet" — and confusing the two wastes a submission cycle chasing a problem that was never there.