Skip to content

Upate apiProperties to add routing policy#4166

Open
krautrocker wants to merge 2 commits intomicrosoft:devfrom
krautrocker:krautrocker-legiscan-policy-update
Open

Upate apiProperties to add routing policy#4166
krautrocker wants to merge 2 commits intomicrosoft:devfrom
krautrocker:krautrocker-legiscan-policy-update

Conversation

@krautrocker
Copy link
Copy Markdown
Contributor


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.

@krautrocker krautrocker requested a review from a team as a code owner March 22, 2026 18:56
@krautrocker
Copy link
Copy Markdown
Contributor Author

krautrocker commented Mar 22, 2026

Repo doesn't seem to have the policy template:

image

Connector on my end:

image

The ConnectorPackage has it though:

image

@vmanoharas

@vmanoharas
Copy link
Copy Markdown
Contributor

Hi @krautrocker,

Could you please elaborate your question?

@krautrocker
Copy link
Copy Markdown
Contributor Author

Hi @krautrocker,

Could you please elaborate your question?

No question. This is an update to the connector. The apiProperties file is/was missing the policy template in order for the connector to route requests properly.

@vmanoharas
Copy link
Copy Markdown
Contributor

Thank you @krautrocker.

Kindly upload the package zip file.

@krautrocker
Copy link
Copy Markdown
Contributor Author

ConnectorPackage.zip

Here you go @vmanoharas

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.

2 participants