131 - Enabling EasyAuth for Azure Logic Apps (Standard) HTTP Triggers

[@CameronMcKay]

Thanks for the video Kent! I was implementing inbound http triggers in a client without APIM and really needed this feature. This video was invaluable in accomplishing that with detailed step by step instructions and explanations. The post made by the logic app engineer on the AIS blog was helpful, but I needed the additional explanation in this video to really get this working.

[@KentWeare]

Glad it was helpful!

[@MrRogeriorslf]

Man i was starting to feel hopeless about using token auth with STD LAs! Thank you so much!

[@KentWeare]

Glad I could help!

[@jekabsbumbieris]

This was a lifesaver, thank you so much!

[@KentWeare]

Glad it helped!

[@rubenaster2046]

A very important feature IMHO! Would be great to have this officially supported (also by ARM and Terraform) AND to be able to disable the SAS token.

[@RainePy]

Thank you! This was really useful video. Especially finding out those id-values which are needed in the rest-request to update auth config.

[@KentWeare]

Glad it was helpful!

[@abhabaranwal1306]

Thanks for the detailed video Kent. I am facing an issue at the end while making the call to logic app. Though I am passing the token in the request to logic app i am getting the following "401 Unauthorized" error: "code": "DirectApiInvalidAuthorizationScheme", "message": "The provided authorization token is not valid. The request should have a valid authorization header with 'Bearer' scheme." is there any other setup to be done.?

[@TrangMai-yg2cw]

Hi Kent, thanks for your video. Just wonder if you have any special set up in the API permissions? I followed your steps but it said that my token does not have authorization to perform action 'Microsoft.Web/sites/config/write'.

[@bharanidharanm2653]

i am getting the same error as well, did you solve it getting scope added to this 'Microsoft.Web/sites/config/write' in azure ad?

[@vigneshbe89]

Hi kent, is this easy auth available in the portal now(2024 march) instead of api enabling the auth.

[@KentWeare]

I checked in with engineering and this is something that we will be working on but it will be post Build conference so after June we will get started I would estimate.

[@rezcan]

NICE!!! Thanks for accepting to do this for Standard sku. Appreciate it... Speaking of reducing the attack surface, tried the managed identity in the identities array and it worked as well. Perhaps a more secure option than Service Principal and secret?

[@KentWeare]

Good to know about managed identities. I hadn't tried that out but agree that is a good approach

[@E20625]

EasyAuth appears to be...3 round trips.

[@ThomasFlock]

not every time, there is an expiry, so you can run a function once and store it and use that token until the expiry time