Hello Raphael Silva,
One possible solution is to use the forward-request policy instead of set-header. The forward-request policy allows you to forward the entire incoming request, including all headers (such as the Authorization token), directly to the backend service. Here’s an example of how you can use the forward-request policy: <forward-request />
By using the forward-request policy, you can pass the entire request—including the authorization token—onto the backend for further validation and logging purposes.
Make sure the forward-request policy is placed in the inbound section of your API Management policy configuration.
If you encounter any issues or need further assistance with this approach, feel free to let me know. It would also be helpful if you could share any specific error messages or details you're encountering so I can provide a more targeted solution.