| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Marketplace criteria content validation - Azure | Microsoft Docs |
This article describes how to become a publisher on the marketplace. |
Azure, Marketplace, Compute, Storage, Networking, Blockchain, Security |
yijenj |
nunoc |
marketplace |
article |
10/05/2018 |
yijenj |
This document contains requirement guidelines as well as a checklist for reviewers for new offers and services listed to Azure Marketplace.
All offers must meet the All Listing Requirements indicated below. Additional requirements and checklists are provided for specific listing types including: offers with attached trials, SaaS apps, containers, and consulting offers.
| Listing Element | Base Requirements | Optimal Requirements | |
|---|---|---|---|
| 1 | Lead destination | Have a lead destination configured | OCP Catalog has the lead destination CRM info also listed in partner solution tab |
| 2 | Offer title | Descriptive of solution offering. Matches online promotion of solution in partner’s website | Contains key search words |
| 3 | Logo | Logo displays correctly | Logo displays correctly and includes hero image which is the large-format image in the Azure Portal |
| 4 | Offer description | • 2-3 paragraphs • Solution offering is easily understood at a glance • Offer description is free of spelling and grammar mistakes • Offer description is comprehensive and captures: target audience, type of user, why it’s valuable (value prop) • Offer description is in paragraph narrative form with short sentences that is easy to comprehend |
• Target industry is outlined (if relevant) • Good style formatting with each paragraph header having a one-sentence or phrase summarizing content that follows and inclusive of bullet points (when appropriate) to emphasize key benefits. The objective here is for the reader to understand the offering at a glance in an easy to view format and not have to read paragraphs. • There is spacing between each paragraph and reads like a car brochure. Meaning not technical features or code lingo but descriptive of the offering in simple terms and is comprehensive. |
| 5 | Categories & Industries | • Categories match solution offering capabilities • Do not extend to categories that solution does not fit • Optimal industry, or all industries selected (if not optimal industries) |
• Max. 3 categories • Max. 3 industries |
| 6 | Images | • No image required, but if provided must display and a high-resolution image. • Image requirements are listed in CPP and also here • Text included in the screenshot is legible with clear image |
Solution offering is easily understood at a glance |
| 7 | Videos | • No videos required, but if provided must play back without any errors. • If provided, may not refer to competitor companies UNLESS demonstrating a migration solution |
• Ideally 3 mins or more • Solution offering easily understood through video content • Demo of solution capabilities |
| 8 | List Status (Call to action) | Must be labeled one of the following type:
|
Customer can readily understand what next steps available are:
|
| 9 | Solution Pricing | Must have solution pricing tab/details and in the local currency of the partner solution offering | Multiple billing options available with tier-pricing for customer to have options |
| 10 | Learn More | Links at the bottom (under the description, not the marketplace links on the left) leads to more information about the solution and are publicly available and displaying correctly | Links to specific items (e.g. spec pages on partner site) and not just partner homepage site |
| 11 | Solution Support & Help | Link to at least one of the following: o Telephone numbers o Email support o Chat agents o Community forums |
• All support methods listed: telephone & email support. • Paid support offered free during trial or test drive period |
| 12 | Legal | Policies or terms available via a public URL |
| Listing Element | Base Requirements | Optimal Requirements | |
|---|---|---|---|
| List Status | Link must lead to customer-led trial experience | Other CTAs (e.g. buy now) also available |
| Listing Element | Base Requirements | Optimal Requirements | |
|---|---|---|---|
| 1 | Offer title | • Must consist only of lowercase, alphanumeric characters, dashes, or underscores. Cannot be modified once published. • Descriptive of solution offering. • Matches online promotion of solution in partner’s website. |
Contains key search words |
| 2 | Technical Info: Configuration | • For SaaS app, choose whether you just want to list your app or if you want to enable customers to purchase your app through Azure. • Select appropriate text that you want on your offer's acquisition button: Free, Free Trial, or Contact me • Only select (pop-up box)- one of these applicable products if your app utilizes the technology: Cortana Intelligence, Power BI Solution Templates, Power Apps |
|
| 3 | Test Drive | Select: Yes or No | Customer can readily understand what next steps available are: 1. Try the Trial 2. Buy Now 3. Contact via e-mail or phone number to arrange for PoC, Assessment, or Briefing. |
| 4 | Storefront details: Offer Summary | This will appear on your app's search page with a maximum of 100 characters | |
| 5 | Storefront details: Industries | Industries (Max 2): Select the industries that your app is best aligned and applicable to. | |
| 6 | Offer Description | • Simple HTML is allowed, including p, em, ul, li, ol and header tags. Maximum of 3000 characters. • 2-3 paragraphs • Solution offering is easily understood at a glance • Description is comprehensive and captures: target audience*, type of user, why it’s valuable (value prop) • Offer description is in paragraph narrative form with short sentences that is easy to comprehend. |
• Target industry is outlined (if relevant) • Good style formatting with each paragraph header having a one-sentence or phrase summarizing content that follows and inclusive of bullet points (when appropriate) to emphasize key benefits. The objective here is for the reader to understand the offering at a glance in an easy to view format and not have to read paragraphs. • There is spacing between each paragraph and reads like a car brochure. Meaning not technical features or code lingo but descriptive of the offering in simple terms and is comprehensive. |
| 7 | Marketing Artifacts | Logos display correctly | • Logo includes “hero image,” which is the large-format image in the Azure Portal • Logos: Small (48x48) & Large (216x216) are requirements • Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish • Screenshot (Max 5): CPP requires a .png image with resolution 1280 x 720. |
| 8 | Categories & Industries | • Categories match solution offering capabilities • At least 1 item(s) should be chosen from pop-up box • Do not extend to categories that solution does not fit • Optimal industry, or all industries selected (if not optimal industries • Do not extend to categories that solution does not fit • Optimal industry, or all industries selected (if not optimal industries) |
Max. 3 categories selected if applicable. |
| 9 | Lead Management | Select the system where your leads will be stored. Learn how to connect your CRM system here | |
| 10 | Contacts: Solution Support & Help | • Engineering contact name: Enter the name of the engineering contact for your app. This contact will receive technical communications from Microsoft. • Engineering contact email: Enter the email address of the engineering contact for your app. • Engineering contacts Phone: Enter the phone number of the engineering contact. ISO phone number notations are supported; for details, see https://en.wikipedia.org/wiki/E.123. • Support contact Name: Enter the name of the support contact for your app. This contact will receive support-related communications from Microsoft. • Support contact email: Enter the email address of the support contact for your app. • Support contact phone: Enter the phone number of the support contact. ISO phone number notations are supported; for details, see https://en.wikipedia.org/wiki/E.123. • Support URL: Enter the URL to your support page. |
• All support methods listed: telephone & email support. • Paid support offered free during trial or test drive period |
| 11 | Legal | • Privacy policy URL: Enter the URL to your app's privacy policy in the Privacy policy URL field in CPP. • Terms of use: Enter the terms of use of your app. Customers are required to accept these terms before they can try your app. |
Policies or terms available via a public URL site |
| Listing Element | Base Requirements | Optimal Requirements | |
|---|---|---|---|
| 1 | Offer Settings | • Offer ID: Max 50 Character • Publisher ID: Select from drop-down • Name: Max 50 characters |
Mirrors the title style already available in the description- do not want long titles. |
| 2 | SKUs | Partner clicks on new SKUs | Mirrors the title style already available in the description- do not want long titles. |
| 3 | Marketplace Artifacts | Logos display correctly | • Logo includes “hero image,” which is the large-format image in the Azure Portal • Logos: Small (48x48) & Large (216x216) are requirements • Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish • Screenshot (Max 5): CPP requires a .png image with resolution 1280 x 720. |
| 4 | Lead Management | • Lead Management: Select the system where your leads will be stored. • Learn how to connect your CRM system here |
| Listing Element | Base Requirements | Optimal Requirements | |
|---|---|---|---|
| 1 | Offer Title | • Must clearly list service type and duration in the following format: NAME : DURATION TYPE. (i.e., “Offer Engagement: 1-Week Proof-of-Concept”) |
• Does not repeat publisher name • Mirrors the title style already available in the description- do not want long titles. |
| 2 | Offer Description | • Ensure proper usage of Microsoft product names • Offers marked as Price: Estimated must have a note either at the top or bottom of the offer to explain the variability (travel to client, number of servers being migrated, etc.) • Each offer type has description requirements as follows: o Briefings need at least 4 to 5 bullets with information on topics covered in briefing o All workshops need agenda o All agendas must be broken down by day or by week, depending on the duration of the workshop o Assessment, POC, non-training workshops, Implementation offers need deliverables o 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 on the company providing the service in the top section • Offer includes a paragraph on 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 converted to HTML | |
| 4 | Categories & Industries | Categories not relevant | |
| 5 | List Status (CTA) | Automatically listed as Contact Me | |
| 6 | Solution Support & Help | Support & Help not required | |
| 7 | Privacy Policy & Terms of Use available | Policies or terms not required | |
| 8 | Service Types | Ensure Service Type matches title | |
| 9 | Competencies | • Must be 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 | |
| 11 | Country/Region | Ensure country and region matches chosen currency | |
| 12 | Learn More | • Links at the bottom (under the description, not the marketplace links on the left) leads to more information about the solution and are publicly available and displaying correctly. • Links must have a “friendly name” and not be appearing as the file name of any downloads |
- Learn about different offer types in the marketplace
SaaS Apps
Containers
Consulting services - Determine the listing type for your solution