This article describes pricing, billing, invoicing, and payout considerations for transactable offers sold through the commercial marketplace. For information about publishing non-transactable [free or Bring your own license (BYOL)] offers, see Introduction to listing options.
To see the customer's view of purchasing in the commercial marketplace, see Azure Marketplace purchasing. For SaaS offers, see Purchase SaaS apps on Microsoft AppSource.
Either the publisher or Microsoft is responsible for managing software license transactions for offers in the commercial marketplace. The listing option you choose for your offer determines who manages the transaction. For availability and explanations of each publishing option, see Introduction to listing options.
Choosing to sell through Microsoft takes advantage of Microsoft commerce capabilities and provides an end-to-end experience from discovery and evaluation to purchase and implementation. A transactable offer is one in which Microsoft facilitates the exchange of money for a software license on the publisher's behalf. Transact offers are billed against an existing Microsoft subscription or credit card, enabling Microsoft to host cloud marketplace transactions on behalf of the publisher.
You choose the transact option when you create a new offer in Partner Center. This option appears only if transact is available for your offer type.
When using the transact option, Microsoft enables the sale of non-Microsoft software and deployment of some offer types to the customer's Azure subscription. The publisher must consider the billing of infrastructure fees and your own software licensing fees when selecting a pricing model for an offer.
The transact publishing option is currently supported for the following offer types:
Offer type | Billing cadence | Metered billing | Pricing model |
---|---|---|---|
Azure Application (Managed application) | Monthly | Yes | Usage-based and flat rate |
Azure Container | Monthly [1] | No | Usage-based, BYOL |
Azure Virtual Machine | Monthly and upfront [2] | No | Usage-based, BYOL |
Software as a service (SaaS) | One-time upfront monthly, annual [3] [4] | Yes | Flat rate, per user, usage-based. |
Dynamics 365 apps on Dataverse and Power Apps [5] | Monthly and annual | No | Per user |
Power BI visual [6] | Monthly and annual | No | Per user |
(1) Azure Container offers support usage-based billing plans. These plans are billed monthly for hourly use of the usage based on per core, or per every core in cluster.
(2) Azure Virtual Machine offers support usage-based billing plans. These plans are billed monthly for hourly use. The plans are billed based on: free, flat rate, per vCPU, per vCPU size, or per market and vCPU size usage. Virtual Machine plans also support 1-year and 3-year reservation pricing billed either upfront or monthly. See Plan a virtual machine offer.
(3) SaaS plans support monthly, 1-year, 2-year, and 3-year terms that can be billed either monthly or for the entire term upfront. See Plan a SaaS offer for the commercial marketplace.
(4) If you choose to configure a 2-year or 3-year billing term, or a 1-year billing term with a monthly payment option, your offer is published to Azure Marketplace only. If you update an offer that is currently published live on AppSource with a multi-year billing term, the offer is delisted from AppSource and published only to Azure Marketplace.
(5) Dynamics 365 apps on Dataverse and Power Apps offers that you transact through Microsoft are automatically enabled for independent software vendor (ISV) license management. See ISV app license management for Dynamics 365 apps on Dataverse and Power Apps.
(6) Power BI visual offers that you transact through Microsoft are automatically enabled for license management. See ISV app license management for Power BI visual offers.
The Marketplace metering service lets you specify pay-as-you-go (consumption-based) charges in addition to monthly or annual charges included in the contract (entitlement). You can charge usage costs for marketplace metering service dimensions that you specify such as bandwidth, tickets, or emails processed. For more information about metered billing for SaaS offers, see Metered billing for SaaS using the commercial marketplace metering service. For more information about metered billing for Azure Application offers, see Managed application metered billing.
For virtual machines, containers, and Azure applications, Azure infrastructure usage fees are billed to the customer's Azure subscription. Infrastructure usage fees are priced and presented separately from the software provider's licensing fees on the customer's invoice.
For SaaS Apps, the publisher must account for Azure infrastructure usage fees and software licensing fees as a single cost item. It's represented as a flat fee to the customer. The Azure infrastructure usage is managed and billed to the publisher directly. The customer doesn't see actual infrastructure usage fees. Publishers typically opt to bundle Azure infrastructure usage fees into their software license pricing. Software licensing fees aren't metered or based on user consumption.
Depending on the transaction option used, subscription charges are as follows:
Offers that are billed according to consumption after a solution has been used aren't eligible for refunds.
To change the prices associated with an active transactable offer, see Changing prices in active commercial marketplace offers.
Use this flowchart to determine the appropriate transactable offer type and pricing plan to sell your software in the commercial marketplace. This chart assumes that as the publisher, you have a clear understanding of your software delivery and licensing/billing models.
SaaS offers are a good fit if your customers just want to subscribe to your service and use it online. With SaaS, the publisher (you) hosts the software in your cloud infrastructure, managing technical infrastructure, app software, and data management responsibilities.
Virtual machine and Azure Application offers are a good fit if you want customers to deploy, manage, and run your packaged app or service (as a VM Image and/or as other Azure services in the ARM template) in their own Azure cloud infrastructure.
[2] VM offer images can be included in the Azure App offer to improve pricing and deployment flexibility.
[3] This can include your own VM offers.
[4] Customer pays other infrastructure costs because Azure services are deployed on the customer tenant for VM and Azure App offers.
When publishing an offer as a usage-based or subscription transaction, Microsoft provides the technology and services to process software license purchases, returns, and charge-backs. In this scenario, the publisher authorizes Microsoft to act as an agent for these purposes. The publisher allows Microsoft to facilitate the software licensing transaction. The publisher, however, retains the designation as the seller, provider, distributor, and licensor.
Microsoft enables customers to order, license, and use your software, subject to the terms and conditions of both Microsoft's commercial marketplace and your end-user licensing agreement. You must either provide your own end-user licensing agreement or select the Standard Contract when creating the offer.
For transact publishing scenarios, you can make a software license available free for 30 to 120 days, depending on the subscription. Customers are charged for applicable Azure infrastructure usage.
Usage-based
Usage-based pricing has the following cost structure:
Your license cost | $1.00 per hour |
---|---|
Azure usage cost (D1/1-Core) | $0.14 per hour |
Customer is billed by Microsoft | $1.14 per hour |
In this scenario, Microsoft bills $1.14 per hour for use of your published VM image.
Microsoft bills | $1.14 per hour |
---|---|
Microsoft pays you 97% of your license cost | $0.97 per hour |
Microsoft keeps 3% of your license cost | $0.03 per hour |
Microsoft keeps 100% of the Azure usage cost | $0.14 per hour |
Bring Your Own License (BYOL)
BYOL has the following cost structure:
Your license cost | License fee negotiated and billed by you |
---|---|
Azure usage cost (D1/1-Core) | $0.14 per hour |
Customer is billed by Microsoft | $0.14 per hour |
In this scenario, Microsoft bills $0.14 per hour for use of your published VM image.
Microsoft bills | $0.14 per hour |
---|---|
Microsoft keeps the Azure usage cost | $0.14 per hour |
Microsoft keeps 0% of your license cost | $0.00 per hour |
SaaS app subscription
SaaS subscriptions can be priced at a flat rate or per user. If you enable the Sell through Microsoft option for a SaaS offer, you have the following cost structure:
Your license cost | $100.00 per month |
---|---|
Azure usage cost (D1/1-Core) | Billed directly to the publisher, not the customer |
Customer is billed by Microsoft | $100.00 per month (publisher must account for any incurred or pass-through infrastructure costs in the license fee) |
In this scenario, Microsoft bills $100.00 for your software license and pays out $97.00.
Microsoft bills | $100.00 per month |
---|---|
Microsoft pays you 97% of your license cost | $97.00 per month |
Microsoft keeps 3% of your license cost | $3.00 per month |
We charge a 3% standard store service fee when customers purchase your transact offer from the commercial marketplace.
When subscription or Pay-as-You-Go (also called usage-based) pricing models are selected, Microsoft acts as the agent of the publisher and is responsible for all aspects of billing, payment, and collection.
Any software licensing fees collected by Microsoft as an agent are subject to a three percent store service fee unless otherwise specified and are deducted at the time of publisher payout.
Customers typically purchase using the Enterprise Agreement or a credit-card enabled pay-as-you-go agreement. The agreement type determines billing, invoicing, collection, and payout timing.
All reporting and insights for the transact publishing option are available via the Analytics section of Partner Center.
For more information and legal policies, see the Microsoft Publisher Agreement. For help with billing questions, contact commercial marketplace publisher support.
This section covers transact requirements for different offer types.
The ability to transact through Microsoft is available for the following commercial marketplace offer types only. This list provides the requirements for making these offer types transactable in the commercial marketplace.
You can create a private plan for an offer, complete with negotiated, deal-specific pricing, or custom configurations.
Private plans enable you to provide higher or lower pricing to specific customers than the publicly available plan. Private plans can be used to discount or add a premium to an offer. Private plans can be made available to one or more customers by listing their Azure subscription at the plan-level.