Get a Power BI visual certified

Certified Power BI visuals are Power BI visuals in AppSource that meet the Microsoft Power BI team code requirements. These visuals are tested to verify that they don't access external services or resources, and that they follow secure coding patterns and guidelines.

Once a Power BI visual is certified, it offers more features. For example, you can export to PowerPoint, or display the visual in received emails, when a user subscribes to report pages.

The certification process is optional. Power BI visuals that are not certified, are not necessarily unsafe Power BI visuals. Some Power BI visuals aren't certified because they don’t comply with one or more of the certification requirements. For example, a map Power BI visual connecting to an external service, or a Power BI visual using commercial libraries.

Note

Microsoft is not the author of third-party Power BI visuals. To verify the functionality of third-party visuals, contact the author of the visual directly.

Certification requirements

To get your Power BI visual certified, your Power BI visual must comply with the requirements listed in this section.

General requirements

Your Power BI visual has to be approved by Seller Dashboard or Partner Center. We recommend that your Power BI visual is already in AppSource. To learn how to publish a Power BI visual to AppSource, see Publish Power BI visuals to Partner Center.

Before submitting your Power BI visual to be certified, verify that it complies with the guidelines for Power BI visuals.

When submitting the Power BI visual, make sure that the compiled package exactly matches the submitted package.

Code repository requirements

Although you don’t have to publicly share your code in GitHub, the code repository has to be available for a review by the Power BI team. The best way to do this, is by providing the source code (JavaScript or TypeScript) in GitHub.

The repository must contain code for only one Power BI visual. It can't contain code for multiple Power BI visuals, or unrelated code.

The repository must contain a branch named certification. The source code in this branch has to match the submitted package. This code can only be updated during the next submission process, if you're resubmitting your Power BI visual.

If your Power BI visual uses private npm packages, or git submodules, you must provide access to the additional repositories containing this code.

File requirements

Use the latest version of the API to write the Power BI visual.

The repository must include the following files:

  • .gitignore - Add node_modules to this file. The code cannot include the node_modules folder.
  • capabilities.json - If you are submitting newer version of your Power BI visual with changes to the properties in this file, verify that they do not break reports for existing users.
  • pbiviz.json
  • package.json
  • package-lock.json
  • tsconfig.json

Command requirements

Make sure that the following commands don't return any errors.

  • npm install
  • pbiviz package
  • npm audit - Must not return any warnings with high or moderate level.
  • TSlint from Microsoft with no overridden configurations. This command must not return any lint errors.

Compiling requirements

Use the latest version of powerbi-visuals-tools to write the Power BI visual.

You must compile your Power BI visual with pbiviz package. If you're using your own build scripts, provide a npm run package custom build command.

Source code requirements

Verify that you follow the Power BI visuals additional certification policy list. If your submission doesn't follow these guidelines, the rejection email from Partner Center will include the policy numbers listed in this link.

Follow the code requirements listed below to make sure that your code is in line with the Power BI certification policies.

Required

  • Only use public reviewable OSS components such as public JavaScript or TypeScript libraries.
  • The code must support the Rendering Events API.
  • Ensure DOM is manipulated safely. Use sanitization for user input or user data, before adding it to DOM.
  • Use the sample report as a test dataset.

Not allowed

  • Accessing external services or resources. For example, no HTTP/S or WebSocket requests can go out of Power BI to any services.
  • Using innerHTML, or D3.html(user data or user input).
  • JavaScript errors or exceptions in the browser console, for any input data.
  • Arbitrary or dynamic code such as eval(), unsafe use of settimeout(), requestAnimationFrame(), setinterval(user input function), and user input or user data.
  • Minified JavaScript files or projects.

Submitting a Power BI visual for certification

You can request to have your Power BI visual certified by the Power BI team via Partner Center.

Tip

The Power BI certification process might take time. If you're creating a new Power BI visual, we recommend that you publish your Power BI visual via the Partner Center before you request Power BI certification. This ensures that the publishing of your visual is not delayed.

To request Power BI certification:

  1. Sign in to Partner Center.
  2. On the Overview page, choose your Power BI visual, and go to the Product setup page.
  3. Select the Request Power BI certification check box.
  4. On the Review and publish page, in the Notes for certification text box, provide a link to the source code and the credentials required to access it.

Note

If you are in the middle of a Power BI visual submission process, and have to use Seller Dashboard (the old management tool), review the Seller Dashboard certification submission process instructions.

Certified Power BI visuals

The certified Power BI visuals are listed below. Click the link to open the Power BI visual in AppSource. If a video is available, you can click the video link to watch it.

FAQ

For more information about visuals, see Frequently asked questions about certified visuals.

Next steps

More questions? Try the Power BI Community