Blog Post

Marketplace blog
4 MIN READ

Agentic Marketplace publishing expands with broader product coverage and generally available APIs

Akshat_Singal's avatar
Akshat_Singal
Icon for Microsoft rankMicrosoft
Oct 20, 2026

When we introduced Marketplace Ingestion Model Context Protocol (MCP), the idea was simple: help developers start with what they want to accomplish, rather than with an API payload. 

Now, that workflow can go further. 

Marketplace Ingestion MCP and APIs have reached 100% product coverage for Microsoft Marketplace offers, giving publishers more ways to bring Microsoft Marketplace publishing into the development processes and tools they already use. We’ve also reached another important milestone: the Product Ingestion APIs for SaaS and virtual machine offers are now generally available (GA). 

Together, these updates give development teams more flexibility in how they build Marketplace publishing into their workflows, whether they work with an AI agent through Marketplace Ingestion MCP, integrate directly with APIs, or combine both approaches.   

From agentic publishing to broader product coverage 

In my previous post, I shared how Marketplace Ingestion MCP connects natural-language intent with Microsoft Marketplace publishing actions. 

That experience now supports a broader range of Marketplace products. With 100% product coverage across our MCPs and APIs, publishers can apply the same outcome-first approach across their Marketplace publishing workflows. 

Marketplace Ingestion MCP connects supported agentic experiences with Partner Center APIs. Instead of manually constructing API payloads, you can describe the publishing outcome you want. Your agent can then help retrieve the right schema, build and validate the payload, and perform supported publishing actions. 

For development teams, that means publishing can become part of the workflow rather than a separate activity after development is complete. 

SaaS and virtual machine APIs are now generally available 

Publishers that prefer to integrate directly with Marketplace publishing APIs also have an important update: Product Ingestion APIs for SaaS and virtual machine offers are now generally available. 

These APIs give development teams a programmatic way to create, publish, and manage their offers in Microsoft Marketplace. With these APIs now generally available, publishers have another way to build Marketplace publishing into their development and release processes. 

For teams already using the APIs, there is no need to immediately rework integrations built with older preview versions. Existing preview API versions continue to work. You can continue using those versions in your current integrations while adopting to the GA versions. 

If you're starting a new integration, we encourage you to use the latest generally available API versions for SaaS and virtual machine offers. 

Choose the workflow that works for your team 

There isn't one way every publisher needs to work. 

Some teams may want an agent-assisted experience, using natural language and Marketplace Ingestion MCP to handle more of the translation between publishing intent and API structures. Other teams may work directly with the Product Ingestion APIs to build publishing into automated processes. And some teams may combine both. 

The opportunity is to make Marketplace publishing fit more naturally into how your team develops and ships software. 

You can: 

  • Start with intent. Use Marketplace Ingestion MCP to describe the publishing outcome you want and let your agent help translate it into supported actions. 
  • Build repeatable workflows. Bring common offer creation and update tasks into development workflows, including CI/CD processes where appropriate. 
  • Integrate directly with APIs. Use the generally available Product Ingestion APIs for SaaS and virtual machine offers to build programmatic publishing experiences. 
  • Move forward at your own pace. Existing integrations using older preview API versions continue to work, giving teams flexibility in when they adopt the latest GA versions. 

What this means for publishers 

The goal is straightforward: give developers more flexibility in how they bring their cloud and AI solutions to customers through Microsoft Marketplace. 

Marketplace Ingestion MCP brings publishing closer to the tools and agentic workflows developers already use. The Product Ingestion APIs provide the foundation for teams that want direct programmatic integration. With expanded product coverage and GA APIs for SaaS and virtual machine offers, publishers have more options for building Marketplace publishing into the way they already develop and operate their products. 

If you've been exploring agent-assisted publishing, now is a good time to take another look. And if you're building directly with the Product Ingestion APIs, consider using the latest generally available SaaS and virtual machine API versions as you create new integrations. 

Get started 

Marketplace Ingestion MCP is included with access to Microsoft Marketplace submission APIs. To get started, you'll need: 

  • A Partner Center account with the required role 
  • Access to Microsoft Marketplace submission APIs 
  • An MCP-compatible client, such as Visual Studio Code or GitHub Copilot CLI, if you want to use Marketplace Ingestion MCP 

Learn more: 

Publishing doesn't need to sit at the end of development. With agent-assisted workflows, broader product coverage, and generally available APIs, teams have more ways to make publishing a natural part of how they build and bring solutions to market. 

Updated Oct 20, 2026
Version 1.0
No CommentsBe the first to comment