I have worked through the basic vs code, github sample and deployed successfully I'm satisfied i understand the concept. Remove the existing publish profile Create a new publish profile and deploy the function app again Enable the basic authentication in azure portal=>function app=>settings=>configuration=>general settings before deploying the function Application settings of my function app
Created a publish profile to zip deploy the function. I am trying to use managed identity to get a connection string from an azure key vault when i run my application locally in visual studio 2022 Note the profile is set to project not executable This allows me to have multiple test profiles With this setup i can run multiple azure functions at the same time in debug in visual studio when i set the solution properties configuration to multiple. I'm attempting to connect to an azure key vault instance from a.net 4.7 application running locally under iis and the debugger (visual studio 2022 17.4.4) but am encountering the below exception(s.
My problem could have originated from having two different azure devops accounts cached in windows credentials and visual studio started choosing which one to authenticate with at random. I am using visual studio professional 2022 and have a free azure devops account linked to my personal microsoft account However, when i connect this account in team explorer it doesn't show me any. A recent change was made to prefer using the windows authentication broker over other authentication mechanisms in visual studio such as the embedded browser or system browser.
OPEN
