App name blocked on Marketplace submission
Hello everyone, I'm reaching out to the community in hopes that someone has encountered a similar issue and can provide guidance. We’ve developed a new app that we’re ready to submit to the Microsoft Marketplace with a transactable offer. However, during the submission process, we’re encountering a roadblock: when entering the desired app name, we receive the following message: "The name is not available." I contacted email address removed for privacy reasons for clarification, as the name isn’t currently used by any other app or offer and doesn’t appear to violate Microsoft’s naming conventions. They redirected me to Partner Center Support, where I was informed that the issue is being reviewed internally. Unfortunately, I haven’t received any clear explanation or resolution so far. To support our case, we’ve demonstrated that: We own the domain name associated with the app name. We have 16 other products and apps with a similar naming convention, ensuring brand consistency. Despite this, we’re still waiting for a response. Has anyone else faced a similar issue? Any advice on how to navigate this or expedite the process would be greatly appreciated. Thank you in advance for your help!
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
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, CraigHow can I accommodate payment plans where the amounts differ per term?
When selling our SaaS solution we typically have a 3 year contract with annual payments. We always use private offers. Generally the contracts have 3 equal payments. But in some cases the payment amount differ per term. At this moment I need to create multiple private offers to accommodate this. In some cases I have to wait two years to have the customer activate their last subscription. For example, a payment schedule Year 1 = 100.000 Year / Year 2 = 150.000 / Year 3 = 250.000 This would result into 3 Private Offers with different starting dates which shows to be confusing for our customers. How can I make a Private Offer with 1 plan where the amounts differ per term(year)?
Critical! SaaS App review and rating synchronized with the wrong AppSource App!
First of all. THANK YOU SO MUCH for finally making a synchronization between the SaaS App and the corresponding App in AppSource. HOWEVER! the SaaS app is synchronizing with the wrong App in AppSource. This is critical, I don't have time for support to first acknowledge it and then find time to make the fix. I need this to be done immediately. Can a responsible please take action. The problem. In AppSource I have a free version - iPlanner Free - that only offers 20% of the App that is purchased using the SaaS App - iPlanner Pro. The free version have pure ratings in compare to the Pro version. I of course don't want customer to use the free I want them to purchase the Pro with the SaaS App. In my Marketplace listening I am connecting the SaaS App to iPlanner Pro in AppSource. For that reason it is odd why you guys synchronizing with the wrong app. The problem is taking the review and rating to the SaaS app makes my subscribed based app look very bad. This is highly critical and is also very wrong. The reviews shown on the SaaS app comes from the wrong app. I would appreciate if this can be fixed asap. I am sure you guys can see that it is critical. Thank you and happy holydays to all in the community.A story about our journey on the marketplace. I hope it will inspire and help on your journey
I would like to share my experience with publishing transactable apps on the Microsoft commercial marketplace, the Microsoft 365 App Certification Program, Marketplace Rewards, and certified software designations. Starting with publishing our apps on to the marketplace: We have several apps that operate within the context of Microsoft 365, including apps for Outlook, Microsoft Teams, Copilot Agent, Office, and SharePoint. We have been in AppSource for many years and have customers worldwide. We developed an in-house license application to manage our customers' licenses. Before the commercial marketplace, we managed all invoicing and license management manually. Now, everything has become much easier. We have published monetized SaaS apps connected to the AppSource apps. Using the SaaS Fulfillment API, we integrated the purchasing process with our in-house license application. We have gained numerous benefits, including: Significant time savings in the invoicing and billing process, as purchasing, adding, removing, or cancelling licenses is automated and managed by Microsoft Customers appreciate the ability to manage licenses themselves, finding it easier Improved market awareness due to promotion in the marketplace And new customers are joining regularly. It is also important to mention Marketplace Rewards, which offer various benefits. For example, customer case stories can be published through Marketplace Rewards on Microsoft customer case stories. Here is a link to our latest story: Microsoft Customer Story - Design for Leisure improves efficiency 30% with iGlobe solutions and Microsoft Planner. Additionally, the Transact & Grow Incentive Campaign has provided us with financial incentives through marketplace sales, as well as Azure sponsorship credits to offset deployment costs. Considering these advantages, there is potential to make the apps CSP Ready as well: https://aka.ms/P2PeBook. Equally important is obtaining the Microsoft 365 App Certification. Certification confirms that an app solution is compatible with Microsoft technologies, compliant with cloud app security best practices, and supported by Microsoft. This is significant because: It provides certification from Microsoft, confirming app security and compliance It saves time in the sales process, as security and compliance are already verified It makes the app easier to find on AppSource, the Commercial Marketplace, and in the Teams App admin portal, where it will be listed in a special category Achieving sales in the marketplace, having customer case stories, and obtaining the Microsoft 365 App Certification provides the foundation to obtain Certified Software Designations, which come with additional benefits and opportunities for co-selling with Microsoft. Today two of our apps have achieved the Certified Software Designation for Modern Work. Soon iPlanner Pro for Teams that includes a Copilot Agent will follow as well. I share this story not to boast but to inspire and motivate others. There is nothing exceptional about us or our experience here – it can be completely replicated by leveraging the resources that Microsoft provides. Was it all very easy…. No. Is it doable? Yes!
