Debug Azure API Management Policies | Send-Request APIM Policy | Managed Identity Authentication

📚 Azure API Management's policy engine allows applying transformations to API requests and responses using Liquid templates. However, writing and maintaining complex business logic with Liquid templates can become challenging, especially when dealing with heavy lifting scenarios.

🚀 To address this, we can offload the complex transformation logic to an Azure Function by leveraging the Send-Request APIM Policy. This approach improves code organization, maintainability, and simplifies the APIM policies, making them more readable and manageable.

🔍 Additionally, we'll explore how to debug APIM policies in Visual Studio Code, providing better troubleshooting capabilities.

📹 In this video, you'll learn:

1. ⚙️ Configuring a simple APIM Policy
2. 🐞 Debugging the APIM Policy in Visual Studio Code
3. 🔗 Using the Send-Request APIM Policy with an Azure Function
4. 🔒 Securing the Azure Function with Managed Identity Authentication, all configured within the APIM policy.

Chapters:
00:00 Introduction
02:52 Pre-requisites
03:32 Demo - Debugging Azure API Management Policy in Visual Studio Code
08:42 Demo - Send-request Azure APIM Policy with Azure Function using Managed Identity Authentication

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

Come and say Hi!

[arupmaitra]

Great video to see how we can debug Azure APIM policies. However, I believe any transformation (XML to JSON or vice versa) where business logics are present, should not be in APIM and the best place is orchestrator or Logic App here using either XSLT or Liquid template. This is also a standard approach recommended by Microsoft. Exception for much complex transformation is built Azure Function and invoke it from Logic App instead of invoking from APIM. Thanks.