isv success
153 TopicsMicrosoft Ignite- Meaningful Announcements That Create Real Movement
Now that we are officially in 2026, I want to reflect back on Microsoft Ignite as it was more energized than ever. There is real momentum right now across Microsoft Marketplace, and the most meaningful shift I am seeing is around REO( Reseller Enabled Offer )capability. This is opening the door for partners to take Marketplace offers and bring them directly into new regions, new customer segments, and new routes to market without adding operational friction for either side. A true channel selling motion! For ISVs, REO means you can authorize trusted partners to resell your Marketplace offer in the way that works best for the customer. You no longer need to manage every deal yourself. For partners, it means instant access to in demand AI and security solutions that customers are already asking for. It removes barriers, it speeds up the process, and it connects the ecosystem in a much more natural way. If anyone in the community is exploring REO, private offers, multiparty models, or Marketplace strategy in general, it would be great to hear from you or reach out and would love to discuss. Looking forward to connecting with everyone in the new year. justinroyal'Unknown Error' while completing Microsoft ISV Success Sign Up
While completing my ISV Success signup, after pressing 'Agree and Continue' and verifying all input fields, it shows me "An unknown error occurred, please try again later". Why is it showing this error? All the fields have been filled correctly. Can someone assist me with this? Has anyone else faced and resolved this error? I have attached the screenshot of the error as well. Thanks.Solved108Views0likes1CommentTransitioning SaaS Offers with Multi-Year Pricing from AppSource to Azure Marketplace
When a SaaS transactable offer on Microsoft AppSource includes a pricing plan for more than 1 year, the offer is delisted from AppSource and becomes available on Azure Marketplace. This is due to the platform's structure: AppSource primarily supports monthly or annual subscription models for SaaS offers. Any pricing model that exceeds 1 year (e.g., 2-year, 3-year plans) is outside the scope of AppSource’s transaction capabilities. When a SaaS solution introduces https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-commercial-transaction-capabilities-and-considerations, it is automatically transitioned to Azure Marketplace, which can accommodate longer-term contracts and subscription models (such as 2-year, 3-year, or longer terms). Azure Marketplace is designed for more complex transactions, including multi-year deals, and supports deeper infrastructure integration and contract management features compared to AppSource. Thus, any SaaS offer that requires multi-year pricing terms will shift from AppSource to Azure Marketplace, where such transactions can be handled effectively.Scale smarter: Discover how resale enabled offers drive growth
Friday, December 5 | 11:00 12:00 PM GTM+1 online event Discover how resale enabled offers (REO) help software development companies scale through the Microsoft Marketplace by simplifying transactions, expanding reach and accelerating co-sell opportunities. Why attend? Simplify multi-party transactions Expand your global reach through resellers Accelerate co-sell opportunities and close more deals Reserve your spot now to start unlocking new growth opportunities🤔Finding alignment with Channel partners as an ISV?
Hi all! We're new to the MS ecosystem. Spent the last 15 years developing products for the Salesforce ecosystem, which is very direct sales heavy. We've launched our app https://marketplace.microsoft.com/en-us/product/Office365/WA200008222 which is a native and robust integration between Salesforce and Microsoft Teams. We listed just this year in March 2025. We're attending Microsoft Ignite for the first time, and it's clear we need to have a channel partner strategy. Microsoft claims there are over 500k partners - my question to the group (especially ISV partners): how do you find channel partners effectively that align to your product and strategy? Where do we even start? We obviously have an affinity towards partners that serve Saleforce and MS Teams customers. Thanks in advance!!165Views3likes2CommentsYou’ve built your app, it’s on Marketplace… now what?
Your solution is live on Microsoft Marketplace – so what’s next? How do you make the most of this opportunity? What benefits can you unlock? And what practical steps will set you up for long-term success? As a Partner Solutions Sales Manager at Microsoft, I work with partners every day who’ve just published to Marketplace and want to accelerate their impact. That’s why I’ve launched a new blog series designed to help you go beyond “listing” and start thriving. In this first edition, I share: Best practices for getting started How to move from visibility to real growth The key signal that shows your solution is well-architected …and more. Check out the full post on the Marketplace Community Blog: Your next big move: Thriving in the reimagined Microsoft Marketplace | Microsoft Community HubNew To The Community
Hello ISV Success Community, As a new member to the community, I decided to start with an introduction. I’m Aubin Bakana, Founder and CTIO (Chief Technology & Innovation Officer) of Baobab Logix LTD, now based in Leeds, UK. I lead technology and innovation, driving solutions that are secure, ethical, and intelligent. At Baobab Logix, we’re building future-ready platforms that empower businesses to thrive. One of our flagship innovations is KeepComm Intel, a next-generation contact center solution that combines AI-driven automation with human-in-the-loop architecture for speed, accuracy, and trust. As a Microsoft Azure Solutions Architect Expert, Harvard CS50 certified, and full-stack developer, I bring deep technical expertise and a vision for sustainable innovation. I’m here to connect, collaborate, and share insights with fellow innovators who believe in shaping technology for good. Looking forward to engaging with this amazing community and exploring opportunities to build impactful solutions together! thank you.SharePoint Embedded guide for software companies
Looking to accelerate your SaaS solution with SharePoint Embedded? This new blog post breaks down key success factors, positioning strategies, and how to align your architecture for maximum impact. Read the full article here: SharePoint Embedded guide for software companies: success factors, positioning & key insights | Microsoft Community HubApp Advisor updates: Build smarter, publish faster with these new features
The App Advisor experience has been enhanced to help you build smarter and publish faster to the Microsoft Marketplace. The six new features make it easier to stay focused, move faster, and scale smarter with apps and agents. Whether you are in the planning, building, or publishing phase of your journey, the new features are designed to meet you where you are, offering curated guidance and actionable insights. Learn how the updates can help you today. Build smarter, publish faster: Here’s what’s new in App AdvisorVulnerabilities Introduced in CNAB after using cpa buildbundle
Hi, this is my first post here. I am following the instructions in the article https://learn.microsoft.com/en-us/partner-center/marketplace/azure-container-technical-assets-kubernetes?tabs=windows%2Clinux2 I used the command cpa buildbundle to build and upload the CNAB to my Azure Container Registry (ACR), but the Defender scan shows vulnerabilities in the CNAB bundle, even though my solution image is free of vulnerabilities. I also scanned the image with Trivy and found Critical and high vulnerabilities in Helm 3, kubectl, and the Docker Engine (Moby). The approach mentioned in the technical asset mounts the Docker engine of the host machine to the Microsoft's image mcr.microsoft.com/container-package-app:latest. My host machine has the Community Edition of Docker Engine, yet the Moby issue persists . Inside the container, I tried running `tdnf clean all && tdnf update`, which updated Moby, but I was unable to update kubectl and Helm. Should I be concerned about these vulnerabilities? I believe they may have been introduced by the CPA tool. The documentation states that for marketplace listings, the repository must be free of vulnerabilities. Additionally, it mentions in the limitations section that single containers are not supported, and my current offering contains only single image. Any tips on how I can address this issue or any remediation steps would be greatly appreciated. Thanks! AsifSolved612Views0likes6Comments