ABN Lookup (Independent Publisher)

[jsnl85]

Search the Australian Business Register to find companies and their business status.

✔️ Certification Checklist

• 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.

📄 Independent Publisher Requirements

• 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.

👀 Extra checklists

• Did some additional checks against the Certification policy errors list

✅ Working Flows

1. Successful Flow Run
   

🧪 Working Operations on the Custom Connector Test UI

🙏 Open API validation successful

🚀 Package validation successful

📦 Package shared below

ConnectorPackage.zip

[jsnl85]

@microsoft-github-policy-service agree company="sp365 pty ltd"

[vmanoharas]

Hi @jsnl85,

Thank you for your interest for submitting IP connector. Kindly follow below link and submit your connector files.

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

Additionally, please prepare package as per the below link and submit.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

[jsnl85]

Hi @vmanoharas,

The package has been prepared and shared below:
ConnectorPackage.zip

🧪 Open API validation successful:

🧪 Package validation successful:

[vmanoharas]

Thank you @jsnl85 for submitting the package.

As next steps, we need to start OneVet Verification, shared the MS Form, please fill the same.

[jsnl85]

Thank you @vmanoharas, that's complete now.

[jsnl85]

@vmanoharas - just checking if you need any more info from my side

[vmanoharas]

Hi @jsnl85,

Apologies for the delay. We have sent you the OneVet verification link. Please complete the Onevet verification

[jsnl85]

Hi @vmanoharas,

Thank you for sending the OneVet verification link.

This is now complete.

[vmanoharas]

certify-connector

[certificationteam]

We reviewed your submission and identified some changes that are needed before we can publish or update the connector.Kindly make the following changes and resubmit the request for certification.You can refer here to understand more about the error codes and how to fix them.

Many Thanks,
Copilot Connector Certification Team

Error(s) are:

1. More than one folder found in the pull request. Changes should be present in only one folder.

[vmanoharas]

Hi @jsnl85,

Please remove screenshot folder, settings.json and icon.png files.

[jsnl85]

Hi @vmanoharas,

I've followed your instructions. Extra files have been removed.

Please let me know if there are any other restrictions.

Kind regards,

[vmanoharas]

certify-connector

[jsnl85]

Hi @vmanoharas, just checking-in, as it's been more than 1 month since the last update.

[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.