Unable to update the Functions Extensions Version

[tnlthanzeel]

hi, im have been deploying azure functions from visual studio 2019 for a long time. but today im having an issue after publishing from visual studio. i updated the visual studio this morning to version 16.6.0.

the issue is

Unable to update the Functions Extensions Version in Azure Application Settings because you may not be signed into Visual Studio with the appropriate Azure subscription. See https://go.microsoft.com/fwlink/?LinkId=2071272&CLCID=0x1033 for more information.

[codermrrob]

Same issue - never any problem publishing Azure Functions but this morning :

Unable to update the Functions Extensions Version in Azure Application Settings because you may not be signed into Visual Studio with the appropriate Azure subscription.

I am signed in, of course, with my company account. To get around this error I had to sign in with VS using my clients Azure account.

I never before had to sign into VS with my clients Azure account credentials in order to publish to a clients subscription. Then after publishing I must sign in with my company account again to continue working.

I already provided credentials in the publish profile, and never before needed to change credentials in order to publish. Why now?

[tnlthanzeel]

any update on this issue?

[lpperras]

I have the same issue when importing a publishing profile, even if this profile is from the Azure subscription I'm logged in in VS. I tried logging out many times.

I can also see everything in the cloud explorer.

[razdavidovich]

I have the same issue with latest VS2019

[v-bbalaiagar]

Hi @razdavidovich, Apologies for the delayed response, the issue was somehow lost in the trace. We will check for the possibilities internally and update you with the findings.

[vijayrkn]

The reason you are seeing this error is because VS does the following 2 things as part of the publish process:

1. Push the required deployment artifacts to the target destination (Azure in this case). This does not need the user id to be logged into VS since the publishing creds are all we need to push the artifacts.
2. Set the required app settings correctly on the Azure functions instance. This requires the userid to be logged in that contains access to the Azure resource where the artifacts are pushed to.

If you are manually handling step (2), then you can set the following msbuild property in the csproj to bypass step(2).

<PropertyGroup>
<DisableFunctionExtensionVersionUpdate>true</DisableFunctionExtensionVersionUpdate>
</PropertyGroup>

If you are setting this property, please make sure that the Functions instance is correctly updated with all the required settings for the app to run successfully.

Hope this helps.

[v-bbalaiagar]

Hi @razdavidovich / @lpperras , Let us know if the above information resolves your query, or if you have any further queries.

[Bengkel]

Same issue here. Above information does not resolve the issue.

[v-bbalaiagar]

Tagging @vijayrkn , for further inputs

[warpdriv]

Just started with me too. VS 2022 (community), trying to publish a v4 function. I used the profile from the portal. No luck.

[papadeltasierra]

Hitting this with latest VS 2022, v17.3.2

[sengiv]

The reason you are seeing this error is because VS does the following 2 things as part of the publish process:

1. Push the required deployment artifacts to the target destination (Azure in this case). This does not need the user id to be logged into VS since the publishing creds are all we need to push the artifacts.
2. Set the required app settings correctly on the Azure functions instance. This requires the userid to be logged in that contains access to the Azure resource where the artifacts are pushed to.

If you are manually handling step (2), then you can set the following msbuild property in the csproj to bypass step(2).

<PropertyGroup>
<DisableFunctionExtensionVersionUpdate>true</DisableFunctionExtensionVersionUpdate>
</PropertyGroup>

If you are setting this property, please make sure that the Functions instance is correctly updated with all the required settings for the app to run successfully.

Hope this helps.

@vijayrkn nice & simple solution This has been tested working in VS 17.4.0 Preview 3.0

Another temporary hack that worked, was sign out of Visual Studio, and sign in back, works for awhile.

[hariharan228]

I faced the same issue while using VS2022. None of the above solutions worked for me. Later I found out that my azure account has been logged out while creating a new publish profile. After reentering the credentials that error text was gone.

[lwyj123]

Solution

After "re-enter your credentials" in Visual Studio account setting. I solve the problem.