Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

AuthBinder (Independent Publisher)#4204

Open
AuthBinderSimon wants to merge 17 commits into
microsoft:devmicrosoft/PowerPlatformConnectors:devfrom
AuthBinderSimon:devAuthBinderSimon/PowerPlatformConnectors:devCopy head branch name to clipboard
Open

AuthBinder (Independent Publisher)#4204
AuthBinderSimon wants to merge 17 commits into
microsoft:devmicrosoft/PowerPlatformConnectors:devfrom
AuthBinderSimon:devAuthBinderSimon/PowerPlatformConnectors:devCopy head branch name to clipboard

Conversation

@AuthBinderSimon

@AuthBinderSimon AuthBinderSimon commented May 27, 2026

Copy link
Copy Markdown

Connector: AuthBinder (Independent Publisher)

Publisher: AuthBinder
Description: AuthBinder is an AI agent audit platform. Connect your Copilot Studio agents or Power Automate flows to capture tool call telemetry, score behavioural risk, and receive a structured compliance report delivered by a security analyst.
Support email: info@getauthbinder.com
Privacy policy: https://authbinder.com/privacy
Terms of service: https://authbinder.com/terms

Attestations

  • I have validated the swagger file by running paconn validate command
  • This is an independent publisher connector — I am not submitting a connector icon
  • The PR is named after the pattern "Connector Name (Independent Publisher)"
  • apiDefinition.swagger.json included
  • apiProperties.json included
  • README.md included
  • Support email is monitored
  • Privacy policy URL is live
  • Terms of service URL is live
  • Production host URL is used (authbinder-prod-api.azurewebsites.net)

Checklist

  • Screenshots of 3 unique operations working in a Flow — pending Power Automate setup
  • Screenshots of Flow succeeding — pending Power Automate setup
  • Screenshot from Test operations section in Custom Connector UI — pending

@AuthBinderSimon
AuthBinderSimon requested a review from a team as a code owner May 27, 2026 02:30
@AuthBinderSimon

AuthBinderSimon commented May 27, 2026 via email

Copy link
Copy Markdown
Author

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @AuthBinderSimon,

Thank you for your interest to submit Independent Publisher Connector.

Please refer below links.

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

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

@AuthBinderSimon AuthBinderSimon changed the title Add AuthBinder independent publisher connector AuthBinder (Independent Publisher) Jun 3, 2026
@AuthBinderSimon

Copy link
Copy Markdown
Author

Test operation screenshots

Operation 1 — LogAgentEvent (POST /events) — Status 201

Screenshot 2026-06-04 130457

Operation 2 — LogAgentEventsBatch (POST /events/batch) — Status 202

Screenshot 2026-06-04 131139

Operation 3 — GetConnectionStatus (GET /connection-status) — Status 200

Screenshot 2026-06-04 130807

Operation 4 — HealthCheck (GET /health) — Status 200

Screenshot 2026-06-04 130935

All 4 operations tested successfully against the live production API at authbinder-prod-api.azurewebsites.net

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @AuthBinderSimon,

Thank you for your interest to submit Independent Publisher connector with us.

Please go through below links for IP connectors submission process.

Our connector certification process has been changed, kindly follow this link and submit the connector package. https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#step-5-submit-your-connector-for-deployment
Kindly go through this for IP connector certification process - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

@AuthBinderSimon

AuthBinderSimon commented Jun 16, 2026 via email

Copy link
Copy Markdown
Author

@AuthBinderSimon

Copy link
Copy Markdown
Author

Thank you @vmanoharas. I've reviewed the IP certification process.
I understand I need to complete OneVet verification and submit a
package.zip as part of Step 6. I'll work through these steps and
update this PR accordingly. Happy to answer any questions in the meantime.

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — I've reviewed the IP certification process and
OneVet verification requirements. I haven't received the verified
credentials setup email yet. Could you please initiate the process
for @AuthBinderSimon? The email on my GitHub account is ready to receive it.

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — following up on my message from last week.
I'm ready to proceed with OneVet verification but haven't
received the verified credentials setup email yet. Could you
please confirm it has been sent to the email on my GitHub
account, or re-initiate if needed? Happy to move quickly
once I receive it.

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @AuthBinderSimon,

Thank you for following up.

Could you please prepare connector package and upload as part of the artifacts, before start the onevet process.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#step-5-submit-your-connector-for-deployment

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — thank you. I've prepared the connector package
and am ready to upload. Could you please confirm the best way to
attach the package.zip to this PR — I will commit it directly
to the AuthBinder folder in my fork.

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — the connector package and intro.md have now been
uploaded to the PR. The AuthBinder folder now contains:

  • apiDefinition.swagger.json
  • apiProperties.json
  • README.md
  • intro.md
  • authbinder-connector-package.zip

Ready to proceed with OneVet verification when you are.

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — just following up on PR #4204 for the AuthBinder independent publisher connector. Happy to provide any additional information or make any changes needed to progress the review. Let me know if there's anything outstanding on your end. Thanks!

@vmanoharas

Copy link
Copy Markdown
Contributor

Hello @AuthBinderSimon,

Thank you for uploading the package.

We have shared the MS form to fill out the details that need to be used for Onevet Verification. Please fill the form and let us know.

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — the Independent Publisher Registration Form has been completed. Please let me know if you need anything else to progress the review.

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @AuthBinderSimon,

Thank you for submitting the details. We have shared OneVet verification form. Kindly follow the instruction from the below documentation and complete the verification.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — I completed the AU10TIX identity verification
step. Could you please confirm the verified credentials have been
received and let me know the next steps?

@vmanoharas

Copy link
Copy Markdown
Contributor

certify-connector

@certificationteam

Copy link
Copy Markdown
Collaborator

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. Solution package not found at root of the package zip file

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — I've updated the connector package with the
correct solution zip exported from Power Automate. The AuthBinder
folder now contains the updated authbinder-connector-package.zip
alongside apiDefinition.swagger.json, apiProperties.json,
README.md, and intro.md. Please let me know if anything else
is needed.

@vmanoharas

Copy link
Copy Markdown
Contributor

certify-connector

@certificationteam

Copy link
Copy Markdown
Collaborator

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. Solution package not found at root of the package zip file

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — I've rebuilt the connector package with the
correct structure. The package.zip now contains the connector
files at the root level with no subfolders.
All 5 files have been updated in the PR. Please let me know
if anything else is needed.

@vmanoharas

Copy link
Copy Markdown
Contributor

certify-connector

@certificationteam

Copy link
Copy Markdown
Collaborator

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. Solution package not found at root of the package zip file

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @AuthBinderSimon,

Please follow this link and prepare a package as per the below folder structure.

image

@AuthBinderSimon

Copy link
Copy Markdown
Author

Hi @vmanoharas — thank you for your reviews and guidance. As AuthBinder Limited owns the underlying API, we're withdrawing this submission to resubmit through the verified publisher track via Partner Center. Closing this PR accordingly. Thanks again for your time.

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.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.