Connector Certification

When developing a custom connector, or if you've been given one by another developer or vendor, you'll notice that they require you to lower the security settings in Power BI to use them. This is due to the fact that M is a versatile language that (as seen in Handling Authentication) has the capacity to interact with stored credentials. This means that we needed to give end users a way to only allow certified connectors to run.

The 'Connector Certification' program is a program in which Microsoft works with vendors to extend the data connectivity capabilities of Power BI.

Certified connectors are:

  • Certified by Microsoft
  • Distributed by Microsoft
  • Maintained by the developer
  • Supported by the developer

We work with vendors to try to make sure that they have support in maintenance, but customer issues with the connector itself will be directed to the developer.

We have a certain set of requirements for certification. We recognize that not every developer can meet these requirements, and as above we're hoping to introduce a feature set that will handle their needs in short order.

Certification Requirements

Before starting

  • Developer must own the data source or have recorded permission from the owner of the data source to develop a connector for it.
  • Developer must sign an NDA
  • Developer must sign a business partner agreement with our team
    • The business partner agreement is different from a Microsoft Partner agreement. The agreement addresses terms of making your connector code available to us for use in the relevant products. We will sign the agreement when we kick off the process.
  • Data source must not be an internal only data source


  • PBIX file
    • Report should contain one or more queries to test each item in their navigation table
    • If you don't have a set schema (as an example, databases), you should include a query for each 'type' of table you're concerned with.
  • .mez file
    • The .mez file should follow style standards. For example, use Product.mez rather than Product_PowerBI_Connector.mez.
  • Test account
    • The test account will be reused whenever we're troubleshooting or certifying updates, so if you have a persistent test account it would be best to find a way to share this.
  • Link to external dependencies (ODBC drivers, for example).
  • Documentation on how to use the connector if needed


  • If using Extension.CurrentCredentials() …
    • Is the usage required? If so, where do the credentials get sent to?
    • Are the requests guaranteed to be made via HTTPS?
    • If the credentials are sent using Web.Contents() via GET …
      • Can it be turned into a POST?
      • If GET is required, connector MUST use the CredentialQueryString record in the Web.Contents() options record to pass in sensitive credentials
  • If Diagnostics.* functions are used …
    • Validate what is being traced - it MUST NOT
      • Contain PII
      • Contain large amounts of data
    • If you implemented significant tracing in development, you should attach it to a variable that checks if tracing should be on or not, and you should turn it off before shipping.
  • If Expression.Evaluate() is used …
    • Validate where the expression is coming from / what it is (i.e. can dynamically construct calls to Extension.CurrentCredentials() etc…
    • Expression should not be user provided / take user input
    • Expression should not be dynamic (i.e. retrieved from a web call)

Features and Style

  • Connector MUST use Section document format
  • Connector MUST have Version adornment on section
  • Connector MUST provide function documentation metadata
  • Connector MUST have TestConnection handler
  • Connector MUST follow naming conventions (DataSourceKind.FunctionName)
  • FunctionName should make sense for their domain - generally "Contents", "Tables", "Document", "Databases" …
  • Connector SHOULD have icons
  • Connector SHOULD provide a navigation table
  • Connector SHOULD place strings in resources.resx file

Getting your connector certified

If you'd like to reach out about connector certification, please contact us at