Azure API Management Policy Not Applying to Backend Service Calls in .NET Core
This might be a silly question, but I'm stuck on something that should probably be simple. I've looked through the documentation and I'm still confused about I'm struggling with applying policies in Azure API Management (APIM) that seem to not be functioning as expected when calling my backend .NET Core service. I've created a simple API in Azure API Management that routes requests to a .NET Core 6 Web API. However, when I try to apply a transformation policy to the incoming requests, it doesn’t seem to affect the outgoing requests to my backend. I am using the following policy in my API Management configuration: ```xml <policies> <inbound> <base /> <set-header name="x-custom-header" exists-action="override"> <value>CustomValue</value> </set-header> </inbound> <backend> <base /> </backend> <outbound> <base /> </outbound> </policies> ``` The scenario I'm working with is that the `x-custom-header` does not appear in the headers sent to my backend service. I’ve verified that the policy is correctly attached to the API operation, and I see no errors in the APIM logs or in my .NET Core application logs. I've also tried clearing the cache and redeploying the policies, but nothing changes. In my .NET Core application, I am using the following code to read the headers: ```csharp public async Task<IActionResult> Get() { var customHeader = HttpContext.Request.Headers["x-custom-header"].ToString(); return Ok(new { CustomHeader = customHeader }); } ``` When I invoke the API through APIM, I expect to see `CustomValue` in the output, but it returns `null`. Is there something I might have missed in the configuration, or am I overlooking a specific setting in Azure API Management that could impact header propagation? Any insights would be greatly appreciated! What am I doing wrong? Has anyone else encountered this? I'm on Linux using the latest version of C#.