`Server failed to authenticate the request.` when connecting to Azure storage

I'm hitting the following error when attempting to use my identity to acces a task hub:

[2025-07-31T09:30:12.080Z] Executing 'DfmGetOrchestrationsFunction' (Reason='This function was programmatically called via the host APIs.', Id=986c8755-ea41-436c-913e-485f86fa7639)
[2025-07-31T09:30:12.276Z] DFM failed
[2025-07-31T09:30:12.276Z] DurableTask.AzureStorage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. Microsoft.WindowsAzure.Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
[2025-07-31T09:30:12.277Z] Executed 'DfmGetOrchestrationsFunction' (Succeeded, Id=986c8755-ea41-436c-913e-485f86fa7639, Duration=197ms)

With the following setting:

    "durableFunctionsMonitor.taskHubsDiscoveryMode": "Do not use Storage keys"

As a test, on the same environment, i installed the Azure Storage Explorer (standalone) https://azure.microsoft.com/en-us/products/storage/storage-explorer. Accessing the storage account (and the content of tables/blobs/queues) with identity works just fine there.

In the same environment with a personal account (pointing to a personal tenant), using the monitor via VS Code, works just fine.

I think Microsoft.WindowsAzure.Storage (which is marked as legacy btw) isn't supported in my work tenant.

Any way around this? Or to debug further?

Start by reproducing the authentication failure with durableFunctionsMonitor.taskHubsDiscoveryMode set to "Do not use Storage keys" in the reported work-tenant environment. Compare this with the successful Storage Explorer and personal-tenant cases, then trace the DurableFunctionsMonitor storage access path. Done means documenting a confirmed cause and an actionable workaround or fix.