Skip to content

Conversation

@varunynoox
Copy link
Contributor

@varunynoox varunynoox commented Nov 14, 2024


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.

varunynoox and others added 30 commits November 24, 2021 11:13
Merge from microsoft/PowerPlatformConnectors dev
Merge from powerplatform
merge from PowerPlatform
merge from PowerPlatform
merge from powerautomate
@varunynoox varunynoox requested a review from a team as a code owner November 14, 2024 09:56
@vmanoharas
Copy link
Contributor

Hello @varunynoox,

can you please confirm that existing flows will not break from the swagger validation errors below?

The type format has been changed for the input field. Existing flows will continue to send the field with the old type format. ValuePath: operation/AddAttachmentToPdf_v1/parameter/body/schema/document/Name/format Source: NewSwagger

The type format has been changed for the input field. Existing flows will continue to send the field with the old type format. ValuePath: operation/AddAttachmentToPdf_v1/parameter/body/schema/attachments/items/docContent/format Source: NewSwagger

@varunynoox
Copy link
Contributor Author

The existing flow will not break. They are not working as required hence the change.

@vmanoharas
Copy link
Contributor

The existing flow will not break. They are not working as required hence the change.

Thank you for the confirmation!

Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 & Plugins. Read the blog here- Announcing Partner Center to certify and publish Power Platform Copilot Connectors and Plugins - Microsoft Power Platform Blog

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. Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
  4. Initiate a certification request in Partner Center- Verified publisher certification process
  5. Ensure your connector & plugin files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
  6. Test your connector post certification to provide go-live for deployment- Testing Guidelines
  7. 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 certificationteam@microsoft.com

Many thanks,
Power Platform
Copilot connector & plugin certification team

@vmanoharas vmanoharas merged commit ca02b71 into microsoft:dev Nov 22, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants