Commercial marketplace certification policies

Document version: 1.03

Document date: September 20, 2019

Note

For a summary of recent changes to this agreement, see Change history.

Table of contents

100 General

700 Managed Services

800 Consulting Services

1000 Software as a Service (SaaS)

1100 Office 365

1120 Office add-ins

1140 Teams

1160 SharePoint

1180 Power BI visuals

1200 Power BI visuals additional certification

1220 Excel custom functions

1400 Dynamics 365 Business Central

1420 Dynamics 365 CE

1440 Dynamics 365 Finance Ops

3000 Co-sell solutions

100 General

Your offer listing on the Marketplace must accurately and clearly reflect the source, functionality, and features of your offer. Your listing should let customers quickly and easily understand the value proposition, usage scenario, and benefits of your offer, including provisions for acquisition and support.

100.1 Value proposition and offer requirements

To let customers quickly identify offers of interest, your listing must clearly, concisely and accurately convey the type of offer, the value proposition for your offer, and requirements for its adoption. The listing elements related to this requirement include:

  • An accurate and descriptive title
  • A concise, well written summary of the offer and its intended use
  • A description that identifies the audience for the offer, briefly and clearly explains the unique and distinct value of the offer, identifies supported Microsoft products and other supported software, and includes any prerequisites or requirements for its use.

You must clearly describe any limitations, conditions or exceptions to the functionality, features, and deliverables described in the listing and related materials before the customer acquires your offer. The capabilities you declare must relate to the core functions and description of your offer.

Commercial marketplace content (including Storefront text, documents, screenshots, Terms of Use, and Privacy Policy) is not required to be in English as long as the description begins with the phrase, “This application is available only in <non-English language>.” It is also acceptable to provide a Useful Link URL to offer content in a language other than the one used in the marketplace content.

If your offer supports multiple languages, all offer and marketplace listing content should be localized for each supported language. Offers listed in multiple languages must be easily identified and understood.

Author the summary and description elements of your listing by using the Markdown markup language. For information about using Markdown see How to use Markdown for writing Docs. Attached documents must be in .pdf format.

100.2 Offer targets

To help customers identify appropriate publishers and offers, your listing must accurately identify your expertise and the areas your offer supports. Listing features that do this include:

  • Categories
  • Industries
  • Competencies

You must provide accurate current information needed to validate your competencies and qualifications when you submit your offer.

100.3 Graphic elements

Graphic elements help customers identify the source and understand the features of your offer. When used, graphic elements must be accurate, easy to understand, and related to your offer. Graphic elements include:

  • Logo
  • Images, including screenshots
  • Videos

100.4 Acquisition, pricing, and terms

Customers need to understand how to evaluate and acquire your offer. Your listing must accurately describe:

  • How you are providing your offer (for example, as a limited time trial or as a purchase)
  • Pricing, including currencies used in your market
  • Variable pricing structures

All purchase transactions associated with your offer must begin by using a starting point in the commercial marketplace listing, such as the Contact Me or Get It Now buttons.

Microsoft does not currently provide native application programming interfaces (APIs) to support in-offer purchases. You may use any third-party payment system for those purchases.

In addition, all aspects of your offer, including but not limited to acquisition, pricing, and terms, must comply with all applicable laws and regulations.

100.5 Offer information and support contacts

Customers want to know how to find out more about your offer and how they’ll get support for evaluating and using it. Links to information may include:

  • “Learn More” links to additional offer information
  • Support and Help links with appropriate information
  • Transaction information
  • Terms of use
  • Privacy policy

Links must be functional, and accurate and must not jeopardize or compromise user security. For example, a link must not spontaneously download a file.

100.6 Personal information

Customers and partners care about the security of their personal information. Personal Information includes all information or data that identifies or could be used to identify a person, or that is associated with such information or data. Your listing must not include third-party personal information without authorization. Your listing must include a link to your privacy policy for the listed offer.

100.7 Accurate source

Customers want to know who they are dealing with and expect clarity about the offers and relationships they rely on. All content in your offer and associated metadata must be either originally created by the offer provider, appropriately licensed from the third-party rights holder, used as permitted by the rights holder, or used as otherwise permitted by law.

When referring to Microsoft trademarks and the names of Microsoft software, products, and services, follow Microsoft Trademark and Brand Guidelines.

100.8 Significant value

Customers expect offers in the marketplace to be worth their time. Offers must provide enough value to justify the investment it takes to learn and use them. Your offer should provide significant benefits such as enhanced efficiency, innovative features, or strategic advantages. Simple utilities or offers with limited scope are not a good fit for the marketplace.

100.9 Significant need

Customers also want clear and meaningful choices. Your offer must serve a significant unmet need. Offers that duplicate offerings in well-served areas are not a good fit for the marketplace.

100.10 Inappropriate content

Customers expect offers to be free of inappropriate, harmful, or offensive content. Your offer must not contain or provide access to such content including, but not limited to content that:

  • Facilitates or glamorizes harmful activities in the real world.
  • Might pose a risk of harm to the safety, health, or comfort of any person or to property.
  • Is defamatory, libelous, slanderous, or threatening.
  • Is potentially sensitive or offensive or that advocates discrimination, hatred, or violence based on membership in a particular racial, ethnic, national, linguistic, religious, or other social group, or based on a person's gender, age, or sexual orientation.
  • Facilitates or glamorizes excessive or irresponsible use of alcohol or tobacco products, drugs, or weapons.
  • Contains sexually explicit or pornographic content.
  • Encourages, facilitates, or glamorizes illegal activity in the real world, including piracy of copyrighted content.
  • Includes excessive or gratuitous profanity or obscenity.
  • Is offensive in any country/region to which your offer is targeted. Content may be considered offensive in certain countries/regions because of local laws or cultural norms.

100.11 Security

Customers want to be confident that offers are safe and secure. Your offer must not jeopardize or compromise user security, the security of the Azure service, or related services or systems.

If your offer collects credit card information, or uses a third-party payment processor that collects credit card information, the payment processing must meet the current PCI Data Security Standard (PCI DSS).

Your offer must not install or launch other executable code on the user’s environment.

100.12 Functionality

Customers expect offers to deliver what they promise. Your offer must provide the functionality, features, and deliverables described in your listing and related materials.

If your offer has trial and paid versions, trial functionality must reasonably resemble the paid version.

Offer user interfaces should not look unfinished. All UI should be intuitive and obvious in purpose, without requiring users to read support documentation for basic tasks.

Your offer should be reasonably responsive. Long wait or processing times should be accompanied by some form of warning or loading indicator.

100.13 Business requirements

Offers you submit to the marketplace must meet applicable business requirements including:

  • Specific qualification or approval by Microsoft as needed.
  • Appropriately targeting customer segments and/or the Azure ecosystem.
  • Appropriate configuration including Storefront, offer type, customer authentication, and billing.

100.14 Testability

Your offer submission must include any necessary instructions and resources for successful verification and testing of your offer.

700 Managed Services

The policies listed in this section apply only to Managed Services offers.

700.1 Value proposition and offer requirements

The term “managed service” or “managed services” must be included somewhere in the offer description.

Managed services offers must have the primary purpose of providing services that manage customers’ use of Azure. Offerings, with the primary purpose of selling licenses or subscriptions to software or a platform, must instead be listed as an application.

700.2 Offer information and support contacts

The Lead Destination must not be set to “None”.

700.3 Graphic elements

No text other than official logo marks may be used in logo images.

Logo backgrounds should not be black, white, or gradients. If a transparent background is used for the required logos, logo elements should not be black, white, or blue. Hero logos may not use transparent backgrounds.

700.4 Business requirements

You must have a Silver or Gold Cloud Platform competency level to publish a Managed Service offer.

You should review the managed services publication guidelines before submission.

700.5 Plan details

Plan titles, summaries, and descriptions must be descriptive of the plan.

The billing model for plans must be "Bring your own license".

700.6 Plan manifest details

Manifest version numbers must be in the n.n.n format (for example, 1.2.5).

