SigningHub 2.0.0 - Updated URLs

[JorgeFriasAscertia]

We have moved the URLs listening to the events, this new PR covers the new resource locations.

Most likely will raise the same error as the previous one as is updating two different connectors, let me know for the future if you prefer 2 different PRs.

Thanks,
Jorge

---

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 @JorgeFriasAscertia,

Yes it throughs same error. If possible could you please separate them? Otherwise we can approve. Please let me know.

[JorgeFriasAscertia]

Hi @vmanoharas let's approve this one. From now on I will add different PRs for each connector if that's OK.

Thanks a lot.

[vmanoharas]

Dear Partner,

Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors.

As next steps:

Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
Package your connector files- Prepare Power Platform connector and plugin files for certification
Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
Initiate a certification request in Partner Center- Verified publisher certification process
Ensure your connector files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
Test your connector post certification to provide go-live for deployment- Testing Guidelines
If you wish to Update your connector in future- Updating Guidelines

For any queries or concerns please get in touch with us on certificationteam@microsoft.com

Many thanks,
Power Platform
Copilot connector & plugin certification team