Skip to content

Conversation

troystaylor
Copy link
Contributor

brave_yVF0DUJYYm brave_Yu2NubbCPx

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.

@troystaylor troystaylor requested a review from a team as a code owner September 24, 2025 18:20
@vmanoharas
Copy link
Contributor

Hi @troystaylor,

Our IP connector certification process has been changed. Kindly refer the below link. As per the process, we have shared a MS Form through email to the email that you mentioned in the swagger file. Please fill the form to proceed for the next process and please reply here once the form is filled.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification

@troystaylor
Copy link
Contributor Author

@vmanoharas The MS Form has been submitted - can you tell me if this is a temporary necessity, as I don't see this form as a step on the MS Learn page? Also, I've received 6 email notifications - do all 6 need to be completed or just the 1?

@vmanoharas
Copy link
Contributor

Hi @troystaylor,

Thank you for filling the form. Please refer the MS learn form where it is mentioned to fill the form - https://learn.microsoft.com/en-us/connectors/custom-connectors/verified-credentials-ip#fill-out-form

Additionally, the from should be filled and Onevet verification done for each and every submission. But in case the submission is very much frequent, form can be filled for every 3 months once. Onevet verification should be done every time.

@vmanoharas
Copy link
Contributor

vmanoharas commented Oct 8, 2025

Hi @troystaylor,

Shared Onevet verification link for this connector. Kindly complete the verification. Please message here once done.

@troystaylor
Copy link
Contributor Author

@vmanoharas From that page, it is not clear that the form/AU10TIX process needs to be completed with every PR, only one-time. For any Independent Publisher, completion with every PR is too cumbersome. Please have a PM contact me.

@vmanoharas
Copy link
Contributor

@vmanoharas From that page, it is not clear that the form/AU10TIX process needs to be completed with every PR, only one-time. For any Independent Publisher, completion with every PR is too cumbersome. Please have a PM contact me.

Hi @troystaylor, actually, There are two types of submission links we use. The first is for the complete verification process, which you previously completed for the Toggle PR. This time, however, we’ve submitted a lite version, so you likely won’t need to go through the full verification again.
That said, could you please share a screenshot of the email you received and what you see after clicking the link? This will help us move forward with the next steps.
If this submission doesn’t trigger a full verification, please note that we’ll need to complete the full process once every three months.
Appreciate your help!

@troystaylor
Copy link
Contributor Author

I have received emails to fill out the MS Form (one for each PR) but nothing from OneVet

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.

2 participants