800 Consulting Services

The policies listed in this section apply only to Consulting Services offers.

800.1 Title

Your Title must follow the format “Offer Name: Duration Service type.” (For example, “ProtectX - Database Security and Compliance: 2-week Implementation”).

Your offer title must not include your company name in the offer Title unless it is also a product name. (For example, “CompanyX 3-Week Assessment”).

800.2 Summary and description

The Summary and Description must provide enough detail for customers to clearly understand your offer, including:

  • Service deliverables and outcomes.
  • Daily or weekly agendas for workshops longer than one day.
  • Detailed itemization of briefing and workshop topics.

800.3 Value proposition

For consulting services offered by Microsoft Managed Partners, clearly describe the Azure-related value of your services, or state that the offer provides a managed service for an Azure environment.

Consulting services offers must have the primary purpose of providing services that help customers get started with or extend their use of Azure. Offerings with the primary purpose of selling licenses or subscriptions to software or a platform must be listed as an application instead.

800.4 Competencies and types

Your offer should list any fully earned competencies and must list at least one of the following competencies:

  • Application Development
  • Application Integration
  • Application Lifecycle Management
  • Cloud Platform
  • Data Analytics
  • Data Center
  • Data Platform
  • DevOps

Your offer must specify a type. This type must be appropriately specified when mentioned in the title, summary, and description.

800.5 Supporting documents

Your listing may include supporting documents with further information for your offer. Documents may feature Microsoft competing products only in the context of migration to Microsoft products.

1000 Software as a Service (SaaS)

The policies listed in this section apply only to SaaS offers.

1000.1 Value proposition and offer requirements

Your offer must be a commercially available, business-focused offer that targets the Azure ecosystem. If we are unable to determine that your offer meets these criteria, we may request that you reevaluate your offer and provide substantiating information before resubmitting.

1000.2 Offer targets

Offer categories may only include Internet of things (IoT), if the offer supports Azure IoT Services such as IoT Hub or Device Provisioning Service (DPS), and the partner has been approved by the IoT team.

1000.3 Acquisition, pricing, and terms

Your offer must use an organizational or Microsoft Account (MSA) AAD Single Sign On (SSO) experience for users to connect to the offer (this includes Free, Free Trial, or transactional Call to Action options). Integration with AAD should not require that an admin grant permission to an app, unless the description discloses that admin-level access is required.

If your offer has a Sell Through Microsoft Call to Action, you must validate the end-to-end experience, including customer purchase and API interactions. For more information, see https://docs.microsoft.com/azure/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2.

1100 Office 365

The policies listed in this section apply only to Office 365 offers.

1100.1 General content

Your app or add-in title may not include “app”, “plug-in”, or derivatives.

Your offer listing must only describe your app or add-in, and not include advertising for other offers.

Your offer description must disclose any app or add-in features or content that require an extra charge, whether through in-app or add-in purchases or through other means. Your description must also disclose any dependencies on additional services or accounts.

1100.2 Displaying ads

Apps or add-ins can contain ads.

  • The primary purpose of the app or add-in must be more than displaying advertisements.
  • Ads must comply with our content policies and should match our ad design guidelines.
  • Ads should not interfere with app or add-in functionality.

1100.3 Selling additional features

Apps or add-ins running on iOS must not offer any additional features or content for sale.

1100.4 Predictable behavior

Your app or add-in must not make unexpected changes to a user’s document.

Your app or add-in must not launch functionality outside of the app or add-in experience without the explicit permission of the user.

Your app or add-in should not consume an unreasonable amount of memory that negatively impacts the performance of an average user’s environment.

Your app or add-in must be fully functional with the supported operating systems, browsers, and devices for Office 2013, Office 2016, SharePoint 2013, and Office 365.

  • All features must work on a touch-only device without a physical keyboard or mouse.
  • Your app or add-in must not utilize deprecated functionality.
  • Your add-in may not alter or promote the alteration of Office or SharePoint except via the Office and SharePoint Add-ins model.

