Get a Power BI visual certified

Certified Power BI visuals are visuals in the Marketplace that meet certain specified code requirements that the Microsoft Power BI team has tested and approved. The tests are designed to check that the visual doesn't access external services or resources.

Certified Power BI visuals and standard Power BI visuals are used in the same way. They can be added to Power BI Desktop and Power BI service, and viewed with Power BI mobile and Power BI Embedded.

The certification process is an optional process. It's up to the developers to decide if they want their Power BI visual in the Marketplace to be certified. 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.

Uncertified Power BI visuals do not necessarily mean unsafe visuals. Some visuals aren't certified because they don’t comply with one or more of the certification requirements. For example, connecting to an external service like map visuals, or visuals using commercial libraries.

If you're a web developer interested in creating your own Power BI visuals and adding them to the Microsoft AppSource, start with the Developing a Power BI visual tutorial.


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


Microsoft can remove a Power BI visual from the Certified Power BI visuals list at its discretion.

Certification requirements

To get your Power BI visual certified, make sure your Power BI visual complies with the requirements listed in this section.


We recommend that you use EsLint with the default security rule set, to pre-validate your code before submission.

  • Microsoft Seller Dashboard or Partner Center approved. Your Power BI visual should be in our Marketplace.

  • The Power BI visual is written with API v2.5 or higher.

  • The code repository is available for review by the Power BI team. For example, a readable format of the source code (JavaScript or TypeScript), is available to us through GitHub.


    You don’t have to publicly share your code in Github.

  • Code repository requirements:

    • Must include these files:
      • .gitignore
      • capabilities.json
      • pbiviz.json
      • package.json
      • package-lock.json
      • tsconfig.json
    • Must not include the node_modules folder (add node_modules to the.gitingore* file).
    • The npm install command must not return any errors.
    • The npm audit command must not return any warnings with high or moderate level.
    • The pbiviz package command must not return any errors.
    • Must include TSlint from Microsoft with no overridden configurations. This command must not return any lint errors.
    • The compiled package of the Power BI visual must match the submitted package.
  • Source Code requirements:

    • The Power BI visual must support the Rendering Events API.
    • Ensure no arbitrary/dynamic code is run (bad: eval(), unsafe to use of settimeout(), requestAnimationFrame(), setinterval(some function with user input), running user input/data).
    • Ensure DOM is manipulated safely (bad: innerHTML, D3.html(<some user/data input>), use sanitization for user input/data before adding it to the DOM.
    • Ensure there are no javascript errors or exceptions in the browser console, for any input data. Users might use your Power BI visual with a different range of unexpected data, so the visual must not fail. You can use this sample report as a test dataset.
  • If any properties in the file capabilities.json are changed, make sure that they do not break existing user's reports.

  • Make sure the Power BI visual complies with the guidelines for Power BI visuals.

  • Your code can only use public reviewable OSS components such as public Javascript or TypeScript libraries. The source code has to be available for reviewing and doesn't have known vulnerabilities. We can't verify a custom visual using a commercial component.

  • The Power BI visual must not access external services or resources. For example, no HTTP/S or WebSocket requests can go out of Power BI to any services.

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.


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.


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.


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

Next steps

More questions? Try the Power BI Community