Winston AI (Independent Publisher)

[fordosa90]

---

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.

[vmanoharas]

Hi @fordosa90,

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

[fordosa90]

@vmanoharas thank you, will do.

A few questions in the meantime, knowing, that most publishers are investing their free time trying to help you (Microsoft) and the customers by submitting and maintaining/owning connectors.

• can also the PR template be updated? I know many just skip it, but it describes then an outdated and wrong process for publishers to follow
• any specific reason why in the new process only the original creator can submit PR for the connectors? This is going against the "open source" format and community spirit of the whole Connector program
• any specific reason why ZIP files (binaries) are expected to be uploaded as part of the new process to the repository? GIT is not meant to handle binaries, it leads to significant bloating since deltas are not granular. Moreover, change management process gets confusing as their is no native visibility over modifications of a ZIP content

I understand the reasoning behind the 2 prepared ZIP files, however, this could be easily (and in better manner) achieved using the existing source code and proper CICD pipelines (github actions) or something similar, instead of the time consuming and overwhelming "new" process. Is the aim to reduce connector submissions by expecting even more time invested from the publishers?

@troystaylor maybe you know more here than me about the reasons of these changes?