> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/partners/partner-administration/azure-marketplace-offer-types.md).

# Which Azure Offer Type Applies to You

Choose between an ISV-to-CSP Private Offer and a Multiparty Private Offer based on whether you own the customer's Azure consumption.

There are two ways to transact Archera through Microsoft Marketplace. Which one applies is determined by two questions: **who owns the customer's Azure consumption**, and **what billing agreement the customer is on**.

Read [Azure Marketplace Offers 101](https://docs.archera.ai/partners/partner-administration/azure-marketplace-offers-101.md) first if you have not — it covers the economics that apply to both.

***

## Pick your structure

```
Do you own the customer's Azure consumption?
(Is their Azure spend on YOUR CSP invoice?)
│
├── YES — they are on your CSP invoice
│   │
│   ├── Are you a Direct CSP or an Indirect Provider?
│   │   └── YES → ISV-to-CSP PRIVATE OFFER
│   │             Our default. Fastest to set up.
│   │
│   └── Are you an Indirect Reseller?
│       └── Margin flows through your Indirect Provider.
│             Tell us who your distributor is.
│
└── NO — what is the customer billed under?
    │
    ├── EA, MCA, indirect EA, or web direct
    │   └── → MULTIPARTY PRIVATE OFFER (MPO)
    │         The customer transacts in the marketplace
    │         themselves and you set your margin in the offer.
    │
    └── CSP, under a different partner
        └── MPO IS NOT AVAILABLE. See below.
```

{% hint style="danger" %}
**A CSP-billed customer cannot accept an MPO.** Microsoft restricts multiparty private offers to customers purchasing with an EA, MCA, indirect EA, or web direct billing account. CSP is not on that list. This catches people out because the partner is eligible — it is the *customer's billing account* that is not.
{% endhint %}

***

## Side by side

|                                    | ISV-to-CSP Private Offer      | Multiparty Private Offer (MPO)                    |
| ---------------------------------- | ----------------------------- | ------------------------------------------------- |
| You own the customer's consumption | ✅ Required                    | ❌ Not required                                    |
| Customer billing account           | CSP                           | EA, MCA, indirect EA, or web direct — **not CSP** |
| Customer transacts in Marketplace  | ❌                             | ✅                                                 |
| Premiums decrement customer MACC   | ❌                             | ✅                                                 |
| Microsoft settles with Archera     | ✅                             | ✅                                                 |
| Who bills the customer             | You                           | Microsoft                                         |
| Who sets the customer price        | You, off-marketplace          | You, in the offer                                 |
| Operational overhead               | Medium                        | High                                              |
| Typical customer segment           | SMB / cloud                   | Enterprise                                        |
| Typical partner                    | Direct CSP, Indirect Provider | SI firms, consultancies                           |

***

## ISV-to-CSP Private Offer

**Our most common partner motion, and the default for Azure CSP resellers.**

### How it works

We extend a private offer to you in Partner Center at your tier discount. You purchase the Archera subscription on behalf of your customer through Partner Center. The charge lands on your Microsoft invoice at the discounted price, and you invoice your customer at list price on their regular CSP bill.

The end customer never touches the marketplace transaction. From their perspective, Archera is simply a line on the invoice they already receive from you.

### You are eligible if

You are enrolled in Microsoft's CSP program as either a **Direct CSP** or an **Indirect Provider (distributor)**. Those are the two positions Microsoft allows a margin to be extended to.

{% hint style="warning" %}
**Indirect Resellers cannot receive the margin directly.** If you are an indirect reseller, give us the name of your Indirect Provider (distributor). We extend the offer to them, and they pass the margin through to you under your existing arrangement. This is a Microsoft program constraint, not an Archera policy.
{% endhint %}

### When it does not work

If the customer is on an EA or MCA with a MACC balance and their procurement team specifically requires the Archera fee to decrement that balance, this structure cannot satisfy that requirement. Route the deal to MPO instead.

In practice most CSP-billed customers have no direct MACC relationship with Microsoft, so this rarely comes up. How the Archera license is billed has no bearing on the savings generated for the customer.

### Setup

You need to be registered in Partner Center and provide your seller ID. Step-by-step walkthrough: [Set Up the Azure CSP Private Offer](https://docs.archera.ai/partners/partner-administration/azure-csp-private-offer-setup.md).

***

## Multiparty Private Offer (MPO)

**The right structure for SI firms and anyone who does not own the customer's consumption.**

### How it works

We create a private offer in Partner Center for you at a wholesale price. You set your markup — Microsoft calls this the "customer adjustment" — and extend the finished offer to the named end customer. The customer accepts and purchases through the Azure portal.

Microsoft then settles with Archera at wholesale and with you on your margin, separately. Both sides are paid through the marketplace.

### When to use it

* You do not own the customer's Azure consumption — they are Microsoft direct-bill, or on a different partner's CSP
* The customer specifically requires the Archera fee to decrement their MACC balance
* You want clean marketplace settlement rather than an off-marketplace invoice relationship

### Operational notes

MPO carries the most coordination overhead of the three. The flow is:

1. Archera creates the partner-facing offer and sends it to you
2. You set your customer adjustment and extend to the named customer
3. The customer accepts through the Azure portal

{% hint style="warning" %}
**Every handoff has an expiration window.** If the customer does not accept before the offer expires, it has to be recreated from scratch. Confirm the customer's procurement timeline before we create the offer and build in buffer — restarts are the single most common cause of MPO delay.
{% endhint %}

{% hint style="danger" %}
**Plan IDs are the thing to watch.** Every MPO generates a unique plan ID, and Archera emits metered premium usage against that specific plan ID. If you have multiple MPO deals running, confirm with us which plan ID is active for each customer. **Usage emitted against the wrong plan ID will not bill correctly**, and it is painful to unwind after a billing period closes.
{% endhint %}

### Setup

We need your Partner Center seller ID, the deal timeline, and the customer's Azure billing account ID. Raise the request at <partners@archera.ai> or in the shared Slack workspace.

***

## When the customer is on another partner's CSP

This comes up often enough to be worth its own section: a customer you want to bring to Archera buys their Azure through a CSP that is not you. You do not own the consumption, so ISV-to-CSP is out — and because they are CSP-billed, MPO is out too.

### Why MPO does not apply

Microsoft targets a multiparty private offer at the **customer's billing account ID**, and only EA, MCA, indirect EA, and web direct accounts qualify. A CSP customer's subscriptions sit under their provider's billing, so there is no eligible billing account to target, and the customer cannot be the owner or signatory on one in order to accept. Microsoft's own guidance is that CSP-program partners may use MPO "for customers with an EA or MCA" — the restriction follows the customer, not the partner.

### Separate the two blockers

Solving one does not solve the other, and a deal can clear the first and still stall on the second.

| Blocker                        | Question                                                                                                      | Resolution                                                                                                                   |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Billing the premium**        | How does the Archera premium reach the customer?                                                              | The options below                                                                                                            |
| **Transacting the commitment** | Does that CSP permit self-service purchase of reservations and savings plans in the customer's subscriptions? | If yes, business as usual. If no, either that CSP enables it, or someone on their ops team procures what Archera recommends. |

### The options, in the order worth trying

1. **Bring their CSP in.** We extend an ISV-to-CSP private offer to whoever owns the customer's billing. The margin costs that CSP nothing to accept and puts the premium on the invoice the customer already pays. This is the designed path, and in practice it is a partner-recruitment conversation rather than a blocker.
2. **Check for a non-CSP billing account.** Many organisations are hybrid — CSP for some subscriptions, a direct MCA or EA elsewhere. The premium is a SaaS charge and does not have to sit on the same subscription running the workloads. If any eligible billing account exists, a customer private offer or an MPO opens up. One question to the customer, and it occasionally unblocks the deal outright.
3. **Invoice off-marketplace.** Archera bills the customer directly. Commercially simple, but there is no MACC decrement and no marketplace procurement route — some customers will not buy this way.
4. **Run the platform unmonetized.** The customer uses Archera for native commitment management at no cost and we do not sell Guaranteed Commitments. A legitimate deliberate outcome, and better taken knowingly than by default.

{% hint style="info" %}
Tell us who invoices the customer for Azure today before you plan the deal. That single fact determines the structure, and getting it wrong late is expensive.
{% endhint %}

***

## Questions

Not sure which applies? Tell us the customer's billing relationship — who invoices them for Azure today — and we will tell you the structure. <partners@archera.ai> or the shared Slack workspace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/partners/partner-administration/azure-marketplace-offer-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
