Unable to use custom SAS tokens for accessing files from ADLS gen2 storage accounts with hierarchical namespace enabled.

I have some parquet files in abfss://con@sa1.dfs.core.windows.net/folder1/. I generated the User Delegation SAS token with the following permission on 'folder1'

SAS_SIGNED_PERMISSIONS -> "racwdxltmeop"

But when I read from "abfss://con@sa1.dfs.core.windows.net/folder1/"

I get a HTTP 403 error, I believe this happens when ABFSS driver makes use of `getACLStatus` API call to determine whether the storage service has hierarchical namespace enabled or not.

I found a workaround, ie to set fs.azure.account.hns.enabled to true which would skip get ACL API call and as folder level SAS only works for HNS enabled accounts. May I know if this behavior is expected and the workaround I am using is stable for production use and if there are any hidden implications?

Thank you in advance.