Non-Microsoft publisher certification process

This process is for non-Microsoft publishers (excluding independent publishers). If you're an independent publisher, go to Independent publisher certification process.

After you've finished developing your custom connector, follow these steps to prepare it for certification and generate the connector files to submit to Microsoft.

Note

This topic provides information for certifying custom connectors in Azure Logic Apps, Power Automate, and Power Apps. Before following the steps in this article, read Get your connector certified and register your custom connector with Microsoft.

Step 1: Register your connector

You don't need to have finished development on your custom connector to apply for certification. To begin the certification process, register your connector for certification by filling out our registration form.

Expect an email within two business days from a Microsoft contact, who will:

  • Understand your custom connector.
  • Learn about your development progress.
  • Guide you through the certification process.

Step 2: Meet submission requirements

To maintain a high standard of quality and consistency among our certified connectors, Microsoft has a set of requirements and guidelines that your custom connector must adhere to for certification.

Give your connector a title

  • Must exist and be written in English.
  • Must be unique and distinguishable from any existing connector title.
  • Should be the name of your product or organization.
  • Should follow existing naming patterns for certified connectors.
  • Can't be longer than 30 characters.
  • Can't contain the words "API", "Connector", or any of our Power Platform product names (for example, "Power Apps").
  • Can't end in a non-alphanumeric character, including carriage return, new line, or blank space.

Examples

  • Good connector titles: "Azure Sentinel", "Office 365 Outlook"
  • Poor connector titles: "Azure Sentinel's Power Apps Connector", "Office 365 Outlook API"

Write a description for your connector

  • Must exist and be written in English.
  • Must be free of grammatical and spelling errors.
  • Should describe concisely the main purpose and value offered by your connector.
  • Can't be shorter than 30 characters or longer than 500 characters.
  • Can't contain any Power Platform product names (for example, "Power Apps").

Design an icon for your connector