Your app experience must not prompt a user to disclose the credentials of a Microsoft identity (for example, Office 365 or Microsoft Azure Organizational Account, Microsoft Account, or Windows Domain Account) except through Microsoft approved OAuth flow, where your app is authorized to act on behalf of the user.

1100.5 Customer control

Your app or add-in must obtain consent to publish personal information.

Your app or add-in must not obtain, store, pass, or transmit customer information or content without notifying the user.

Your app or add-in must be secured with a valid and trusted SSL certificate (HTTPS).

Your app or add-in may not open pop-up windows unless they are triggered by explicit user action. Pop-up windows must not be blocked by the browser’s pop-up blocker when the blocker is set to the default value.

Your app or add-in may not request unreasonably high permissions or full-control permission.

Your app or add-in must have a correctly sized and formatted icon specified in the package or manifest.

Add-ins that depend on external accounts or services must provide a clear and simple sign in/sign out and sign-up experience.

Apps or add-ins that target larger organizations or enterprises:

  • Do not require a sign-in experience for external accounts or services if sign-ups are managed by the enterprise outside of the app or add-in and not by the individual user.
  • Do not require a seamless first run experience and value proposition but must include an email contact or link in the UI so users can learn more about your services.

1100.6 Global audience

You must provide details on the offer submission form if your app or add-in calls, supports, contains, or uses cryptography.

1100.7 Easy identification

You must specify language support for your app or add-in within the package manifest. The primary language selected when you submit your offer must be one of the specified supported languages. The app or add-in experience must be reasonably similar in each supported language.

The title may not include your brand or service unless your offer targets a larger organization or enterprise.

  • Microsoft Teams apps may not include the brand or service in the title.

Your app or add-in must not be a duplicate of an app or add-in you have already submitted.

Multiple variants of an app or add-in (for example, with different functionalities at different price points) must be submitted separately with separate product IDs. The binary may remain the same across multiple listings. We recommend that all listing descriptions include a notification of the multiple variants, so users are aware of different cost/functionality tiers.

1100.8 Preserving functionality

If you update your app or add-in’s pricing or licensing terms, you must continue to offer the original functionality to the existing user base at the original pricing. New pricing and/or licensing terms may only apply to new users.

  • If you update your pricing from free to paid, existing users must receive the same level of functionality as before the update.
  • If you update site license pricing from free to paid or not supported, existing users must continue to be supported for free.
  • Apps or add-ins may convert from free to subscription pricing as long as existing users receive the same level of functionality as before the update. Converting from paid to subscription pricing is not currently supported.

1120 Office add-ins

The policies listed in this section apply only to Office add-in offers.

1120.1 Easy identification

All Office add-ins must use the latest Microsoft-hosted Office.js file.

All Office add-ins must use the latest manifest schema.

You must specify a valid Support URL in the SupportURL element of your add-in manifest.

1120.2 Acquisition, pricing, and terms

Office add-ins also available on iOS, Android, or for Teams:

  • Must not include any in-app purchases, trial offers, UI that aims to upsell to paid versions, or links to any online stores where users can purchase or acquire other content, apps, or add-ins.
    • The iOS or Android version of the add-in must not show any UI or language or link to any other apps, add-ins, or website that ask the user to pay. If the add-in requires an account, accounts may only be created if there is no charge; the use of the term “free” or “free account” is not allowed. You may determine whether the account is active indefinitely or for a limited time, but if the account expires, no UI, text, or links indicating the need to pay may be shown.
  • The associated Privacy Policy and Terms of Use pages must also be free of any commerce UI or Store links.
  • Must comply with the Outlook add-in design guidelines.

For Office add-ins also available on iOS:

  • You must accept Apple’s Terms and Conditions by selecting the appropriate checkbox on the Seller Dashboard submission form.
  • Your add-in must be compliant with all relevant Apple App Store policies.
  • You must provide a valid Apple ID.

PowerPoint add-ins which use restricted permissions must clearly display links to their Privacy Policy and Terms of Use information on the first screen of the add-in. If your add-in does not collect or transmit user information, you must link to a statement stating this fact.

