Azure Marketplace listing guidelines

  • Article

This article explains the requirements and guidelines for listing new offers and services on Azure Marketplace. All offers must meet the listing requirements described in this article. Use the links on the right to navigate to additional requirements and checklists for specific offer types.

Listing requirements for most offers

No. Listing element Base requirement Optimal requirement
1 Offer title Briefly describes the solution offering. Matches the online promotion of the solution on the partner's website. Contains key search words.
2 Logo The logo displays correctly. The logo displays correctly.
3 Offer description
  • Contains 2-3 paragraphs.
  • Solution offering is easily understood at a glance.
  • Is free of spelling and grammar mistakes.
  • Is comprehensive and captures target audience, type of user, and why it's valuable (value proposition).
  • Is in paragraph narrative form with short sentences that are easy to understand.
  • The target industry is outlined (if relevant).
  • Good style formatting, with each paragraph heading having a single sentence or phrase summarizing the content that follows and using bullet points, when appropriate, to emphasize key benefits. The objective is for the reader to understand the offering at a glance in an easy-to-view format and not have to read long paragraphs.
  • There is spacing between each paragraph. It reads like a car brochure. That is, it is comprehensive and describes the offering simply, without technical jargon.
4 Categories and industries
  • Categories and subcategories must match offer capabilities
  • Do not select categories/subcategories that do not fit with your offer capabilities.
  • Select up to two categories, including a primary and a secondary category (optional).
  • Select up to two subcategories for each primary and/or secondary category. If no subcategory is selected, your offer will still be discoverable on the selected category.
5 Images
  • Image requirements are listed in Partner Center.
  • Text included in the screenshot is legible, and the image is clear.
 The solution offering is easily understood at a glance.
6 Videos
  • No video is required but, if provided, it must play back without any errors.
  • If provided, it may not refer to competitor companies unless it is demonstrating a migration solution.
  • Ideally, the length is 3 min. or more.
  • The solution offer is easily understood through video content.
  • Provides demo of solution capabilities.
7 List status (listing options)
  • Must be labeled as one of the following types:
    • Contact Me
    • Trial/Get Trial Now/Start Trial/Test Drive
    • Buy Now/Get It Now
 Customer can readily understand what the next steps are:
  1. Try the Trial.
  2. Buy Now.
  3. Contact via email or phone number to arrange for Proof of Concept (POC), Assessment, or Briefing.
8 Solution pricing Must have solution pricing tab/details, and pricing must be in the local currency of the partner solution offering. Multiple billing options should be available with tier pricing to give customer options.
9 Learn more Links at the bottom (under the description, not Azure Marketplace links on the left) lead to more information about the solution and are publicly available and displaying correctly. Links to specific items (for example, spec pages on the partner site) and not just the partner home page.
10 Solution support and help Provide at least one of the following:
- Telephone numbers [1]
- Email support [2]		 - All support methods are listed.
- Paid support is offered free during the Trial or Test Drive period.
11 Legal Policies or terms are available via a public URL.

[1] Doesn't apply to Consulting service and Power BI app offers

[2] Doesn't apply to Consulting service offers

Listing requirements for Consulting service offers

No. Listing element Base requirement Optimal requirement
1 Offer title Must clearly list the service type and duration in the format Name: Duration Type (for example, "Offer Engagement: 1-Week Proof-of-Concept").
  • Does not repeat publisher name.
  • The title mirrors the title style already available in the description. Avoid using long titles.
2 Offer description
  • Ensure proper usage of Microsoft product names.
  • Offers marked as Price: Estimated must have a note at either the top or bottom to explain the variability (travel to client, number of servers being migrated, and so on).
  • Each offer type has description requirements, as follows:
    • Briefings need at least four or five bullets, with information about topics to be covered.
    • All workshops need an agenda.
    • All agendas must be broken down by day or by week, depending on the duration of the workshop.
    • Assessment, POC, non-training workshops, and implementation offers need deliverables.
    • Training workshops don't need deliverables, but they need a more detailed agenda with topics that will be covered.
  • Any offer has agenda and deliverables.
  • Offer includes a paragraph with context about the company providing the service in the top section.
  • Offer includes a paragraph about the value of the service itself as a top section.
3 Markdown formatting All offers must use Markdown formatting so that the offer renders properly when it's converted to HTML.
4 Categories and industries Categories are not relevant.
5 List status (Listing option) Automatically listed as Contact Me.
6 Solution support and help Support and help are not required.
7 Privacy policy and terms of use available Policies or terms are not required.
8 Service types Ensure that the service type matches the title.
9 Competencies Must have competency in at least one of the following:
  • Application Development
  • Application Integration
  • Application Lifecycle Management
  • Cloud Platform
  • Data Analytics
  • Data Center
  • Data Platform
  • DevOps
10 Products Must be Azure products.
11 Country/region Ensure that the country/region matches the selected currency.
12 Learn more
  • Links at the bottom (under the description, not Azure Marketplace links on the left) lead to more information about the solution and are publicly available and being displayed correctly.
  • Links must have a "friendly name" and are not displayed as the file name of any downloads.

Next steps