126 - Securing Azure Logic App HTTP Triggers with Azure AD 

Great video ... Thanks for sharing this guide

Thanks Kent, that was a really useful video.

Thanks for the great video.

Great video!

Currently it doesnt check if the App Registration has a role or not. I tried creating a 3rd app registration and assigning no permissions to it. The token generated for this new app works to run the logic app.

Hi Kent, Fantastic video, how would differ if one was using APIM in front of it. Being able to access the headers within the logic app would be important to us as we need to see the UPN of the user calling it.

Instead of an application, is it possible to grant individuals permissions in AAD to execute a Logic App via HTTP?

Hi Kent - what is the reason for creating two app registrations? I simply don't understand it. And does this work with all type of external calls (e.g. Salesforce calling, AWS calling, etc. etc.)

i do not see any AD role concept here, when i give roles based , i expect no token required to pass explicitly.

Hi Kent, Thanks very much for the great videos and many congratulations for the new role. I have a usecase where I need to expose certain data to about 200 vendors. I’m wondering if I can use logic apps using above authentication. In that case I’ll need to register all these vendors to setup their credentials. Wondering if this approach is suggested for large number of consumers?

How can we do it for standard logic app?

Can we use azure AD to secure Power Automate Http Triggers?

Hi Kent, your tenantID is visible briefly at 21:58.