Skip to content

Conversation

@ifrifr
Copy link

@ifrifr ifrifr commented Jan 12, 2026


When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@ifrifr ifrifr requested a review from a team as a code owner January 12, 2026 14:39
@ifrifr
Copy link
Author

ifrifr commented Jan 13, 2026

@microsoft-github-policy-service agree company="IFR"

@vmanoharas
Copy link
Contributor

Hi @ifrifr,

Could you please confirm that this is a proposal?

@ifrifr
Copy link
Author

ifrifr commented Jan 14, 2026

Hello @vmanoharas, we are a bit confused about the steps on certifying the connector.

We, IFR, have developed the connector for our partner's platform (Deliverea). The connector is fully functional and tested and we are ready to certify it but we need a little bit of guiddance.

@vmanoharas
Copy link
Contributor

Hi @ifrifr,

If you work is for the underlying service, please submit your connector as Verified Publisher connector, otherwise Independent Publisher Connector.

Verified Publisher Connector
https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification

Independent Publisher Connector
https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

@ifrifr
Copy link
Author

ifrifr commented Jan 22, 2026

Hello @vmanoharas as we do not own the service, we are continuing with Independent Publisher Connector.

@ifrifr ifrifr changed the title Intro.md Deliverea connector (independent publisher) Jan 22, 2026
@ifrifr ifrifr changed the title Deliverea connector (independent publisher) Deliverea connector (Independent Publisher) Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants