Here’s a situation for a customer: 

Earlier this year they set up a marketplace listing to process a transaction for a specific customer. They created this as a standard listing, with just one private plan, so it stayed private entirely – and because of this, we named it & entered content in a way specific for that customer. It was approved as IP co-sell incentivized and enrolled as qualifying toward Azure consumption commitment before they customer transacted.

We’d now like to create a generic transactable listing, which would be public (with placeholder pricing – we’d still transact all deals as private). I’ve been working with the ISV Success team – have cc’d Sofia, my main contact – on how best to do this. I’m happy to create a new listing or rename & update the existing one. However:

ISV Success team tells them for an offer to become co-sell eligible, we need to first transact 100k on that specific offer. They suspect an exception was put through for the prior transaction. 
ISV Success team told them if they were to rename the existing co-sell eligible offer, the co-sell eligibility process would be restarted, and the prior transaction would then not count toward that 100k

I’m hoping you can shed some light on this, and advise on how to handle? We aren’t (at this point in time) looking to use the marketplace to drum up new business; our existing Azure customers want to use it to pay us because they have MACC. But if they can’t, they’ll pay us directly. We wouldn’t have a scenario to process a 100k transation that doesn’t qualify for MACC drawdown.

​Here’s a situation for a customer: 
 
Earlier this year they set up a marketplace listing to process a transaction for a specific customer. They created this as a standard listing, with just one private plan, so it stayed private entirely – and because of this, we named it & entered content in a way specific for that customer. It was approved as IP co-sell incentivized and enrolled as qualifying toward Azure consumption commitment before they customer transacted.
 
We’d now like to create a generic transactable listing, which would be public (with placeholder pricing – we’d still transact all deals as private). I’ve been working with the ISV Success team – have cc’d Sofia, my main contact – on how best to do this. I’m happy to create a new listing or rename & update the existing one. However:
 

ISV Success team tells them for an offer to become co-sell eligible, we need to first transact 100k on that specific offer. They suspect an exception was put through for the prior transaction. 
ISV Success team told them if they were to rename the existing co-sell eligible offer, the co-sell eligibility process would be restarted, and the prior transaction would then not count toward that 100k

 
I’m hoping you can shed some light on this, and advise on how to handle? We aren’t (at this point in time) looking to use the marketplace to drum up new business; our existing Azure customers want to use it to pay us because they have MACC. But if they can’t, they’ll pay us directly. We wouldn’t have a scenario to process a 100k transation that doesn’t qualify for MACC drawdown.  Read More

​