1120.3 Functionality

Add-ins must follow design guidelines without impeding the customer experience within the host application.

Add-ins must be compatible with all versions of Internet Explorer 11 and later, and the latest versions of Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple Safari (macOS).

Add-ins must work in all Office applications specified in the Hosts element in the add-in manifest.

Add-ins must work across all platforms that support methods defined in the Requirements element in the add-in manifest, with the following platform-specific requirements:

  • Add-ins must support Office Online applications compatible with the APIs listed in the Requirements element.
  • Add-ins that support iOS must be fully functional on the latest iPad device using the latest version of iOS.
  • Outlook add-ins must not include the CustomPane extension point in the VersionOverrides node. Outlook add-ins that support mobile must allow users to log on separately for each email account added to the Outlook app. Add-in commands must be supported if your add-in is shown on every message or appointment, whether in read or compose mode. If your add-in manifest includes the SupportPinning element for read mode of a message and/or appointment, the pinned content of the add-in must not be static and must clearly display data related to the message and/or appointment that is open or selected in the mailbox.
  • Add-ins that use the taskpane manifest must support add-in commands.

Content add-ins for PowerPoint may not activate their content (e.g., play audio or video) until after the JavaScript API for Office Office.initialize event has been called. This ensures that content display will correctly synchronize with presentations.

1140 Teams

The policies listed in this section apply only to Teams offers.

1140.1 Value proposition and offer requirements

Teams apps must focus on the Teams experience and should not include names, icons, or imagery of other similar chat-based collaborative platforms or services unless the apps provide specific interoperability.

1140.2 Offer information and support contacts

You must submit a Terms of Service link.

1140.3 Security

Bots may not transmit financial instrument details through the user to bot interface. Bots may only transit links to secure payment services to users if this is disclosed in the app’s Terms of Use, Privacy Policy, and any profile page or website for the app before a user agrees to use the bot.

Bots and Compose Extensions:

  • Must follow privacy notice requirements as communicated in the Developer Code of Conduct for the Microsoft Bot Framework.
  • Must operate in accordance with the requirements set forth in the Microsoft Bot Framework Online Services Agreement and Developer Code of Conduct for the Microsoft Bot Framework.

Domains outside of your organization’s control (including wildcards) and tunneling services cannot be included in the valid domains of your manifest.

1140.4 Functionality

App packages must be correctly formatted and conform to the latest manifest schema.

Bot manifest information must be consistent with the bot’s Bot Framework metadata (bot name, logo, privacy link, and terms of service link).

Apps may not launch functionality outside of the Microsoft Teams app experience without the explicit permission of the user.

Apps must be fully functional on the following operating systems and browsers:

  • Microsoft Windows 7 and later.
  • macOS 10.10 and later.
  • Microsoft Edge 12 and later.
  • Mozilla Firefox 47.0 and later.
  • Google Chrome 51.0 and later.
  • iOS 9.0 and later.
  • Android 4.4 and later.

Bot experiences must be fully functional on the following mobile systems:

  • iOS 9.0 and later.
  • Android 4.4 and later.
  • Windows Phone 10.0.10586 and later.

Response times must be reasonable.

  • For tabs: Responses that take more than three seconds must display a loading message or warning.
  • For bots: Responses to user commands that take more than two seconds must display a typing indicator.
  • For compose extensions: Responses to user commands must occur within five seconds.

Teams apps must follow design guidelines without impeding the customer experience within the host application.

  • Tab experiences must provide value beyond hosting an existing website.
  • Content in a channel tab must be contextually the same for all members of the channel and not scoped for individual use.
  • Content in a tab should not have excessive chrome or layered navigation.
  • Configurable tabs should not allow users to navigate outside the core experience within the same tab. Tab configuration must happen in the configuration screen, which must clearly explain the value of the experience and how to configure.
  • Bots must be responsive and fail gracefully.

