Unanswered

Azure DevOps Pull Request Trigger - How can I trigger it for all repositories in a project?

(2) Share

Report

Posted on by SamHunt2002

Hi all,

I am upgrading from our old O365 connector to Power Automate / Flow as it is being deprecated. Right now I am working on the workflow where when a pull request is opened in Azure Dev Ops, a message is posted on our teams channel.

I want this to be triggered any time there is a new PR in the project, regardless of repository. This is so we don't have a super big flow, or have to update it every time a new repo is added to our project.

How do I achieve this?

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Expiscornovus 33,970 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SamHunt2002,

If you want to trigger it from any repo in your project I would suggest to look into using a Servicehook in the Project configuration of your DevOps projects instead of using the When a Pull request is created trigger action.

With a Servicehook you can trigger it from any repo. You can use a HTTP web hook and POST to a When a HTTP is received trigger action of a cloud flow.

In this thread I shared this approach:

https://powerusers.microsoft.com/t5/Building-Flows/Azure-DevOps-queue-a-new-build-status/m-p/1681910

And @Jondoesflow has also written a blog about that approach as well:

https://www.jondoesflow.com/post/service-hooks-for-azure-devops-http-request-in-power-automate

Was this reply helpful? Yes No
SamHunt2002 6 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks for this!

Although I am now running into the issue where the only way I can avoid a 401 is if I set it so anyone can access the link, which is a big security issue.

I've seen that the HTTP Trigger needs OAuth, but DevOps Webhooks only support basic? Is there a way to make this more secure?

Was this reply helpful? Yes No
Expiscornovus 33,970 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SamHunt2002,

You can still check your own properties in the request, this could make it a bit more secure.

@Paulie78 has shared a blog about this approach: https://www.tachytelic.net/2020/09/secure-http-request-power-automate/

Was this reply helpful? Yes No
SamHunt2002 6 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks for your help on this.

Our team still think this is not great practice, because we're exposing a password in our API call. If someone got hold of that they could still remotely send messages and cause issues.

Hopefullly Microsoft intends to improve security around this ahead of our O365 connectors being deprecated.

Thank you again for all your help though 🙂

Was this reply helpful? Yes No
Expiscornovus 33,970 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SamHunt2002,

This was just an example to check for properties from the request. You can also check things like User-Agent, Client-IP which are located in the headers of the request instead by using a similar approach.

Was this reply helpful? Yes No