Stopping at co-sell ready
Many ISVs reach co-sell ready status, see their solution appear in Microsoft’s internal catalog, and wait for referrals. Few arrive. Co-sell ready makes your solution visible to Microsoft sellers. It doesn’t give them a reason to bring it into their accounts.
The next status provides that reason. Only Azure IP co-sell eligible offers count toward a customer’s MACC, earn the Microsoft preferred solutions badge, and come with incentives for Microsoft sellers.
So ISVs that stop at co-sell ready miss most of what makes co-selling worth the effort.
How to fix: Make Azure IP co-sell eligible status the target from day one, and track your progress toward the $100,000 revenue threshold.
Only receiving referrals, never sending them
Co-sell works in both directions. Many ISVs accept referrals from Microsoft but never share the deals they’re already working on.
That keeps them invisible to the Microsoft sellers who manage their target accounts. A seller can’t help with a deal they don’t know about. They’re also unlikely to send new opportunities to a partner who has never shared one.
Outbound referrals also tell you things. Microsoft sellers can confirm whether a customer has an Azure commitment, who the decision makers are, and whether Microsoft is already in the account.
How to fix: Register every eligible deal in Partner Center where Microsoft manages the customer, and make it a standard step in your sales process.
Letting referrals go stale
Inbound referrals from Microsoft sellers are time-sensitive. If they sit untouched in Partner Center, they expire.
Each expired referral tells the seller who sent it that your team isn’t ready to co-sell. Sellers remember. A partner who doesn’t respond gets fewer referrals next quarter, and that reputation spreads through the region.
Usually nobody ignores them on purpose. Referrals land in a portal most of the sales team never opens, and the alerts go to one inbox.
How to fix: Route inbound referrals into your CRM automatically, acknowledge them the same business day and qualify them within 24 hours.
Closing deals off Marketplace
Some ISVs co-sell with Microsoft through the whole deal, then sign the contract on their own paper.
Under FY27 rules, that costs them. Microsoft now recognizes your impact mainly through Marketplace billed sales. A deal that closes outside Marketplace gives Microsoft little visibility into your contribution and does little for your co-sell standing.
The customer loses too. A deal signed off Marketplace can’t count toward their MACC, so you’ve given up your strongest commercial lever.
How to fix: Make a Marketplace private offer the default for every Azure customer deal, and build custom pricing and terms into it.
Keeping MACC out of sales conversations
Many MACC-eligible ISVs mention it on their website and in their listing, then never bring it up in a deal.
That usually happens because account executives don’t know what MACC is, don’t know how to ask about it or assume procurement will raise it. Procurement rarely does.
MACC changes the budget question entirely. A buyer who has no new budget for your product may already have millions in committed Azure spend they need to use before the term ends.
How to fix: Train account executives on MACC, add an Azure commitment question to every discovery call and state MACC eligibility on every proposal.
Using generic co-sell collateral
Many ISVs upload their standard product brochure as their co-sell one-pager. Microsoft sellers scan it, see nothing relevant to their accounts, and move on.
Microsoft sellers aren’t your buyers. They need to know which customers to bring you to, which Azure services your product uses, and why raising you in a meeting helps them.
How to fix: Write the one-pager and pitch deck for Microsoft sellers, covering target segments, the Azure services you use, MACC eligibility, and a named contact.
Running co-sell manually
Many teams start co-selling by copying deals between Partner Center and their CRM by hand. It works for a handful of deals and breaks at scale.
Manual work creates duplicate records, mismatched deal stages between systems, missed seller updates, and expired referrals. RevOps can’t report co-sell pipeline accurately, so leadership loses confidence in the channel.
Microsoft is also tightening data checks. Inbound referrals are now validated automatically, and API-submitted referrals must include Marketplace purchase intent. Incomplete data slows deals down.
How to fix: Sync Partner Center referrals with your CRM in both directions through a co-sell connector or a cloud GTM platform.
Letting IP co-sell eligibility lapse
Azure IP co-sell eligible status isn’t permanent. It depends on staying primarily platformed on Azure, keeping the offer transactable, and keeping your collateral current.
Several things can quietly put it at risk: moving part of a workload to another cloud, letting a pricing plan become non-transactable, or leaving outdated documents in Partner Center. Startups on the Acceleration benefit face a hard deadline. If they don’t hit the $100,000 milestone within 120 days, they lose the status.
How to fix: Review your co-sell status, Azure footprint, and Partner Center collateral every quarter, and assign one person to own them.
Treating the PDM relationship as transactional
Your Partner Development Manager (PDM) is your main link to Microsoft’s field teams. Many ISVs contact their PDM only when they need an introduction or a deal is stuck.
PDMs manage many partners and focus on the ones who make it easy to show results. A partner who regularly shares wins, pipeline and customer stories gets introduced to more sellers. A partner who only asks for favors gets introduced to fewer.
How to fix: Hold a monthly working session with your PDM covering recent wins, a target region or industry, and your pipeline goal for the next 90 days.