FAQ: Is private plan or private offer better for Year 2 for co-sell eligible publisher?
Q: I'm a publisher that published a private plan for year 1 and am now at the verge of publishing a private plan for year 2. I'm now contemplating whether to go with a private plan or private offer. I am co-sell eligible becaues of the first year deal. If I publish a private plan for year 2, can the client use that for MACC decrement or does it has to be a private offer? A: Private plan or private offer will both do the trick, however there's more functionality available with a private offer. Flexible billing options most importantly. It's also becoming the more common customer purchasing experience. Last but not least, the reporting provides much more information when it's a private offer than a private plan, so our recommendation is to go with the private offer.
Error when i try to test deploy our Azure application offer solution from marketplace
Hi All, We have published our azure app offer and recently went live successfully. But when i try to access it from marketplace and test the deploy as a customer by giving all the parameters, i got below error at the end. I have reviewed the templates and i dont see anything wrong. And all test passed with the azure testing tool. Please advice if you come across this error and help us in fixing this. Thank you.Explore Curated Marketplace Resources
Good morning, afternoon, evening community! I wanted to introduce myself; I am Stephanie, a pug and plant lover, and a leader in Marketplace FastTrack at Microsoft. I am here to help you streamline your Marketplace journey through curated self-serve resources to help you go further, faster. Reach out if you have any questions, feedback, or need help to publish an offer or win an imminent deal. 📘 Looking for a guide on publishing and transacting on the Azure Marketplace? Explore the Marketplace Playbook. ⚙️ Need to simplify SaaS offer creation? Use the open-source code on Git Hub for SaaS Accelerator. 🎥 Want to learn how flexible billing can unlock new deal structures? Learn more about Flexible Billing. Use Mastering the Marketplace videos and labs to upskill end-to-end. 💸 Bringing an off-Marketplace renewal or renewing a Marketplace offer? Don’t forget the agency fee discount. 🤖 Have you tried the App Advisor or Partner Center AI Assistant? We’d love your feedback!No plans are available for the selected subscription
I've set up a SaaS offer in the Azure Marketplace and created a free plan for testing purposes. However, when attempting to subscribe to the offer, I encounter an issue: No plans are available for the selected subscription, despite configuring both yearly and monthly plans. Additionally, a paid plan has been configured. Please see the screenshot below for reference.Do you need admin privilege to purchase on AppSource?
Hi Community, We are an ISV and publish Apps on AppSource. I’ve always assumed that anyone with a valid email and credit card could purchase a product through AppSource. The requirements on this Microsoft page seem to support that: https://learn.microsoft.com/en-us/marketplace/purchase-software-appsource However, I recently discovered that only Microsoft 365 admins can access order details in the Admin Center. For example, clicking on your badge in AppSource, View all orders in Admin Center, redirects you to this link: https://admin.microsoft.com/Adminportal/Home#/subscriptions/apps But if your account isn’t an admin, you’ll see this message: Switch to an account that has permission Your account (xxxxxx) doesn’t have permission to view or manage this page in the Microsoft 365 admin center. This is confusing. If any user can initiate a purchase, why can’t they view or manage their orders? And if only admins are meant to complete or manage purchases, why is the checkout process open to all users? Would appreciate any clarification or official guidance on this. Thanks!
Azure App Service Web Job Access
We have published a Managed App that includes a backend Web Job hosted on an Azure App Service, we did not use Azure Functions because this process can run for many hours. I understand some architectural thoughts could make it work, that change may come in the future. However, right now. We have the Plan configured to allow Partner owner access. But when I look at the web jobs on a customer environment I am unable to start the web job or view the logs of the web job. When I attempt to view the logs going through the Managed Applications Center I get this error: How do we get permission to run a job or view the logs? I would have thought owner access would be sufficient.Multitenant and Marketplace publishing, issue with Solution Designation
We have our solution published on Microsoft Marketplace using Partner Center. This is first / main Partner center MPN Location and Microsoft tenant in Europe. Now publishing requires having Solution Designation. We need to publish this solution on another MPN Location / Microsoft tenant in US. On the second / child tenant, we did not reach the Solution Designation, so it is not active. Therefore, we are unable to publish solution on Microsoft Marketplace due to missing Solution designation. Should Solution Designation status be automatically inherited from partner (main) to child tenant / locations? How can we grow revenue etc to reach solution designation, if we cannot publish (already successful) solution on Marketplace.Multitenant and Marketplace publishing, issue with Solution Designation
We have our solution published on Microsoft Marketplace using Partner Center. This is first / main Partner center MPN Location and Microsoft tenant in Europe. Now publishing requires having Solution Designation. We need to publish this solution on another MPN Location / Microsoft tenant in US. On the second / child tenant, we did not reach the Solution Designation, so it is not active. Therefore, we are unable to publish solution on Microsoft Marketplace due to missing Solution designation. Should Solution Designation status be automatically inherited from partner (main) to child tenant / locations? How can we grow revenue etc to reach solution designation, if we cannot publish (already successful) solution on Marketplace.
