Scrive eSign - updates

[marcusdelang]

---

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.

• [x] 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.
• [X] I attest that the connector works and I verified by deploying and testing all the operations.
• [X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• [X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• [X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• [X] 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.

[marcusdelang]

This is ready to merge. These changes are onboarded on the current deployment schedule and should be in production in a few days.

[marcusdelang]

These changes are now live in production. Please merge theses changes so we keep it synced.

[marcusdelang]

@Amjed-Ayoub Can you merge this please? 🙏

[marcusdelang]

Or @vmanoharas, please merge this 🙏

[marcusdelang]

@vmanoharas Thank you. Unrelated question, it seems like the connector certification portal is broken. Do you know if it will be fixed?

[vmanoharas]

Hi @marcusdelang,

Apologies for the inconvenience caused, there was an issue in the morning, please try now if it doesn't work, kindly try with .zip file. Please let me know none of the solution works.

[marcusdelang]

Hi @marcusdelang,

Apologies for the inconvenience caused, there was an issue in the morning, please try now if it doesn't work, kindly try with .zip file. Please let me know none of the solution works.

@vmanoharas None of the solutions work. I tried both the .zip and the submitting using the repo but both of them get an error. This is the error I get when uploading the .zip.

[vmanoharas]

Hello @marcusdelang,

Our certification process is changed, kindly follow the below steps.

Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors & Plugins. Read the blog here- Announcing Partner Center to certify and publish Power Platform Copilot connectors and plugins

As next steps:

1. Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
2. Package your connector and plugin files- Prepare Power Platform connector and plugin files for certification
3. Initiate a certification request in Partner Center- Verified publisher certification process
4. Ensure your connector & plugin files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace
5. Test your connector post certification to provide go-live for deployment- Testing Guidelines
6. If you wish to Update your connector or plugin in future- Updating Guidelines

For any queries or concerns please get in touch with us on [email protected]

Many thanks, Power Platform Copilot connector & plugin certification team

[marcusdelang]

@vmanoharas Thank you for the reply. I have tried following this process but the guide leads me to a dead end in our partner center. I have sent an email to [email protected] describing my problem and I assume it is being looked into.

I expect that it might take some time before we can figure that out, so in the meantime is there any other way I can submit updates to our connector? We have some quite urgent changes and I am currently unable to submit.

One suggestion is that I create a PR to this repo and then it can be deployed by someone in your team? Can we find some solution for this?

[vmanoharas]

Hello @marcusdelang,

Apologies for the inconvenience caused, could you please mention your problem, so that I can take it to the concerned team and provide you the solution.

[marcusdelang]

@vmanoharas Thank you, this is the problem as I described it in the email I sent to [email protected]

The new method to submit connector updates does not work for me. I am trying to follow the instructions here: https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification

Which leads me to this page: https://learn.microsoft.com/en-us/partner-center/marketplace/open-a-developer-account#create-a-partner-center-account-and-enroll-in-the-microsoft-365-and-copilot-program

I then end up on the publishers page where I have my new publisher with access to Microsoft 365 and Copilot:

I then go to the partner center on the correct publisher:

I follow these steps but on step 3 it says I should find Microsoft 365 and Copilot on the marketplace->overview page. But there is no such thing as you can see on the next screenshots.

[vmanoharas]

Hello @marcusdelang,

Please provide the Seller ID of your partner center account which is associated with Microsoft 365 and Copilot program.