Forum Discussion
REST API using MS Entra ID App
I think you only need one header parameter, Authorization.
If your token is 12345 then the value you enter in the Authorization header should be Bearer 12345.
Thus, you need to add Bearer in front of the token.
That worked for me with the endpoints I mentioned
You also need to make sure that you gave the app registration permissions to read the required scopes in the API permissions page in the App registration in Azure portal.
I agree there seems to be some contradiction in the documentation regarding whether or not service principal is supported. In my experience, currently service principal authentication doesn't work for the Lakehouse endpoint, but it works for the endpoints I mentioned.
Hello swapnil-saxena ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
Otherwise, will respond back with the more details and we will try to help .
Hi,
So far, I'm not able to get this working for the endpoints that I mentioned in my response. Looking at the expert responses, I'm not sure if this has a definite solution given the limitations of using SPN or any other possible alternatives.
Just to confirm: did any endpoints work?
Btw, I agree support for SPN is needed on all endpoints
Nope. I'm not able to get it working for any of the endpoints, unfortunately. I can get the token generated but further to that all the endpoints bring back the same error message:
"message": "Unable to process the operation due to an error in the request"
