Microsoft Azure Marketplace Participation Policies
Last updated January 2018
These Microsoft Azure Marketplace Participation Policies apply to all publishers and offerings in the Microsoft Azure Marketplace. These policies are in addition to the terms and conditions set forth in the Microsoft Marketplace Publisher Agreement. Publishers must comply at all times with the policies described and/or referenced in this document in order to participate in the Azure Marketplace. If a publisher fails to meet all terms and conditions at any given time, Microsoft may remove the publisher’s offering from the Azure Marketplace. We may update this document from time to time.
SECTION 1 Base Criteria.
- Software and services offered in the Azure Marketplace must meet at least one of the following criteria:
- Run on Microsoft Azure: The primary function of the software or service must run on Microsoft Azure.
- Deployable to Microsoft Azure: Publishers must describe in their offering listing information how the software or service is deployed on Microsoft Azure.
- Integrate with or extend a Microsoft Azure service: Publishers must indicate in their offering listing information which Azure service the software or service integrates with or extends and how the software or service integrates or extends the Azure service.
- Publishers must be located in a sell-from country supported by the Azure Marketplace. The Azure Marketplace currently supports the following sell-from countries:
- Afghanistan, Albania, Algeria, Angola, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, Azerbaijan, Bahrain, Bangladesh, Belarus, Belgium, Benin, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Canada, Central African Republic, Chad, Chile, Colombia, Comoros, Congo (DRC), Congo (Republic of), Costa Rica, Cote D'Ivoire, Croatia, Cyprus, Czech Republic, Denmark, Dominica, Dominican Republic, Ecuador, Egypt, El Salvador, Eritrea, Estonia, Ethiopia, Fiji Islands, Finland, France, Georgia, Germany, Ghana, Greece, Guatemala, Guinea, Haiti, Honduras, Hong Kong SAR, Hungary, Iceland, India, Indonesia, Iraq, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kazakhstan, Kenya, Korea (South), Kuwait, Laos, Latvia, Lebanon, Liberia, Liechtenstein, Lithuania, Luxembourg, Madagascar, Malawi, Malaysia, Mali, Malta, Mauritius, Mexico, Monaco, Mongolia, Montenegro, Morocco, Mozambique, Nepal, The Netherlands, New Zealand, Nicaragua, Niger, Nigeria, Norway, Oman, Pakistan, Panama, Paraguay, Peru, Philippines, Poland, Portugal, Qatar, Romania, Russia, Rwanda, Saudi Arabia, Senegal, Serbia, Sierra Leone, Singapore, Slovakia, Slovenia, Somalia, South Africa, Spain, Sri Lanka, Sweden, Switzerland, Tajikistan, Tanzania, Thailand, Timor-Leste, Togo, Tonga, Trinidad and Tobago, Tunisia, Turkey, Turkmenistan, Uganda, Ukraine, United Arab Emirates, United Kingdom, United States, Uruguay, Uzbekistan, Venezuela, Vietnam, Zambia, Zimbabwe.
- For each offering, publishers must make the offering available in at least one sell-to country supported by the Azure Marketplace. The Azure Marketplace currently supports the following sell-to countries:
- Algeria, Argentina, Australia, Austria, Bahrain, Belarus, Belgium, Brazil, Bulgaria, Canada, Chile, Colombia, Costa Rica, Croatia, Cyprus, Czech Republic, Denmark, Dominican Republic, Ecuador, Egypt, El Salvador, Estonia, Finland, France, Germany, Greece, Guatemala, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, Italy, Japan, Jordan, Kazakhstan, Kenya, Kuwait, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malaysia, Malta, Mexico, Montenegro, Morocco, Netherlands, New Zealand, Nigeria, Norway, Oman, Pakistan, Panama, Paraguay, Peru, Philippines, Poland, Portugal, Puerto Rico, Qatar, Romania, Russia, Saudi Arabia, Serbia, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sri Lanka, Sweden, Switzerland, Taiwan, Thailand, Trinidad and Tobago, Tunisia, Turkey, Ukraine, United Arab Emirates, United Kingdom, United States, Uruguay, Venezuela.
- Publishers must remain in good financial standing.
- Publisher offerings in the Azure Marketplace must be of limited or general availability and must have an established customer base.
- Offerings in the Azure Marketplace cannot use or be dependent on any product or component that is not supported or that is no longer commercially available.
- Publishers must make detailed technical documentation available that describes how to use their offerings on Microsoft Azure and must provide or link to such documentation in their listing information for each offering.
- Publishers must announce the availability of their offering in the Azure Marketplace on their public website and must include hyperlinks to their offer listing page(s) on https://azuremarketplace.microsoft.com/en-us/marketplace/.
- Publishers must classify each offering based on one or more classification taxonomies provided by Microsoft, including the categories described in Section 4 of this document. Microsoft reserves the right to reclassify any offering if it considers a publisher-selected classification to be inaccurate.
- If a publisher’s offering is Microsoft Azure Certified and does not run primarily on Microsoft Azure, the publisher must make a paid version of the offering available within the Marketplace within 90 days of publishing a free or BYOL version of the offering in the Azure Marketplace.
SECTION 2 Publishing Offers.
- Publishers must publish at least one offering in the Azure Marketplace within 60 days of executing the Microsoft Marketplace Publisher Agreement.
- Publishers must adhere to Azure Marketplace technical requirements for onboarding as defined in the Marketplace Publication Guidelines and as may be further identified in the Publishing Portal.
SECTION 3 Offer Listings.
- Publishers must include detailed offer information in their offer listing pages, which must be accurate and kept up to date. Such information must include, as applicable:
- Offering description
- Minimum offer description
- SKU information
- Value proposition
- Recommended offer description
- Detailed SKU information
- Detailed value proposition
- Features: 3-5 factual statements about the offering
- Benefits: 3-5 results produced by offering features
- Minimum offer description
- Pricing model
- The offering must be compatible with pricing models supported by the Azure Marketplace, as described in Section 5 of this document.
- Link to customer support details
- Publishers must provide commercially reasonable customer support for offerings in the Azure Marketplace, either included within user fees associated with the offering, or as a support offering that is purchased separately.
- Offer resources
- Resources include, but are not limited to, demo videos, screenshots, whitepapers, case studies, testimonials, and detailed technical documentation on how to use the publisher’s offering on Microsoft Azure.
- Customer refund policy
- Offering description
- Publishers may not redirect or upsell Azure customers within their offer listing page to software or services other than those available in the Azure Marketplace. This restriction does not apply to support services that publishers sell outside of the Azure Marketplace.
- Publishers may not promote within the Azure Marketplace the availability of their offerings on other cloud platforms.
- Microsoft reserves the right to edit and revise offer listing page details for quality assurance. Microsoft will inform publishers prior to publication of their offering listing pages in the Azure Marketplace if Microsoft makes any changes to any listing page details.
SECTION 4 Offering Classification Definitions.
Virtual Machine Image
Pre-configured virtual machine (VM) image with a fully installed operating system and one or more applications. Virtual Machine Image offerings may include a single VM image or multiple VM images tied together by an ARM Template.
A virtual machine image (“Image”) provides the information necessary to create and deploy virtual machines in the Azure Virtual Machines service. An Image comprises an operating system virtual hard drive and zero or more data disk virtual hard drives. Customers can deploy any number of virtual machines from a single Image.
Virtual Machine Extension
VM agents that can be added to new VMs using a variety of options, including via REST API, the Azure Portal, or Azure PowerShell cmdlets. VM Extensions can also be manually installed on existing VMs, and can be configured for either Windows Server or Linux-based VMs.
A virtual machine extension (“VM Extension”) is mechanism for installing a software application, or suite of software applications, within Azure virtual machines. A VM Extension may include software applications or, once installed within or executed by a virtual machine, may operate to download and install one or more software applications within the virtual machine from an external location. For clarity, any software or other data installed by your VM Extension, even if retrieved from an external location, is considered Offering Contents for purposes of this Agreement. You will be responsible, and must provide support to Customers, for any VM Extension handlers associated with your VM Extension Offerings.
Fully managed services for information workers, business analysts, developers, or IT pros to use in custom application development or system management. The Marketplace supports three types of services:
Application Services provide functionality to enable customers to quickly develop cloud scale applications on Azure.
Application package that can be used to install and deploy open source or proprietary website content or management platforms in the Azure Websites Service. Web Applications must comply with the Microsoft Web Application Gallery Principles.
As used in this Agreement, a “Web Application” is an application package that can be used by Customers to install and deploy open source or proprietary website applications in the Azure Websites Service.
Offerings that are not available to Azure customers directly through the Marketplace, but for which the Marketplace displays a link, icon, and software/service product listing directing customers to the publisher’s web site or provides instructions on how customers obtain and use the offering on Azure. A “Catalog-Only Listing” is an Offering that is not available to Customers directly through the Marketplace but for which the Marketplace displays a link, icon, and/or description directing Customers to your website or providing instructions on how Customers may obtain and use the Offering in Azure. For clarity, any software or data referenced by a Catalog-Only Listing is considered Offering Contents for purposes of this Agreement.
Azure Resource Manager (ARM) template that can reference multiple, distinct offerings, including offerings published by other publishers, to enable Azure customers to deploy one or more offerings in a single, coordinated fashion.
An “Azure Resource Manager (ARM) Template” is a data structure that references one or more Offerings and includes metadata about the Offering(s), including associated Listing Information. ARM Templates are used by the Marketplace Service to display and enable Customers to deploy certain categories of Offerings. Publishers may publish ARM Templates in the Marketplace that reference multiple, distinct Offerings, including Offerings published by other publishers.
If you wish to make an application or service available in the Azure Marketplace that does not fall within any of the above categories, please provide feedback on the Azure Marketplace Forum.
SECTION 5 Pricing Models.
The following table describes the pricing models that are currently supported by the Azure Marketplace. An offering may include different SKUs that utilize different pricing models.
|Pricing Model||Description||Applicable to|
Free SKU. Customers are not charged Azure Marketplace fees for use of the offering. Prices for free SKUs may not be increased to non-zero amounts.
(Try it now)
Bring-Your-Own-License (BYOL) SKU. Customers obtain outside of the Azure Marketplace the right to access or use the offering and are not charged Azure Marketplace fees for use of the offering in the Azure Marketplace.
Customers are charged a fixed monthly fee for a subscription to the offering. Monthly subscriptions begin on the date of customer purchase except as described below, monthly fees are not prorated for mid-month customer cancellations or in the case of unused services. Monthly fees may be prorated if the customer's licensing terms require calendar monthly billing or if the customer upgrades or downgrades its subscription in the middle of the month. Upgrades and downgrades are only supported if the Publisher configures the offering accordingly.
Customers are charged based on the extent of their use of the offering. For Virtual Machine Images, customers are charged an hourly Azure Marketplace fee, as set by publishers, for use of virtual machines deployed from the images. The hourly fee may be uniform or varied across virtual machine sizes. Partial hours are charged by the minute.
For Application Services, publishers are responsible for defining the unit of measurement for billing purposes (e.g., number of transactions, number of emails sent, etc.). Publishers can define multiple meters for the same Application Service plan. Publishers are responsible for tracking individual customers’ usage for each meter defined by the offering and reporting such information to Microsoft on an hourly basis using reporting mechanisms provided by Microsoft. Microsoft will charge customers based on the usage information reported by publishers for the applicable billing period.
Publishers now have the ability to lower their user fees for virtual machine offerings that have already been published. All other types of price alterations for existing offerings are currently not supported in the Marketplace. Until such additional functionality is available in the Marketplace, Publishers who wish to change the user fees associated with an offering should remove the offering from the Marketplace, subject to the requirements of the Microsoft Marketplace Publisher Agreement and this document, and publish a new offering that includes the new user fees.
After publishing a Services Offering on the Marketplace, Publishers must maintain their own data logs regarding the provisioning of their Offering(s) to Customers for a minimum of two (2) previous calendar years. If there are any conflicts in the data between the Publisher’s data logs and Microsoft’s data logs, Microsoft’s data logs will control.
SECTION 6 Offering Suspension and Removal.
- Microsoft reserves the right to suspend or remove an offering from the Azure Marketplace for any reason. Reasons Microsoft may remove an offering include, but are not limited to:
- The offering has not been provisioned by any customers for six or more months;
- The offering has a high cancelation rate for paid SKUs;
- The offering consistently receives negative customer feedback;
- The offering consistently receives a large number of support tickets; or
- The publisher has failed to comply with terms and conditions in the Microsoft Marketplace Publisher Agreement, the Marketplace Publication Guidelines, or this document.
- For various reasons, you may decide to remove your offer from the Marketplace. Offer Removal ensures that new customers may no longer purchase or deploy your offer, but has no impact on existing customers. Offer Termination is the process of terminating the service and/or licensing agreement between you and your existing customers. Guidance and policies related to offer removal and termination are governed by Microsoft Marketplace Publisher Agreement (see Section 7). You may request removal or termination by logging a support ticket.
SECTION 7 Payment Terms.
Publishers will be paid applicable Publisher Net Revenues, as defined in the Microsoft Marketplace Publisher Agreement, within 45 days after each calendar month.
SECTION 8 Microsoft Software Products.
Microsoft permits publishers to include the following Microsoft Software Products in their Image Offerings, subject to the terms and conditions of Exhibit B of the Microsoft Marketplace Publisher Agreement:
- Windows Server®
- SQL Server®
- Microsoft Dynamics NAV®
SECTION 9 Taxes.
- Microsoft Remittance Countries.
- The following countries are Microsoft Remittance Countries, as defined in the Microsoft Marketplace Publisher Agreement: European Union, Canada, India, Ireland, Liechtenstein, Monaco, New Zealand, Norway, Puerto Rico, South Korea, Switzerland, United States. Taiwan and Australia are Microsoft Remittance countries only for Web Direct sales.
- Within Ireland, Microsoft charges Irish VAT to all Irish customers (unless Irish customer provides details of a valid VAT 56B certificate). For business customers within the European Union and Norway (located outside of Ireland), Microsoft applies the zero rate of VAT when provided with a valid VAT number. If a valid VAT number is not provided, then customers are charged VAT at the rate applicable in the customer’s country/jurisdiction.
- Microsoft will charge Swiss VAT to all customers in Switzerland or Liechtenstein.
- ISV Remittance Countries.
- ISV Remittance Countries include all sell-to countries as defined in Section 1 (3) of this Policy that are not Microsoft Remittance Countries. In addition, sales for Taiwan and Australia via the Enterprise channel, are treated as ISV Remittance sales. However, with regards to publishers in Taiwan, Microsoft cannot confirm that any such Taiwanese publishers are collecting and remitting applicable taxes.
- If publishers choose to make offerings available in an ISV Remittance Country, such publishers will have sole responsibility to determine their tax obligation in such ISV Remittance Country, if any, and acknowledge that Microsoft may not currently be able to provide the transaction details required for publishers to provide customers with tax invoices.
SECTION 10 Security Events.
Publishers must report suspected security events, including security incidents and vulnerabilities, relating to their Azure Marketplace software and service offerings to Microsoft at the earliest opportunity. Publishers should log a support ticket using the process outlined here, providing the requested information.