The Microsoft Publisher Agreement is the contract between Microsoft and each company that publishes listings and offers on Microsoft Marketplace. Its July 2026 update, effective July 1, 2026, names agents and MCP servers as AI Systems, adds obligations for offers that include one, changes the tax rules for multiparty private offer (MPO) partners, and adds terms for Dragon Copilot offers. Any publisher that kept a listing after July 1 accepted it.
Acme publishes a SaaS offer on Microsoft Marketplace with an AI agent built in, and sells its larger deals through a channel partner with multiparty private offers. Nobody at Acme signed anything in July 2026, and nobody had to: Acme kept its listing, and under the agreement’s own terms that was acceptance. What’s left is deciding who owns the obligations that came with it.
This guide sets Microsoft’s change history and the new text against the September 2025 version, then turns them into an owner-and-action matrix. It is a reading guide, not legal advice: have counsel read the agreement before you rely on any of it.
What is the Microsoft Publisher Agreement?
The Microsoft Publisher Agreement is the contract that governs your relationship with Microsoft for publishing listings and making offers available on Microsoft Marketplace, including your use of Partner Center to do it. You agree to it by publishing, or attempting to publish, a listing, or by using Partner Center’s publishing features.
The current text reads “Version: 8.0 July 2026 update” and “Effective date: July 1, 2026.” Its Learn page was last updated on May 26, 2026, and the update’s change history on May 27, 2026; Microsoft’s index of change histories lists nothing later. The update before it, September 2025, took effect September 30, 2025.
Five addenda follow the Terms and Conditions and “will control” where they differ. Three matter here: A (offer types, including the AI System terms), B (go-to-market channels, including multiparty private offers) and the new E (Dragon Copilot offers).
It is not the Microsoft Partner Agreement, which Cloud Solution Provider (CSP) program partners accept to take part in that program. That one is covered in the updated Microsoft Partner Agreement, explained.
Did your company accept the July 2026 update?
Yes, if anyone at your company kept using your Publisher Account, or kept a listing on Microsoft Marketplace, after July 1, 2026. The agreement says: “By continuing to use your Publisher Account or maintain your Listing in the Microsoft Marketplace after the changes become effective, you agree to the new terms.” The only alternative is to leave: “you must remove your Listings from the Microsoft Marketplace and close your Publisher Account.”
The agreement sets no general notice period for changes, only specific ones, such as 90 days before an increase to the Store Service Fee; Microsoft “may update this Agreement at any time and will notify you of such changes in Partner Center.” And under Section 11(a), notices go to the individual you name in Partner Center as “the primary contact for Partner Center notices and messages.” Check who that is today.
What changed in the July 2026 update?
The change history lists eight changes: an anti-corruption requirement in Sections 4 and 11, a longer AI System definition in Section 12, two new obligations for AI offers in Addendum A, new MPO geography and tax rules in Addendum B, and the new Addendum E for Dragon Copilot offers.
| Section | September 2025 text | July 2026 text | Applies to |
|---|---|---|---|
| 4(b) Local law | Comply with applicable laws, already including AI laws | Adds “(x) anti corruption laws (as Section 11(e) further clarifies)“ | Every publisher |
| 11(e) Anti-corruption | Not present | No action that violates anti-corruption laws, “including the U.S. Foreign Corrupt Practices Act”; Microsoft may suspend or terminate the agreement | Every publisher |
| 12(a) AI System | A machine-based system that infers how to generate outputs | The same definition, plus a list of components, from agents to MCP servers and RAG pipelines | Offers that are or include an AI System |
| Addendum A, 8(c) | Not present | Cooperate with Microsoft on external queries about the offer’s legal compliance | AI offers |
| Addendum A, 8(d) | Not present | A representation on training content and safeguards | AI offers |
| Addendum B, 1(b) MPO geography | Customer billing accounts in the U.S., U.K. or Canada; partner tax profiles for the U.S. or U.K. | ”eligible countries, set out in Multiparty private offers overview” | MPO ISVs and partners |
| Addendum B, 1(j) MPO taxes | ”U.K.-based Authorized Partners must complete applicable IRS W-8 form" | "Authorized Partners must complete applicable IRS W-8 form” | MPO partners |
| Addendum E Dragon Copilot | Not present | Healthcare fraud and abuse laws, a HIPAA Business Associate agreement per customer, and fees | Dragon Copilot Offers only |
Two details for anyone citing section numbers:
- The anti-corruption section is 11(e). The change history’s bullet says 12(e), but 12(e) defines Certification Requirements, and Section 4(b) points to 11(e). Choice of Law and Venue, URLs and Miscellaneous are now 11(f), 11(g) and 11(h).
- Addendum A’s 8(a) and 8(b) aren’t new, and neither are Addendum B’s terms for resale enabled offers. 8(b) now says “CE markings” where it said “marks.”
Who owns each change, and what should they do?
Give each change one owner and one action, starting with an inventory of your Microsoft Marketplace offers, because six of the eight changes apply only to offers that include an AI System, sell through MPO or are Dragon Copilot Offers. The agreement assigns every obligation to “you,” the publisher, so the owner column is our suggestion.
| Change | Owner | Action |
|---|---|---|
| Continued publishing after July 1, 2026 | Legal | File the July 2026 text, and check that the Partner Center primary contact is a current person who reads its messages |
| Offer inventory | Marketplace operations | Mark which offers include an AI System, which sell through MPO, and which are Dragon Copilot Offers |
| AI governance review (12(a), Addendum A 8) | AI governance or product security lead | For each AI offer, review prohibited practices, the documentation 8(b) requires and the 8(d) representation, and record the answer |
| Regulatory-inquiry owner (Addendum A 8(c)) | Legal or compliance | Name who answers a Microsoft query about an offer’s legal compliance, plus a backup |
| Anti-corruption (4(b), 11(e)) | Compliance | Confirm your policy and training cover marketing and selling through Microsoft Marketplace |
| MPO tax profile (Addendum B 1(b)) | Alliances or channel operations | Before each MPO, confirm the partner’s tax profile for the seller ID on the offer is complete and in an eligible country |
| MPO IRS form (Addendum B 1(j)) | The partner’s finance team, asked by your channel team | Get written confirmation of the applicable IRS form and, from a U.S. partner, of resale certificates on file |
| Dragon Copilot (Addendum E) | Healthcare compliance and finance | If you publish one: a Business Associate agreement per customer before handling PHI, a fraud-and-abuse review, and the 90-day payment-terms notice on the calendar |
Which of your offers include an AI System?
Any offer with an AI component the July 2026 definition covers, because Addendum A’s AI terms apply “If your Offer is or includes an AI System.” Section 12(a) keeps the September 2025 definition, a “machine-based system” that “infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions,” and adds:
AI Systems include AI models and AI-enabled software (including but not limited to user interfaces (UI), agents, APIs and inference endpoints, model context protocol (MCP) servers, plug-ins, skills and extensions, connectors, retrieval-augmented generation (RAG) pipelines, embeddings and vector stores, orchestration layers, guardrails and safety layers, and adjacent tooling).
So look inside each offer, not just at its category: an agent, an MCP server or a RAG pipeline inside a SaaS product is now named. Whether a given component counts is a question for counsel.
Section 8 of Addendum A then has four terms. Two were already there: 8(a) bars “prohibited practices under applicable law, including prohibited practices identified in Article 5 of the EU AI Act,” and 8(b) asks for “declarations of conformity, CE markings, and other documentation required by law.” Two are new:
- 8(c), regulatory inquiries: “If Microsoft receives queries relating to the compliance of your Offer with applicable laws or regulations, you will cooperate with Microsoft to respond to such external queries.” It sets no response time and names no channel, so make sure whoever reads your Partner Center messages knows who owns a query.
- 8(d), training and safeguards: “You represent and warrant that, to the best of your knowledge, no unlawful content, including child sexual abuse material, has been knowingly used in training the AI System, and that you have taken commercially reasonable measures to prevent the AI System from generating such content.”
The change history summarizes 8(d) as “reasonable measures to not train AI systems with unlawful content and prevent harmful outputs.” The clause’s qualifiers aren’t the summary’s, and we don’t interpret either: give your AI governance owner the clause.
What do multiparty private offer partners need now?
A completed tax profile in Partner Center in an eligible country, and the applicable IRS W-8 form, which the September 2025 text required only of U.K.-based partners. Both sit with the partner, who is a publisher too: Addendum B says the ISV and the Authorized Partner “are considered Publishers of Offers and are subject to the terms applicable to Publishers under the Agreement.”
Geography moved to a Microsoft list. The September 2025 text allowed customers “using a billing account based in the United States, United Kingdom, or Canada” and partners “with tax profiles for the United States or United Kingdom.” The July 2026 text reads: “MPO only will support sales to Customers that are using billing accounts and Authorized Partners with tax profiles in eligible countries, set out in Multiparty private offers overview.” On October 15, 2026, that overview had 37 countries and regions for customers and 36 for channel partners; Canada “isn’t a supported tax profile market for channel partners.”
The W-8 sentence now covers every partner: “Authorized Partners must complete applicable IRS W-8 form.” U.S.-based partners still “must provide a valid tax exemption certificate.” Microsoft’s tax-profile guide has publishers that satisfy certain U.S. residency requirements fill out an IRS W-9, and other publishers outside the United States an IRS W-8, online with the tax profile. Which form applies to a partner is a question for its tax adviser.
Before you create the offer:
- Get the partner’s seller ID, and have the partner check its tax profile. Microsoft requires “a completed tax profile in Partner Center associated with your Marketplace seller ID in an eligible country,” shown under Account settings > Payout and tax profiles > Tax profiles. A submission can take up to 48 hours to validate.
- Check Microsoft’s eligible channel partner list, a download Microsoft offers ISVs behind partner sign-in.
- For a U.S. partner, confirm resale certificates, filed through a support request “at least five business days before the sale,” or “sales tax might be charged on your purchase.”
- For a partner outside the United States selling to U.S. customers, raise withholding. Microsoft says such a partner “could be subject to withholding tax from their payout unless you have a valid tax treaty associated with your tax profile.”
In Fours, a multiparty private offer starts from New Resale Authorization on an Azure product, with Multiparty private offers as the type, and asks for the Partner’s seller ID and the Customer billing account ID, so run the checks against that seller ID first. Creating a multiparty private offer in Fours covers the rest of the form, and Microsoft resale enabled offers vs MPO compares MPO with resale enabled offers.
When do the Dragon Copilot terms apply?
Only if you “choose to publish a Listing and make your Offer available as a Dragon Copilot Offer”; otherwise Addendum E doesn’t apply. A Dragon Copilot Offer meets the applicable Certification and Certification Requirements and includes “Dragon Copilot Physician Apps and Agents,” “Dragon Copilot Radiology Apps and Agents,” and “Dragon Copilot Clinical App Connectors,” or is otherwise identified in Microsoft’s Documentation. If you publish one:
- Healthcare fraud and abuse laws apply to the offer, its assets and your marketing, “including the Anti-Kickback Statute,” the Medicare/Medicaid fraud and abuse laws and the Federal False Claims Act.
- You need a Business Associate agreement with each customer “before creating, receiving, maintaining, or transmitting PHI on behalf of such Customer.” You and Microsoft “are not Business Associates of each other as defined in HIPAA.”
- Fees can change. Microsoft “reserves the right to modify or revise the pricing and payments terms applicable to Dragon Copilot Offers at any time in its sole discretion,” with “no less than 90 days’ notice prior to an increase in the payment terms.”
Frequently asked questions
What is the Microsoft Publisher Agreement?
The Microsoft Publisher Agreement is the contract that governs your relationship with Microsoft for publishing listings and making offers available on Microsoft Marketplace, including your use of Partner Center. The current text is version 8.0, July 2026 update, effective July 1, 2026.
Do publishers have to sign the updated Publisher Agreement?
No. The agreement says that continuing to use your Publisher Account or maintain your listing after the changes become effective means you agree to the new terms. A publisher that doesn’t agree must remove its listings and close its Publisher Account.
Does the Publisher Agreement’s AI System definition include MCP servers?
Yes. Since July 1, 2026, it says AI Systems include AI models and AI-enabled software, with examples including agents, APIs and inference endpoints, MCP servers, connectors, RAG pipelines, embeddings and vector stores, and guardrails. Addendum A’s AI terms apply to any offer that is or includes one.
What changed for multiparty private offer partners?
Partners need a tax profile in a country on Microsoft’s eligible list, and every partner must complete the applicable IRS W-8 form, which the September 2025 text required only of U.K.-based partners. U.S.-based partners still need a valid tax exemption certificate.
Is the Publisher Agreement the same as the Microsoft Partner Agreement?
No. The Publisher Agreement governs publishing listings and offers on Microsoft Marketplace. The Microsoft Partner Agreement is the agreement Cloud Solution Provider program partners accept to take part in that program, and it has its own update and acceptance rules.
Takeaways
- Keeping a listing, or using your Publisher Account, after July 1, 2026 accepted the July 2026 update. There was nothing to sign.
- AI Systems now explicitly include agents, MCP servers and RAG pipelines; offers that include one owe Microsoft cooperation on regulatory queries and a training-content representation.
- MPO partners need a tax profile in an eligible country and the applicable IRS W-8 form. Check both against the seller ID before you create the offer.
- Name an owner for each change, starting with the Partner Center primary contact who receives Microsoft’s notices.
Fours creates Microsoft multiparty private offers for your channel partners and tracks each one from the partner’s review to the customer’s purchase. See how it runs partner-led deals in Fours’ private and partner-led offers.
Sources
Primary sources for the platform rules cited above. Last verified October 15, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- Microsoft Learn: Change history for Microsoft Publisher Agreement version 8.0 July 2026 update — Last updated May 27, 2026: the four reasons for the update (Dragon Copilot Offers, the expanded geographic scope of multiparty private offers, anti-corruption requirements, and the expanded definition of AI Systems); the changed sections, Sections 4, 11 and 12(a), Addendum A 8(c) and 8(d), Addendum B 1(b) and 1(j), and the new Addendum E; its summary of 8(d); its Section 11 bullet numbering the anti-corruption section 12(e)
- Microsoft Learn: Microsoft Publisher Agreement 8.0 July 2026 update — Version 8.0 July 2026 update, effective July 1, 2026, last updated May 26, 2026; acceptance by publishing, or by continuing to use the Publisher Account or maintain a listing after changes take effect, with removing listings and closing the account as the alternative; updates notified in Partner Center; the addenda controlling where they differ; 90 days' notice before a Store Service Fee increase; anti-corruption laws added to Section 4(b) and the new Section 11(e); the Partner Center primary contact for notices in Section 11(a); the AI System definition and its list of components in Section 12(a); Addendum A Section 8(a) to (d); Addendum B 1(b), 1(c) and 1(j) for multiparty private offers; Addendum E's definition, fraud and abuse laws, Business Associate agreement and fee terms
- Microsoft Learn: Microsoft Publisher Agreement 8.0 September 2025 update — The previous text, effective September 30, 2025, compared clause by clause: the AI System definition without its list of components; Addendum A 8(a) and 8(b) only, with 'marks' where July 2026 says 'CE markings'; multiparty private offers limited to customers with billing accounts in the United States, United Kingdom or Canada and partners with U.S. or U.K. tax profiles; the IRS W-8 sentence applying to U.K.-based partners; no Section 11(e) on anti-corruption; Addendum B Section 2 on resale enabled offers the same as in July 2026
- Microsoft Learn: Change history for Microsoft Publisher Agreement — Microsoft's index of Publisher Agreement change histories, whose newest entry on October 15, 2026 was the version 8.0 July 2026 update
- Microsoft Learn: Multiparty private offers overview — Last updated October 6, 2026: customers need a billing account ID, and channel partners a completed Partner Center tax profile, in a supported country or region; on October 15, 2026 the table had 37 for customers and 36 for channel partners; Canada isn't a supported tax profile market for channel partners
- Microsoft Learn: Multiparty private offers (for channel partners) — A completed tax profile associated with the Marketplace seller ID in an eligible country, checked under Account settings, Payout and tax profiles, Tax profiles; U.S. resale certificates through a support request at least five business days before the sale, or sales tax might be charged; partners outside the United States selling to U.S. customers could be subject to withholding without a valid tax treaty on the tax profile
- Microsoft Learn: Multiparty private offers (for software companies) — The partner must have a completed tax profile in Partner Center in an eligible country; the partner's seller ID under Account settings, Identifiers, Publisher; the multiparty private offer eligible channel partner list, behind Microsoft partner credentials
- Microsoft Learn: Set up Microsoft Marketplace payout and tax profiles — Publishers satisfying certain U.S. residency requirements fill out an IRS W-9 and other publishers outside the United States an IRS W-8, online with the tax profile; a tax profile submission can take up to 48 hours to validate
- Microsoft Learn: The Microsoft Partner Agreement (MPA) for CSP — The Microsoft Partner Agreement is the agreement Cloud Solution Provider program partners accept online in Partner Center to participate in the CSP program, with its own acceptance rules (Global admin acceptance, implicit acceptance in some scenarios, explicit acceptance in certain countries or regions) and its own update, effective December 1, 2026
- Fours docs: Azure Marketplace CPPO — Fours behaviour: a multiparty private offer is created with New Resale Authorization on an Azure product and the Multiparty private offers type, with the Partner's seller ID and Customer billing account ID fields; Pending Partner Action while the partner configures the offer, and Pending Purchase until the customer completes the purchase
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn