ADF REST Linked Services Auth Headers are not working

Question

This stackoverflow thread has a good explanation of the same issue I am seeing: https://stackoverflow.com/questions/78948962/adf-rest-linkedservice-is-missing-authheader-in-live-mode-after-publishing/78950885#78950885

I need auth headers to be entered and using Azure Key Vault, but that doesn't appear to be working all of a sudden.

Answer 1

Hello Joseph Lee and Chris Meesters,

The product team has deployed the fix. Please validate and let me know if you are still facing the same issue.

Answer 2

Seems that Microsoft has stated that this is due to a bug in a different post:

https://learn.microsoft.com/en-us/answers/questions/2036344/auzure-synapse-rest-linked-service-doesnt-save-aut

Stating that: "From your screenshot, it appears that you have added the value from Azure Key Vault (AKV).

If this is correct:

The issue is due to a bug, and the product group is working on a fix. However, there is no ETA at this time.

Workaround: You need to remove the AKV until the permanent fix is deployed."

Which is completely useless as far as workarounds go... Eager for MS to fix this issue.

Answer 3

Hello again,

We seem to have figured out a workaround. For some reason, the authorizationHeader value gets put into an encrypted variable upon deployment due to a 'security improvement' that was implemented by Microsoft. However, this only happens when a single auth header value is present. Adding another auth header with a nonsense value allows you to successfully deploy the Rest LS with auth headers intact.

E.g.:

Leads to...

No headers.

But this:

Leads to the Auth headers coming through when publishing/deploying. Still eager for Microsoft to fix this issue, so we don't have to insert nonsense values in our auth headers as a workaround.

Hope this works for your situation as well!