Secure HTTP Trigger Logic Apps with Microsoft Entra ID (Azure Active Directory - AD) Authentication

:🔐 Still using SAS tokens to secure your HTTP-triggered Consumption Logic Apps? That might be a problem.

SAS tokens are convenient but come with risks — they're embedded in URLs, can easily be exposed in logs, browser history, or shared accidentally. And once shared, they grant full access until explicitly revoked.

A more secure alternative is using Microsoft Entra ID (formerly Azure AD) to protect your Logic App endpoints with proper identity-based authentication and authorization.

✅ But here’s something many miss:
Enabling Entra ID doesn’t automatically block SAS token access. Your Logic App can still be invoked using the original SAS URL.

In this video, I will walk you through how to secure your HTTP-triggered Azure Logic App using Azure Entra ID (formerly known as Azure Active Directory - Azure AD) authentication.

What you’ll learn:
✅ How to configure Microsoft Entra ID (Azure Active Directory - AD) authentication for Logic App HTTP triggers.
✅ How to enforce Microsoft Entra ID (Azure Active Directory - AD) Authentication

chapters:
00:00 Introduction
02:30 Register and Configure Client App in Entra ID
03:30 Register and Configure Service App in Entra ID
07:30 Add Azure Active Directly Authorization
08:35 Testing & Conclusion

Engage & Support: Found this video helpful? Like, comment, and subscribe for more in-depth Azure tutorials. Please share it with your network and help spread the knowledge!

Come and say Hi!
🌏 My Blog - https://srigunnala.com/
✅ LinkedIn -   / srikanthgunnala  
☕Say Thank You! - https://www.buymeacoffee.com/srigunnala