#3962 [BUG] Azure Workload Identity not working with `fsspec` in `flytekit` Issue created by devictr Describe the bug For workload identity to work within `AzureBlobFileSystem`, the filesystem needs to be instantiated with an account name and `anon` set to `False`. Currently, due to how `get_filesystem()` is set up, we cannot pass the right

kwargs

for Workload Identity to work. The workaround is to set

AZURE_STORAGE_ACCOUNT_NAME

and

AZURE_STORAGE_ACCOUNT_KEY

, which will allow

flytekit

to talk to blob storage, but it would be nice to support Workload Identity directly. This relates to the discussion in #3945 Expected behavior Enabling Azure Workload Identity should work out of the box when

flytekit

tries to read/write to blob storage. Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte