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.Issues with Partner Support
I am having some problems with Partner support (created a ticket over a month ago and they kept asking for information saying that it was ok and then asking for the same information again and in the last two weeks they just ignore the emails). I am wondering if anyone else has have similar issues in the past and how can we escalate this (Usually based on the v- account I can contact some of my contacts in Microsoft and they can help me escalate within the team, but it seems that the partner support team uses the generic email address removed for privacy reasons)?
App Source Canvas App - how to prevent customers seeing code and functionality
We are a small ISV and have published a PowerPlatform solution with a canvas app. While we published as a managed solution, etc. we are seeing that our customers can edit the app and see all the code and functionality we've built. Our 2025 plan includes ramping up several new App Source offerings with Canvas Apps included, but we won't be doing that if we can't protect our efforts and someone can easily replicate. Any help or guidance is greatly appreciated! After a customer purchased this solution, this is what they can see when selecting "App" - clearly you can see they can edit it and did confirm they can go in an navigate through the app in the editor and see al the code, etc. This is the solution view - it is working as expected by preventing the editing. This is the offer. Business Apps – Microsoft AppSource
Mastering the Marketplace: How to Build a Co-Sell Narrative for Azure Marketplace via Salesforce
Are you an ISV looking to amplify your reach and skyrocket sales in Azure Marketplace? Co-selling on Azure Marketplace can be your secret weapon! Join our insightful webinar and discover proven strategies to craft a co-sell narrative within Salesforce and propels your solution to new heights. Our cloud experts will equip you with the knowledge to: Craft a Value-Driven Narrative: Learn how to articulate the unique value proposition of your solution combined with Azure. Automation via Salesforce: Learn how automation via Salesforce helps in creating private offers in Azure Marketplace and how it differs from the manual approach. Success Stories Sell: Explore strategies to develop compelling co-selling case studies on Azure Marketplace. Actionable Co-selling: Learn how to create a co-sell narrative that compels Azure Marketplace sales. This webinar is perfect for you if: You're an ISV with a solution listed on Azure Marketplace. You're looking to leverage Sales force to expand your reach on Azure Marketplace. You want to develop a co-sell narrative that positions your solution on Azure Marketplace. Don't miss this opportunity to unlock the full potential of co-selling in Azure Marketplace. Presented by: Amit Malik- Spektra Systems Register HerePrivate Plan with $0 Price
I have created an offer in the marketplace with two plans: one public with a listed price and one private priced at $0, available only to my tenant. This is mentioned in the FAQ here. https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-faq-publisher-guide#how-can-my-own-employees-use-our-offers-from-the-marketplace-without-being-charged- Do my employees still need to provide credit card information to use the private plan?Azure IP Co-sell Eligibility
As per documentation, one of the current requirements is: "At the organization level, generate at least USD100,000 of Azure Consumed Revenue or Marketplace Billed Sales (via the commercial marketplace), over the trailing 12-month period". Our solution naturally has low consumption rates; however, it plays a crucial role in helping end customers migrate and modernize their applications on Azure, thereby significantly driving ACR consumption for those customers. Question: Could our solution still be considered for IP Co-sell based on our customers' ACR increase?
