FBI Most Wanted (Independent Publisher)

[rwilson504]

---

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.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• [X] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• [X] 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.
• [X] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• [X] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[rwilson504]

[rwilson504]

This has been open since Feb and still hasn't been reviewed, could someone please look at it.

[vmanoharas]

Hellow @rwilson504,

Since this FBI related, there is a discussion going on, please allow us some time.

[rwilson504]

Thank you for the update @vmanoharas, just wanted to make sure it wasn't overlooked since it was taking longer than most of my other ones.

[vmanoharas]

Hello @rwilson504,

After checking this internally, unfortunately, this connector cannot be taken and certified as per policy we are not allowed to have risky connectors to be certified, this is FBI related.

[troystaylor]

I see no reason to disqualify this connector - it is a public API.

CC: @shefaaliP

[rwilson504]

Hello @rwilson504,

After checking this internally, unfortunately, this connector cannot be taken and certified as per policy we are not allowed to have risky connectors to be certified, this is FBI related.

I would really like to understand more how this is risky, as @troystaylor stated it's a public API, also it's put out by a US Government organization.

[rwilson504]

@vmanoharas I hope this message finds you well.

I am writing to follow up on the status and the specific reasons behind the rejection of my custom connector for the FBI Most Wanted API. I understand from the previous discussions that there are concerns regarding the connector being considered "risky" due to its association with the FBI, despite it being a public API provided by a U.S. Government organization.

Given the lengthy duration since my initial submission in February and the recent internal discussions, I am seeking a more detailed explanation of the specific risks and policy concerns that led to the decision not to certify this connector. Understanding these details will help me address any issues and comply with the Power Platform's certification policies.

Moreover, I would like to understand if there are any specific adjustments or additional security measures that could be implemented to align this connector with the certification requirements.

I appreciate your time and consideration in this matter and look forward to your guidance on how we can proceed.

Thank you for your continued support.

Best regards,

Rick Wilson