When I am running azure HTTP Trigger function i am getting 401 unauthorized
Multi tool use
When I am running azure HTTP Trigger function i am getting 401 unauthorized
I am trying to run Azure HTTP Trigger Azure Function and I am receiving a 401 Unauthorized. It was working fine for me earlier.
401 Unauthorized
When I created the new function under the same Function App and copied the same code then also it is running fine but when I am trying to run my created function then I am getting the same error that I mentioned.
I'm seeing the following logs in the streaming service.
2018-07-02T07:09:41 Welcome, you are now connected to log-streaming service.
2018-07-02T07:09:48.893 [Info] Executing HTTP request: {
"requestId": "53e54698-c46b-4cb6-9ed0-d042eaf9ec71",
"method": "POST",
"uri": "/api/Source/MPAA/false"
}
2018-07-02T07:09:48.893 [Info] Executed HTTP request: {
"requestId": "53e54698-c46b-4cb6-9ed0-d042eaf9ec71",
"method": "POST",
"uri": "/api/Source/MPAA/false",
"authorizationLevel": "Anonymous",
"status": "Unauthorized"
}
@Jan_V I just mentioned in the above description that when I created the new function with same code under the same function app it's working fine.
– Sumit Garg
Jul 2 at 7:30
Have you enabled App Service Authentication/Authorization? Check under Platform Features > Authentication / Authorization.
– Connor McMahon
Jul 2 at 17:41
@ConnorMcMahon when I am enabling Authentication/Authorization and after that when I am trying to run the function again I am getting an error like ( Authentication is enabled for the function app. Disable authentication before running the function )
– Sumit Garg
Jul 3 at 3:42
@ConnorMcMahon Met this problem in v2. Have a httptrigger function created and worked before
2.0.11888 released. After this runtime upgrade, got 401. New created function works fine.– Jerry Liu
Jul 3 at 7:59
2.0.11888
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Can you add some of the code of your Azure Function? This might occur if you're trying to access an external resource for which the Function is unauthorized. Maybe due to some configuration issue (Firewall, security, expired identity, etc.). Are you able to debug the code locally and inspect it?
– Jan_V
Jul 2 at 7:20