I have a Java Azure Function deployed to AKS (Azure Kubernetes Service) with KEDA enabled. The function uses a blob trigger, which works fine when configured with AzureWebJobsStorage set to a storage account connection string using an access key. However, I’m trying to switch to using Managed Identity to access blob storage.

I’ve configured AzureWebJobsStorage with the following connection string format:

DefaultEndpointsProtocol=https;AccountName=your-storage-account;EndpointSuffix=core.windows.net;Authentication=ManagedIdentity

When I deploy, I encounter the following error:

info: Host.Startup[0]
Job host started

fail: Host.Startup[402]
The 'BlobProcessor' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.BlobProcessor'. Microsoft.Azure.WebJobs.Extensions.Storage: Storage account connection string for 'AzureWebJobsStorage' is invalid.

Also tried including this configuration in different ways like below

 - name: AzureWebJobsStorage__serviceUri
   value : "https://your-storage-account.blob.core.windows.net"

 - name: AzureWebJobsStorage__blobServiceUri
   value : "https://your-storage-account.blob.core.windows.net",

non of these methods worked

How can I correctly configure Managed Identity for accessing blob storage in my Java Azure Function deployed to AKS with KEDA?