This section doesn't apply to independent publishers.

  • Create a logo of approximately 160 × 160 pixels inside a square of approximately 230 × 230 pixels (no rounded edges).
  • Must contain a non-transparent, non-white color (#ffffff) background and not-default color (#007ee5) that matches your specified icon background color.
  • Must be unique to any other certified connector icon.
  • Must be submitted in PNG format as icon.png.

Define operation and parameter summaries and descriptions

  • Must exist and be written in English.
  • Must be free of grammatical and spelling errors.
  • Operation and parameter summaries should be phrases of 80 characters or shorter, and contain only alphanumeric characters or parentheses.
  • Operation and parameter descriptions should be full, descriptive sentences, and end in punctuation.
  • Can't contain any of the Microsoft Power Platform product names (for example, "Power Apps").

Define exact operation responses

  • Define operation responses with an exact schema only with expected responses.
  • Do not use default responses with an exact schema definition.
  • Provide valid response schema definitions for all operations in the swagger. Empty response schemas aren't allowed. This means no dynamic content will be shown in the output and makers must use JSON to parse the response.

Create quality English language strings

Connectors are localized as part of Power Automate localization; therefore, when you're developing a connector, the quality of the English language strings is key to the translation quality. Here are some major areas to focus on as you create the values of the strings you'll provide.

  • Make sure to run a spell check program to ensure all string values are free of typographical errors. If there's any incomplete English language string, the translation result will be incomplete or incorrect in context.

  • Make sure the sentence is in complete form. If the sentence is not complete, that can also generate lower quality translations.

  • Make sure the meaning of the sentence is clear. If the meaning of the sentence is ambiguous, that can also generate lower quality or incorrect translations.

  • Avoid runtime composite strings, if possible. Use fully formed sentences instead. Concatenated strings or sentences make it difficult to translate, or can cause a wrong translation.

  • If you use abbreviations, make sure to capitalize them to make it clear. This will reduce the chance of it being mistaken for a typographical error.

  • Strings in CaMel form (ex. minimizeHighways or MinimizeHighways) are typically considered non-translatable. If you want to localize the string value, you should fix the CaMel form string.

Step 3: Add metadata

Your connector artifacts (files) must contain specific metadata describing the connector and its end service. The information provided in metadata will be published in our connector documentation and is publicly accessible by all users. Don't provide any private or confidential information, and let us know through your Microsoft contact if there are any issues with providing us this information. To learn how the metadata will be documented, visit any one of the connector-specific documentation pages under Connector reference.

Step 3a: publisher and stackOwner properties

  • "publisher" is the name of your company or organization. Provide the full company name (for example, "Contoso Corporation"). This must be in alphanumeric format.

  • "stackOwner" is the owning company or organization of the back-end service stack that the connector is connecting to. This must be in alphanumeric format.

File Location: apiProperties.json

Syntax: The publisher and stackOwner properties exist as top-level properties within the apiProperties.json file. Add the following highlighted lines as shown. Ensure that you enter the property name and schema exactly as shown.

Screenshot showing publisher and stackOwner properties, which are available in Sample code snippets.

Code showing two lines highlighted in red. The two lines are for publisher and stackOwner, and are located directly after the closing square bracket in "capabilities":[ "actions" ]

Step 3b: Product or end service metadata

  • "contact" describes how users can contact the product or end service support resources for assistance or troubleshooting. Provide one value for each of the following:

    • Name of your support team
    • URL of your support website
    • Support email
  • "Website" is the product or end service website. It gives users information about the product or end service they're using with the connector. This should be a URL.

  • "Privacy policy" refers to the public privacy policy of the product or end service, or its company or organization. This should be a URL.

  • "Categories" refer to a logical classification of your connector using a maximum of two of the following categories: AI, Business Management, Business Intelligence, Collaboration, Commerce, Communication, Content and Files, Finance, Data, Human Resources, Internet of Things, IT Operations, Lifestyle and Entertainment, Marketing, Productivity, Sales and CRM, Security, Social Media, Website.

File Location: apiDefinition.swagger.json

Syntax: The contact object is a standard field defined by the OpenAPI contract under the top-level info property. Website, Privacy policy, and Categories will be defined in a custom top-level extension called x-ms-connector-metadata. The Categories property value is a semicolon-delimited string. Add the red-lined code snippets as shown. Ensure you enter the schema exactly as shown; don't change the propertyName.

Screenshot showing x-ms-connector-metadata, which is available as a usable example in Sample code snippets

Code showing the block defining the contact object highlighted in red. This block must be located directly under the description. Another block, x-ms-connector-metadata, is also highlighted in red. This block must be located directly under paths: {}.

Step 3c: Sample code snippets

You can use the following code snippets to copy and enter your information. Ensure that you add the snippets to the correct files in the correct locations as described in the preceding section.

    "publisher": "_____",
    "stackOwner": "_____"
    "contact": {
      "name": "_____",
      "url": "_____",
      "email": "_____"
    }
    "x-ms-connector-metadata": [
      {
        "propertyName": "Website",
        "propertyValue": "_____"
      },
      {
        "propertyName": "Privacy policy",
        "propertyValue": "_____"
      },
      {
        "propertyName": "Categories",
        "propertyValue": "_____;_____"
      }
    ]

Note

There is a current limitation in the use of the stackOwner property and the Paconn CLI tool. For more information, go to Limitations in the README file.

Step 3d: Validate your custom connector files

Run paconn validate --api-def [Location of apiDefinition.swagger.json]. This tool will validate your connector definition and let you know of any errors you'll need to fix before submission.

If your connector uses OAuth as its authentication type, add these allowed redirect URLs to your app:

  • https://global.consent.azure-apim.net/redirect

  • https://global-test.consent.azure-apim.net/redirect

Step 4: Prepare the connector artifacts

This step should take you about one week to complete.

Note

Ensure that you've followed the specifications and have ensured the quality of your connector before certification. Failure to do so will result in delays in certification because you'll be asked to make changes.

You'll be submitting to Microsoft a set of files called connector artifacts, downloaded by using a command-line interface (CLI) tool provided by Microsoft. This tool will validate your connector for any breaking errors.

Follow these steps to get started:

  1. Install the Microsoft Power Platform Connectors CLI tool by following the installation instructions.

  2. Sign in to Microsoft Power Platform using your command line by running paconn login. Follow the instructions to sign in using Microsoft's Device Code process.

  3. After you're authenticated, download your custom connector files:

    • Run paconn download. Select the environment your custom connector is located in by specifying its number in the command line, and then select the custom connector name.

    The tool will download your connector artifacts in a folder to the file system location where you ran paconn. Depending on the type of publisher, you'll find various artifacts:

    Publisher Artifact
    Independent publisher apiDefinition.swagger.json
    apiProperties.json
    Non-Microsoft publisher (other than independent) apiDefinition.swagger.json
    apiProperties.json
    settings.json
    The connector icon

Create a Readme file artifact

A Readme.md file is necessary for both independent publishers and non-Microsoft publishers. You need to create a Readme.md file to document your connector's features and functionality. For an example of documentation to include, go to the Readme.md example.

Step 5: Submit your connector for deployment

Note

During the submission process, you'll be open-sourcing your connector to our Microsoft Power Platform Connectors repository.

  1. Follow the instructions in Submit your connector for Microsoft certification to submit to GitHub and the certification portal.

  2. Once you submit a pull request to the open-source repository, Microsoft will deploy and validate your connector within two business days. If updates are required, allow an extra two business days.

    As part of submission, Microsoft will validate your connector by using the CLA-bot, Swagger Validator, and Breaking Change Detector tools. If you need to troubleshoot swagger errors, go to Fix Swagger Validator errors.

Step 6: Expectations for testing done by non-Microsoft publishers

After we validate your connector, we will ask you to perform thorough testing.

  1. Follow the instructions in Test your connector in certification to create an environment in the Preview region in preparation for your testing.

  2. Within one week, notify your Microsoft contact that you've completed testing so we can begin deployment.

  3. After your connector's functionality and content are validated by both Microsoft and you, we'll stage the connector for deployment in the Preview region for testing.

Step 7: Wait for deployment

After your connector is validated for testing, we'll deploy it across all products and regions.

Important

On average, it takes 7 to 10 business days to deploy the connector. This is required regardless of the size or complexity of your connector, whether it's new or an update. In order to protect integrity, the connector will be subjected to the same validation tasks to test functionality and content that are followed in every deployment.

We'll notify you by email with the names of the regions the connector will be deployed to, as deployment to regions is done in steps. If there's a deployment delay or freeze, non-Microsoft publishers can find the status in the Activity Control in the ISV portal. Independent publishers will be notified by email.

Production deployment

Our connector deployment schedules for production start Monday and Wednesday mornings, PST/PDT. You'll need to let Microsoft know that you're ready for production deployment at least 24 hours in advance for us to include your connector in the next scheduled deployment. Non-Microsoft publishers can notify us in the Activity Control of ISV portal. Independent publishers can notify their Microsoft contact.

Region deployment

Deployment to various regions takes place in a pre-determined daily sequence. The regions are:

  • Testing.
  • US preview.
  • Asia, except Japan and India.
  • Europe, except UK.
  • Brazil, Canada, Japan, and India.
  • Australia, UK, and US.

For example, if your connector is schedule to deploy on Monday, it will deploy to the Testing region on day 1. Then, it will deploy to the US preview region on Day 2. Deployment will continue daily until the connector is deployed to all six regions.

We don't deploy on Fridays, Saturdays, Sundays, and US holidays.

As your connector is finishing certification, we'll engage you about a marketing opportunity for the connector on the Power Automate blog.

Step 8: Explore post-deployment options

Here are some options you can explore after your connector is deployed:

Checklist before submitting

Before moving on to Submit your connector for Microsoft certification, ensure that:

If you're a non-Microsoft publisher (and not an independent publisher), you'll be asked to agree to our Partner Agreement and non-disclosure agreement when you submit for Microsoft certification. If you'd like to review these terms and language before submission, connect with your Microsoft contact.

Next step

Submit your connector for Microsoft certification