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.AppSource Marketplace bugs
Hi everyone, We recently noticed some bugs on the Marketplace, such as the call-to-action button displaying “CTA_Get” instead of the correct label. I’m curious—has anyone else experienced similar issues? It’d be great to know if this is isolated or more widespread. Thanks for sharing your feedback!
Publishing a SaaS offer for PowerApps a canvas app in AppSource
Hello, We have been trying for many months now to publish our PowerApps canvas apps as a SaaS offer, thereby allowing us to have transactable, licensed customers. Through a lot of effort, we managed to get some support where we were told quite vaguely how to achieve this, but without any meaningful guidance we are struggling as we are a small ISV with expertise in our actual business, and Power Platform. We are not, however, experts in SQL (that's being generous) or in creating APIs which seem to be a requirement to keep track of user licenses and feeding the data to our canvas app. If anyone here has any info on this, or how they might have achieved it themselves it would be massively appreciated, as we can't seem to get there by ourselves and MS support is very difficult to find. It does feel as though the app development part is so much simpler than getting it onto the marketplace, which is surely the wrong way round. Thank you, CraigISV Success FAQ: Are their limitations for use of the Azure Sponsorship credits?
Q: Are their limitations for use of the Azure Sponsorship credits (offered as part of ISV Success)? A: Azure Sponsorship must be used within 12 months of joining the ISV Success program. Due to current technical limitations Azure Sponsorship also can not be used on Microsoft Customer Agreements (MCA) or Cloud Solution Provider (CSP) agreements. Azure Sponsorship also can not be used to purchase Reserved Instances (RI) or (Reserved Capacity (RC). Note: this FAQ is relevant to participants in ISV Success. Learn more about ISV Success here.
Managing your marketplace community subscriptions
As the marketplace community continues to grow, I recommend managing your subscriptions to get the content most relevant to your top areas of interest, at the right time. About Labels and Subscriptions: You may have noticed that posts within this discussion forum contain labels such as "Build," "Publish," "Grow," and "ISV Success." These labels are applied to help you identify focused on specific marketplace topics (Building apps for the marketplace, publishing apps, growing your sales of apps on the marketplace, etc.) There are similar labels applied to all blogs on the marketplace blog: "Thought Leadership" - includes content on best practices, interviews with marketplace partners, etc. "Roadmap & Functionality" - any content related to the marketplace roadmap and new features/functionality You can "subscribe" to certain labels based on your areas of interest, which allows for a more customized community experience. For example. on the marketplace blog site, if you are most interested in Roadmap & Functionality content. you can adjust your settings to be notified immediately when new content with this label is published. And if you are interested in other topics, such as ISV Success, you can still subscribe, but just elect to receive notifications less frequently. Starting with subscriptions Refer to this general help article on subscriptions and notifications: Managing Preferences, Subscriptions and Notifications - Microsoft Community Hub If you're not a member of the Tech Community already, create an account at techcommunity.microsoft.com Manage your subscription settings so that you can receive email updates on the content you are interested in. Manage these settings by selecting your profile icon in the top right corner of the community, selecting "My Settings," and selecting "Subscriptions & Notifications. You can also subscribe to the entire marketplace community which will provide you with regular updates on all marketplace discussion topics happening in this forum. To do this, click "follow" in the upper right corner of the marketplace community homepage. Getting Started in the Community: General information about starting on the community can be found via these resources: Getting Started on the Tech Community - Microsoft Community Hub Contributing to the Community - Microsoft Community HubPartner Opportunity to Contribute to the Copilot Roadmap
Microsoft Partners - We're sharing an opportunity with you to contribute to the Copilot roadmap. Voice your company's thoughts on what features and capabilities Microsoft should build to help ISVs build, deploy, and monitor Copilots. Complete this survey (5-10 mins) by EOD 11/22 to influence the Copilot roadmap: https://forms.office.com/r/nv6EPTfYFhFAQ: MACC Decrement for SCE Agreements
Q: My customer is looking at a Marketplace purchase, but their MACC is on an SCE (Server and Cloud Enrollment) agreement and not on an MCA (Microsoft Customer Agreement). Can they transact this under their SCE and still have it decrement their MACC? Is that possible? A: The agreement type does not apply. What matters is the purchase and if it is applicable to the MACC. We have information on this here: Maximize investments with Microsoft Azure Consumption Commitment (MACC) benefit - Microsoft marketplace | Microsoft Learn
