LegiScan (Independent Publisher)

[krautrocker]

---

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.

[krautrocker]

Proof-of-life:

[krautrocker]

Connector package validated:

[vmanoharas]

Hi @krautrocker,

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

[krautrocker]

Just submitted the form @vmanoharas

[vmanoharas]

Hi @krautrocker,

Submitted Onevet verification for the PR. If you have received email, please complete verification, else please let us know so that we will proceed for certification.

[krautrocker]

OneVet verification complete based on previous data, as discussed. Will re-verify once every three months @vmanoharas

[vmanoharas]

certify-connector

[certificationteam]

Congratulations — your certification request has been approved. Your connector will be included in the upcoming deployment schedule for production release and the supporting documentation will be published. This end-to-end process typically takes 3–4 weeks.

Many Thanks,
Copilot Connector Certification Team

[krautrocker]

Thank you!

[vmanoharas]

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

[vmanoharas]

Hello Partner,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed,
Thank you very much for working with us.