Connect development and Marketplace publishing
Marketplace Ingestion MCP and Product Ingestion APIs now support every Microsoft Marketplace product, giving publishers more options for incorporating publishing into development and release workflows. Explore agent-assisted publishing, direct API integration, and generally available SaaS and virtual machine APIs. Existing preview integrations continue to work, so teams can adopt the latest versions at their own pace. Read the blog: Agentic Marketplace publishing expands with broader product coverage and generally available APIsHow software companies can expand their SMB reach with Microsoft Marketplace and AI
How can software companies turn a Microsoft Marketplace presence into greater customer reach and growth? Explore how Microsoft Marketplace can help software companies connect with more small and medium business (SMB) customers, support scalable sales, and expand into new markets in the age of AI. The article highlights Ntegral’s evolution from a traditional systems integrator to a software company with more than 300 enterprise solutions and deployments in more than 150 countries. You’ll also get a preview of what Ntegral President and CTO Dexter Hardy will bring to Ultimate Partner LIVE Reston, including practical perspectives on building beyond a Marketplace listing, developing pipeline, reaching SMB customers, and incorporating AI into a broader growth strategy. Read the full article to discover how Marketplace, AI-powered innovation, and an SMB-focused product strategy can work together to create new opportunities for software companies. 👉 Explore now: How software companies can reach more SMB customers through Microsoft Marketplace in the age of AIWork IQ Cost and Pricing Model for Agents published in Marketplace
I would very much like to ask for assistance and input in regards of "Consumption, cost forecasting, break-even analysis and recommended customer pricing. " I believe a bit of context is required. We are about to publish two Work IQ MCP Agent in Marketplace. Both agents will be integrated to our existing Apps that are published in Marketplace. 1. iGlobe CRM for Teams and 2. iPlanner Pro for Outlook and Teams. Both Apps are multitenant Apps running on customers own tenant. The Apps can only be deployed from Marketplace. Lets use iPlanner Pro Agent as an example. In short, iPlanner Pro Agent uses Work IQ and MCP tools to understand emails, meetings and Microsoft 365 context, while iPlanner Pro turns that intelligence into structured Planner execution, including the appropriate plan, bucket, assignment, priority and supporting email context. Including saving the email or attachments on the task. A prompt could look like this "Find the latest email from email address removed for privacy reasons. Create a task for in Planner, put it in the correct Plan and bucket, assign it to the appropriate owner, set a due date for next week and save the email on the Planner Task" Work IQ and MCP provide context and intelligence, iPlanner Pro executes the structured actions, and Microsoft Planner remains the source of truth. To my understanding Work IQ API usage is billed through Copilot Credits rather than a separate per-user Work IQ license. Microsoft 365 Copilot includes Work IQ functionality within native Microsoft Copilot experiences, but third-party solutions such as iPlanner Pro consume Copilot Credits when they call Work IQ APIs. Work IQ does not require a separate API subscription, SKU or per-user licence. API usage is consumption-based and is measured in Copilot Credits. Work IQ operation Credit consumption Planning note Chat API Variable Depends on grounding, retrieval and reasoning complexity. Context API Variable Depends on the scenario and the sources used. Tool API 0.1 credit per API call Static component: $0.001 per call at $0.01 per credit. Example: 1,000 Tool API calls consume 100 credits, equivalent to $1.00 at the planning rate. Now here comes my confusion. 1. How do we know how many credits we are using with a prompt like the example I showed? the consumption is 0.1 credit per API call. 2. If I understand the above correct, the total consumption is calculated on the customer tenant. That consumption includes much more than just iPlanner Pro. Is that correct? 3. OR, will the sum of all customer using iPlanner Pro Agent be direct to us and we will be billed based on the total consumption of all our customers? If that is the case ( I don't think it is) then how do we know how much each customer consumed? 4. If consumption and billing is on the customer, how can the customer see what iPlanner Pro cost in consumed credits? This is important in regards of giving a cost forecast for customers. I am sure they would want that before start using the Agent. It is also important in regards of the question of if we should charge or offer it as a free agent? If we are billed then we will need to change for it. If the customer is billed then we probably will not be able to charge for it. I hope I have been able to explain my confusion. I tried asking contacts I have at Microsoft, but unfortunately haven't heard anything. That is why I am asking in the community. Have any one else the same challenge? what have you done? Can Microsoft assist here? I will be happy to take a Teams call and others are welcome to join. Thank youBring Marketplace publishing closer to your development workflow
Explore how AI agents can help make Microsoft Marketplace publishing a more natural part of the development workflow. Marketplace Ingestion MCP connects MCP-compatible agent tools with Partner Center APIs, helping publishers turn natural-language intent into supported publishing actions. Learn four ways teams can incorporate agent-assisted publishing into their workflows, from creating and validating offers to building repeatable processes and working from familiar developer tools such as Visual Studio Code and GitHub Copilot CLI. See how publishers can bring product development and publishing closer together while keeping people involved in reviewing and approving changes. Read the articleGrow partner-led business in Japan with multiparty private offers
Explore how multiparty private offers in Japan help software companies and channel partners collaborate on customer opportunities through Microsoft Marketplace. Learn how multiparty private offers, resale enabled offers, and distributor-reseller models can help partners expand their reach and scale partner-led sales. Read the blog to learn about multiparty private offers in Japan: 日本で加速するチャネル成長: Multiparty private offer で広がる Microsoft Marketplace の可能性 | Microsoft Community Hub (Article in Japanese and English)Monetize cloud and AI solutions with SaaS offers
SaaS offers on Marketplace help software and AI companies monetize cloud-based solutions while simplifying how customers discover, purchase, and access applications. This short video explains how SaaS offers enable organizations to sell solutions hosted in their own tenant, support Microsoft 365 integrations, and streamline purchasing experiences across familiar Microsoft tools such as Copilot, Teams, and Outlook. Watch to learn how Microsoft Entra ID, Marketplace fulfillment APIs, and flexible pricing models help support subscription management, upgrades, renewals, and long-term growth. Whether you're bringing a new SaaS solution to market or looking to expand your Marketplace strategy, SaaS offers can help you reach customers where they already work and scale globally through Marketplace.
Could Marketplace Become an AI Discovery Agent?
Today, customers still find apps in Marketplace by searching keywords or browsing categories. In a large catalog like the Marketplace, that often feels like guesswork. Publishers describe similar solutions differently, and customers rarely know the exact keywords to use. Many customers end up scrolling through listings, getting tired, and leaving. When that happens, we as publishers never get the chance to connect with them. What if Marketplace used AI to change that? Instead of searching, customers could simply describe what they need: “I need a time-tracking app that works natively in Microsoft 365 and Microsoft Teams, has light project management, follows our security policies, and keeps all company data inside our tenant in line with General Data Protection Regulation (GDPR).” An AI agent could instantly suggest the best matching apps and guide the customer directly to Get it now. And maybe the next step is even bigger: What if Marketplace became an agent or coworker for Microsoft Copilot, helping users discover and install the right apps simply by asking? Curious what others think—could this be the future of Marketplace discovery?Turn your SaaS application into a revenue-ready offer with Microsoft Marketplace
Building a great SaaS application is just the beginning. Turning that innovation into a transactable offer requires the right approach to tenant isolation, subscription lifecycle management, billing, security, operations, and Marketplace onboarding. The Agentic Road to Revenue explores how Git-Ape SaaS skills can help software companies move from SaaS concept to a commercially ready Microsoft Marketplace offer. Follow the Contoso Outdoors journey to see how an agentic, repository-driven approach brings architecture decisions, Marketplace integration, fulfillment and metering, security, operational readiness, and Partner Center onboarding into one practical path. Whether you’re planning your first transactable SaaS offer or refining an existing Marketplace strategy, this article offers a useful blueprint for turning technical decisions into a scalable commercialization plan. Read the full article to explore the agentic path from SaaS application to Microsoft Marketplace revenue: The Agentic Road to Revenue
Using OneDrive workspaces to maintain QBR history and monitor quarterly account performance changes
Hi Marketplace community, I wanted to share a practical Microsoft 365 agent pattern we have been working on for recurring account-review workflows. In merchant services, quarterly business review preparation often starts with the same basic ingredients: a CSV or TSV export, a set of merchant accounts, performance metrics, PowerPoint scorecards, and follow-up notes. The challenge is not just generating one review. It is maintaining a repeatable QBR history across many accounts and making it easier to spot what changed from one quarter to the next. With https://marketplace.microsoft.com/en-us/product/WA200010195, we are exploring a Microsoft 365-native workflow where the agent helps account teams: - Generate QBR scorecards for one merchant or multiple merchant accounts from CSV/TSV data. - Create PowerPoint outputs for each account. - Save each run into an organized OneDrive workspace. - Maintain an index of accounts and per-account status for the run. - Support follow-up workflows with draft email content. - Use sample workbook content to demonstrate quarter-over-quarter change detection across volume, authorization performance, acceptance cost, disputes, and refunds. The core adoption pattern is simple: use OneDrive not just as file storage, but as the persistent workspace for recurring business reviews. Each QBR run becomes easier to revisit, share, compare, and operationalize. For teams managing many customer or merchant accounts, this turns QBR preparation from a one-off deck-building task into a more durable account-performance workflow. I would be interested to hear how other Marketplace builders are approaching similar patterns: - Are you using OneDrive or SharePoint as the durable workspace for agent-generated outputs? - How are you helping users compare business performance across reporting periods? - Are customers asking for more “history and change tracking” rather than just one-time generated artifacts? The app is listed on Microsoft Marketplace here: https://marketplace.microsoft.com/en-us/product/WA200010195Learn how leading partners turn Microsoft Marketplace into a co-sell growth engine
A transactable Marketplace offer is just the beginning. In this expert blog, Reis Barrie, Founder and CEO of Carve Partners, shares four key practices top-performing partners use to help sellers drive co-sell success and accelerate growth through Microsoft Marketplace. Discover how to integrate Marketplace into your sales process, equip sellers with actionable account insights, identify stronger co-sell opportunities, and scale customer incentive programs. You'll also learn common pitfalls to avoid and practical ways to strengthen your Marketplace go-to-market motion. Read the blog to learn how leading partners transform Marketplace from a listing into a repeatable revenue growth strategy. Join us live on September 10 as Reis expands on these insights and answers your questions during an interactive Q&A session. Read the blog: Four things leading partners teach their sellers to turn a Marketplace listing into co-sell growth Add event to your calendar How leading partners drive co-sell success with Marketplace
