You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup new function app on container app using system assigned managed identity
Set AzureWebJobsStorage__accountName as described in here
Deploy container image
Expected behavior
The class DiagnosticEventTableStorageRepository should work in combination with system assigned managed identities.
Actual behavior
The container app fails to start with the following error:
The Azure Storage connection string is either empty or invalid. Unable to record diagnostic events, so the diagnostic logging service is being stopped.
Value cannot be null. (Parameter 'connectionString') at Azure.Data.Tables.TableServiceClient..ctor(String connectionString,TableClientOptions options) at Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.DiagnosticEventTableStorageRepository.get_TableClient() at /src/azure-functions-host/src/WebJobs.Script.WebHost/Diagnostics/DiagnosticEventTableStorageRepository.cs : 69
Related information
Using mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated8.0 as a base image.
I am having a similar issue with my Azure Function App. I am using a 'user-assigned-identity' (UAI) to access the 'working storage account' (WSA).
The UAI has been granted RBAC perms on the WSA...
"Storage Blob Data Contributor", "Storage Queue Data Contributor", "Storage Account Contributor", "Storage Blob Data Owner", "Storage Table Data Contributor"
Hey @DavidVollmers , thank you for providing the detailed information.
Support for identity-based connections will be included in the next release (PR: #10438). That said, this issue shouldn't cause the function app to fail to start. Are you observing a start failure, or is this just being logged during initialization?
Investigative information
Please provide the following:
Repro steps
AzureWebJobsStorage__accountName
as described in hereExpected behavior
The class
DiagnosticEventTableStorageRepository
should work in combination with system assigned managed identities.Actual behavior
The container app fails to start with the following error:
Related information
Using
mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated8.0
as a base image.Package and Framework references:
The text was updated successfully, but these errors were encountered: