Guidelines for Power BI visuals with additional purchases

Until recently, the Marketplace (AppSource) accepted only Power BI visuals that are free. This policy is changing so that visuals with "additional purchase may be required" price-tag may also be submitted to the AppSource. Additional purchase may be required visuals are similar to in-app purchase (IAP) adds-in in office store. Developers may also submit these visuals for certification after the AppSource team approves them, and after making sure they comply with certification requirements, as described in the Certified custom visuals article.

Note

For the visual to be certified, it must not access external services or resources.

Note

All free visuals should keep same free features previously offered. You may add optional advanced paid features on top of the old free features. We recommend to submit the IAP visuals with the advanced features as new visuals and not to update the old free ones.

What's changing in the submission process?

Developers upload their IAP visuals to AppSource via the Seller Dashboard, as they've been doing for free visuals. To indicate that the submitted visual has IAP features, developers should write in the seller dashboard notes: "Visual with in-app purchase." Also, developers need to provide a license key or token so that the validation team can validate the IAP features. Once the visual is validated and approved, the AppSource listing for the IAP visual states 'Additional purchase may be required' under the pricing options.

What is a Power BI visual with IAP features?

An IAP visual is free visual and offers free features, but also has additional advanced features for which extra charges may be applied to operate them. Developers must notify users in the visual's description regarding which features require additional purchases to operate. Currently, Microsoft does not provide native application programming interfaces (APIs) to support purchase in apps and add-ins. Developers may use any third-party payment system for those purchases. Refer to our store policy.

Note

Watermarks are not allowed on the free features. Developers may display a popup window or watermark if the advanced paid features are used without a valid license.

Logo guidelines

This section describes the specifications for adding logos and logotypes in visuals.

Note

Logos are allowed in edit mode only. Logos can't be displayed in view mode.

definitions

things-to-keep

things-to

size-and-format

margins-and

edit-mode

Best practices

Visual landing page

Use the landing page to clarify to users how they can use your visual and where to purchase the license. Don't include videos that are automatically triggered. Only add material that helps improve the user's experience, such as information or links on license purchasing details, and how to use IAP features.

License key and token

For user convenience, add license key or token related fields at the top of the format pane, so they are better located for users.

FAQ

For more information and answers to questions, visit Frequently asked questions about visuals with additional purchases.

Next steps

Learn how you can publish your custom visual to AppSource for others to discover and use.