Deliverea connector (Independent Publisher)

[ifrifr]

---

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.

[ifrifr]

@microsoft-github-policy-service agree company="IFR"

[vmanoharas]

Hi @ifrifr,

Could you please confirm that this is a proposal?

[ifrifr]

Hello @vmanoharas, we are a bit confused about the steps on certifying the connector.

We, IFR, have developed the connector for our partner's platform (Deliverea). The connector is fully functional and tested and we are ready to certify it but we need a little bit of guiddance.

[vmanoharas]

Hi @ifrifr,

If you work is for the underlying service, please submit your connector as Verified Publisher connector, otherwise Independent Publisher Connector.

Verified Publisher Connector
https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification

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

[ifrifr]

Hello @vmanoharas as we do not own the service, we are continuing with Independent Publisher Connector.

[vmanoharas]

Hi @ifrifr,

Thanks for the confirmation.

Please refer the below link and submit the package.

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

[ifrifr]

@vmanoharas Everything is ready. Please tell me if it is correct or do I need to change anything.

[vmanoharas]

Hi @ifrifr,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package zip file.

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

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

[ifrifr]

@vmanoharas Those are the steps we tried to follow. What's missing?

[vmanoharas]

Oh... My bad @ifrifr, I have not observed the package zip file in the artifacts.

As a next step, all independent publisher connector author must go through the OneVet verification.

We have sent you MS form to the email address mentioned in the swagger json file contact section to collect the details. Kindly fill the form to proceed for the next step.

[ifrifr]

@vmanoharas I have checked the email and nothing was received. We performed a test and our emails are received. Could you send it again?

[vmanoharas]

Hi @ifrifr,

Shared again from different email, please check.

[ifrifr]

@vmanoharas I'm sorry but we are not receiving anything. Just to confirm that you are sending an email to

What can we do? Is there any other way to start OneVet verification?

[vmanoharas]

Yes @ifrifr we have sent to web@ifr.es email.

Please share if you have different email.

[ifrifr]

@vmanoharas you can send it to ifrgithub@ifr.es or ajimenez@ifr.es

[vmanoharas]

Thank you @ifrifr, shared with the emails.

[ifrifr]

@vmanoharas we completed the registration form as ifrgithub@ifr.es. What's next?

[vmanoharas]

@vmanoharas we completed the registration form as ifrgithub@ifr.es. What's next?

Thank you @ifrifr.

We have initiated OneVet Verification. Kindly complete this process.

[ifrifr]

@vmanoharas Ok, I just have completed OneVet. What is the next step?

[vmanoharas]

Hello @ifrifr,

The verification still show in-progress. Please refer the below document and complete all the steps.

https://learn.microsoft.com/en-us/connectors/custom-connectors/verified-credentials-ip

[ifrifr]

@vmanoharas I believe I missed a step (sharing my credentials). Could you check it again?

[vmanoharas]

Yes @ifrifr, it is completed now. Thank you!

[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

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