x-functions-key missing when calling Azure Function from Azure SWA

Mark Dabrowski 0

I have my Azure Functions set to authLevel = 'function'. I'm able to properly pass the x-functions-key in the header when using Postman and get a response from my Azure Function.

However, in my Azure SWA when using fetch and specifying the x-functions-key, it seems to be removed / modified when it reaches the Azure Function.

I have tried adding other customer headers (e.x. x-test-header) and is being properly passed to the Azure function from the SWA.

I noticed in the header received by the Azure Function that there's a x-ms-auth-token. Is x-functions-key being converted to x-ms-auth-token because of the SWA and Azure Function being linked?

Ryan Hill 28,631 Reputation points Microsoft Employee

2024-08-30T22:27:02.68+00:00

Hi @Mark Dabrowski, in referencing this doc, your SWA still needs to pass the function key in the API request. I can't foresee the header value being removed if it's still required, but I've reached out to the product team for further clarification.
Mark Dabrowski 0 Reputation points

2024-09-02T23:16:07.1266667+00:00

Hi Ryan, Thank you for having the product team clarify. I currently am passing the x-functions-key in an HTTP request from the SWA to the Function App. However, in the function app, I don't see that header coming in. Which makes me believe the SWA is somehow removing it or modifying it, because when I do the same request via Postman, the x-functions-key is being passed in properly.
Ryan Hill 28,631 Reputation points Microsoft Employee

2024-09-03T20:09:28.51+00:00

@Mark Dabrowski can you confirm if the token value of x-functions-key is the same as x-ms-auth-token when the request is sent from the SWA? Have observed the header in the middleware prior to function execution?

Share via

x-functions-key missing when calling Azure Function from Azure SWA

Your answer