"endpoints_resolution_error: Endpoints cannot be resolved" when calling an Azure Function in local development environment only #6684
Labels
bug-unconfirmed
A reported bug that needs to be investigated and confirmed
confidential-client
Issues regarding ConfidentialClientApplications
msal-node
Related to msal-node package
question
Customer is asking for a clarification, use case or information.
Core Library
MSAL Node (@azure/msal-node)
Core Library Version
^2.5.1
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Confidential
Description
Azure Functions, Node.js, v4 programming model.
Calling a local function endpoint in Postman returns this error:
"endpoints_resolution_error: Endpoints cannot be resolved"
Calling the live function endpoint in Postman works as expected with no errors.
I documented this issue in a comment on a closed issue here:
#4879 (comment)
I decided to create a new issue here because I don't think anyone will be looking at a closed issue.
I thought I found a solution yesterday, just requesting a token from my local computer to my tenant via Postman, even though I didn't use it afterwards, seems to have enabled my function code to request a token successfully.
However, 24 hours later, without any changes to the code, I am getting the same error and trying the solution that worked yesterday, ie getting an unrelated token in an unrelated call, is not resolving the issue today.
The function SUCCESSFULLY returns a result IF I comment out the code that requests a token.
As soon as I introduce the code that requests a token, I get the error.
package.json:
Error Message
endpoints_resolution_error: Endpoints cannot be resolved
Msal Logs
No response
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Call the live function endpoint in Postman.
Don't get the error.
Call the local function endpoint in Postman.
Get the error.
Expected Behavior
That I don't get an error.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
None (Server)
Regression
No response
Source
External (Customer)
The text was updated successfully, but these errors were encountered: