Cannot publish when identity-based storage connection is used (AzureWebJobsStorage__accountName)

[obesser]

The issue is described in #2671 but the conversation there is locked. It is also marked as fixed in #3306 but it isn't.

When attempting a remote build, I get Azure Functions Core Tools does not support this deployment path. There is an exact name match for AzureWebJobsStorage instead of prefix match:

https://github.com/Azure/azure-functions-core-tools/blob/eb2d8a509b340948009dc2ea0c765eca228f2639/src/Azure.Functions.Cli/Actions/AzureActions/PublishFunctionAppAction.cs#L281-L284

[aelij]

I would also suggest migrating away from the deprecated package WindowsAzure.Storage which hasn't been updated since 2018. With the latest package Azure.Storage.Blobs you can use DefaultAzureCredential to authenticate.

[benedikt-mue]

@aelij any updates on this issue?

[aelij]

I'm not on the Azure Functions team

[rosh2020]

Any update on this?

[christian-vorhemus]

Same problem here. I have disabled local (key based) authentication on der storage account (which is widely recognized as the more secure setting) used by my Azure Function and even when AzureWebJobsStorage__accountName is set in the function app, publishing with func azure functionapp publish <name> (func tools version 4.1.0) fails with "Azure Functions Core Tools does not support this deployment path. Please configure the app to deploy from a remote package using the steps here: https://aka.ms/deployfromurl"