Teams apps that depend on authentication to an external service to allow content sharing in channels, must clearly state in their help documentation or similar location how a user can disconnect or unshare any shared content, if the same feature is supported on the external service. The ability to unshare the content does not have to be present in the Teams app, but the process should be clearly documented, and the documentation should be accessible from within the app.

1160 SharePoint

The policies listed in this section apply only to SharePoint offers.

1160.1 Security

Add-ins must not have any unauthenticated pages or APIs, except for the error page.

  • An unauthenticated error page should not link to other pages or other protected resources of the add-in.

Add-ins must prompt the administrator to explain that the add-in must install a full-control app.

  • The administrator must be able to install this full-control app without interacting with the add-in provider (for example, via email or web forms).
  • The full-control app must comply with all Marketplace policies.
  • If the full-control app meets all validation policies, the add-in can function only to install the full-control app.

1160.2 Functionality

SharePoint add-ins must be fully functional with Windows 7, Windows 10, all versions of Internet Explorer 11 and later, and the latest versions of Microsoft Edge, Google Chrome, and Mozilla Firefox.

Add-ins must not have remote debugging settings enabled. The manifest for your add-in must not include the DebugInfo element.

1180 Power BI visuals

The policies listed in this section apply only to Power BI offers.

1180.1 Acquisition, pricing, and terms

Power BI visuals must be free but can offer additional purchases.

  • If your Power BI visual offers additional purchases, it must comply with the In-App Purchase (IAP) guidelines.

1180.2 Functionality

Your visual must support Power BI Desktop, Power BI Online, Power BI mobile apps, and Power BI Windows universal apps. It must be compatible with Windows 10 and the latest versions of Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple Safari (macOS).

Your visual must support the core functions of Power BI for that visual type, including but not limited to pinning to dashboard, filtering focus mode, and formatting various data types.

Power BI visuals must be accompanied by a sample file in .pbix format included in the same location as the pbviz file. For the best user experience, consider adding Hits and Tips for using the visual to the sample file.

1200 Power BI visuals additional certification

The policies listed in this section apply only to Power BI visuals offers.

1200.1 Source code

1200.1.1 Code repository

Your visual source code must conform to the visual code repository requirements.

The code repository for your visual should be available and correctly formatted.

1200.1.2 Code quality

Your source code should be readable, maintainable, expose no functionality errors, and correspond to the provided visual’s package.

1200.1.3 Code security

Your source code should comply with all security and privacy policies. Source code must be safe and not pass or transmit customer data externally.

1200.1.4 Code functionality

Running visual development related commands on top of your visual source code should not return any errors.

Visual consumption should not expose any errors or failures and must ensure the functionality of any previous version is preserved.

1220 Excel custom functions

The policies listed in this section apply only to Excel offers.

1220.1 Offer information and support contacts

Your custom functions metadata must have the helpUrl property set.

1220.2 Security

To help to ensure the security of your app and users, your custom functions HTML, Javascript, and JSON metadata files must be hosted on the same domain.

1220.3 Functionality

Add-ins that contain custom functions must support add-in commands. This is to ensure that users can easily discover your add-in.

Your add-in must work across all platforms that support custom functions. Your add-in must also define the requirement set <Set Name="CustomFunctionsRuntime" MinVersion="1.1"/> in the Requirements element.

After an add-in is approved using the EquivalentAddins tag in the manifest, all future updates to the add-in must include this tag. This tag ensures that your custom functions save in XLL-compatible mode.

1400 Dynamics 365 Business Central

The policies listed in this section apply only to Dynamics 365 Business Central offers.

1400.1 Value proposition and offer requirements

For more information on any of the following marketing requirements, please see the marketing validation checklist.

1400.1.1 Language

Offer listings and all linked information, including any landing pages, graphics, documentation, and support options may be presented in languages other than English. If the listing is presented in a language other than English, a .pdf document with the offer name, summary, description, and support contact details translated into English must be included.

For more information, see the language and branding guidelines.

1400.1.2 Branding

Microsoft branding must be consistent throughout your communications:

  • “Microsoft Dynamics 365 Business Central” for first mention and all prominent locations (title, headings, etc.)
  • “Dynamics 365 Business Central” on second mention.
  • “Business Central” on subsequent mentions.

Microsoft trademarked imagery (including the Microsoft, Dynamics, and Business Central logos) may not be used.

For more information, see the language and branding guidelines.

1400.1.3 Name

Two naming structures are allowed for offer names:

  • (Your offer name) for Microsoft Dynamics 365 Business Central.
    Example: Sales & Inventory Forecast for Microsoft Dynamics 365 Business Central.
  • (Your offer name)
    Example: Sales & Inventory Forecast.

For more information, see the offer name guidelines.

1400.1.4 Summary

Offer summaries must summarize the value proposition of your offer in one short and concise sentence.

For more information, see the offer summary guidelines.

1400.1.5 Description

Offer descriptions may be a maximum of 3,000 characters and must use only simple HTML tags (h2, h3, p, em, strong, ul, ol, and li).

For more information, see the offer description guidelines.

Offer descriptions must clearly state which edition(s) (Essentials, Premium, or both) and countries are supported by your offer. Please use the following template in your description:

<h2>Supported Editions</h2>
<p>This app supports the Essentials and Premium Editions of Dynamics 365 Business Central</p>
<h2>Supported Countries</h2>
<p>Canada, Mexico, and United States</p>

For more information, see the supported editions and supported countries guidelines.

1400.1.6 Keywords

If keywords are used, a maximum of three keywords may be provided.

For more information, see the supported products, keywords, and hide key guidelines.

1400.2 Graphic elements

For more information on any of the following marketing requirements, please see the marketing validation checklist.

1400.2.1 Logos

Any text included in the logos must be legible.

For more information, see the offer logo guidelines.

1400.2.2 Screenshots

Screenshots of Business Central must show the latest web client user interface.

For more information, see the screenshots guidelines.

1400.2.3 Videos

Videos including Business Central must show the latest web client interface.

For more information, see the videos guidelines.

1400.3 Acquisition, pricing, and terms

Add-on apps may be either Free or Trial. Connect and Localization apps must be listed as Contact Me.

For more information, see the industries, categories, app type guidelines.

Supported countries must be selected on submission.

For more information, see the supported countries, languages, app Version, and app release date guidelines.

1400.4 Offer information and support contacts

The offer Help Link and Support Link should not be identical, unless a single page covers all Help Link and Support Link requirements below.

  • The Help Link should be a landing page on your website that provides help resources such as documentation, FAQs, step-by-step guides, webinars, etc.
  • The Support Link should be a distinct support page on your website, that includes contact options and documentation including defined service level agreements (SLAs). These should include at least two of the following options: email, phone number, live chat (if possible), and address.

For more information, see the help URL and support URL guidelines.

The offer must include Privacy Policy and Terms of Service links.

  • The Privacy Policy must include DPO contact details for customer enquiries regarding data usage.
  • The Terms of Service may be hosted on AppSource. If hosted on AppSource, they must be formatted in HTML.

For more information, see the [privacy policy and terms of use] guidelines.

Lead Management must be defined for all offers.

The App Version field must be numeric and formatted as x.x.x.x. The version number must increment with every update and match the app.json manifest.

For more information see the supported countries, languages, app Version, and app release date guidelines.

1400.5 Technical requirements

Offers must meet all of the requirements in the technical validation checklist.

1420 Dynamics 365 CE

The policies listed in this section apply only to Dynamics 365 CE offers.

1420.1 Value proposition and offer requirements

Any feature changes between updates must be reflected in the marketing materials submitted to the Marketplace.

1420.2 Acquisition, pricing, and terms

Offers must be listed as either Free, Trial, or Contact Me. If Contact Me is chosen, publishers must enable test drive.

1420.3 Content requirements

The following requirements must be met in the offer listing:

  • The Offer Description field must be in plain text or simple HTML format, and must include the full product name.
  • The Terms of Use field must include the full Terms of Use or contain a working URL.

1420.4 Functionality

Any feature changes between updates must be re-certified when the offer is re-submitted. The entire solution package must be submitted with each update to ensure dependency issues are covered. The version number must be incremented with each update.

1420.5 Technical requirements

Offers must support:

  • Dynamics 365 v9.1 or above.
  • Unified Client Interface (UCI) (Model Driven Apps only).

Offers must only use publicly available APIs.

Submitted packages must contain all required artifacts for publication on the Marketplace.

The end-to-end (E2E) functional document must be updated with functional scenarios and the user/admin journey.

1420.6 Code validation

Canvas apps and Common Data Services solutions will have their code validated to check for the following:

  • Static formula errors and warnings.
  • Runtime errors (may occur once the app is opened in Run mode to view).
  • Accessibility errors.

For further information on these requirements, see the app certification checklist.

1420.7 Deployment validation

Offers will be installed to a PowerApps Environment using Package Deployer to ensure that:

  • Canvas apps successfully connect through provided connectors.
  • All Common Data Service components (entities, web resources, plug-ins, and other components) are available.
  • All associated components are properly removed upon uninstall.

For further information on these requirements, see the app certification checklist.

1420.8 Functionality validation

Offers should include the E2E functional document. Video links may be emailed as an alternative.

1420.9 Security validation

Apps will be checked for:

  • Connections to external data sources or connections that require access. Proper connection details should be included in the E2E functional document.
  • External connections out of PowerApps connectors.

Custom code provided inside Package Deployer will be validated before offer approval and checked for retrieval of customer data from the target environment.

1420.10 Sitemap validation

Published app customizations must not change or remove any out of box (OOB) site map.

1440 Dynamics 365 Finance Ops

The policies listed in this section apply only to Dynamics 365 Finance Ops offers.

For further information on these requirements, see the requirements for publishing apps on AppSource.

1440.1 Content requirements

The following requirements must be met in the offer listing:

  • The Offer Description field must be in HTML format and must include the full product name.
  • The Terms of Use field must include the full Terms of Use in HTML format or contain a working URL.
  • The Lead Management and Lead Destination fields must have a valid value other than “none”.
  • The Contact Email and Phone Number fields must have valid, working values.
  • The Storefront Details > App Choice field must be set to “Contact me”.
  • The CAR file must be uploaded using the Technical Info > Validation asset(s) field.

1440.2 Technical requirements

Offers must support the most current version of Dynamics 365.

1440.3 Code validation

Offers must be validated to verify that custom code meets Microsoft guidelines.

Before submission, publishers must:

  • Successfully create a CAR without any localization, accessibility, performance, or security issues.
  • Publish a solution package with all the required artifacts to LCS and create a solution identifier (GUID) for the solution.

1440.4 Deployment validation

Offers must be validated to verify that a solution package can be successfully bundled and delivered in a Microsoft Dynamics 365 for Finance and Operations environment.

Before submission, publishers must:

  • Reference best practice information in the Migrate and Create methodology section of LCS.
  • Successfully deploy at least one Finance and Operations environment without any errors.
    • The environment configuration must be the same as the partner’s reference environment.
    • Partner-supplied master and reference data must be able to be successfully pushed into the Finance and Operations environment without any errors.

1440.5 Functionality validation

During the functionality demonstration:

  • A user must be able to sign in to the environment without any errors.
  • Business transactions must be able to be completed as defined in the package scope without any errors.

3000 Co-sell solutions

The policies listed in this section apply only to Co-Sell Solutions offers.

3000.1 Business requirements

Offers built on Dynamics 365 Customer Engagement, Finance and Ops, or PowerApps where the partner has signed up for the Business Applications ISV Connect program are eligible for IP Co-Sell acceleration, subject to the following requirements.

  1. Your offer must be listed on AppSource.
  2. Your offer must include a complete co-sell bill of materials, including:
    • A solution pitch deck,
    • A one-page leave-behind or website listing,
    • A case study or website listing.
  3. You must have a business profile in Partner Center.
  4. You must have a dedicated sales contact for each co-sell eligible region (country or geographical area).

Next steps

Visit the Azure Marketplace and AppSource Publisher Guide page.