![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 89%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELC%3C/text%3E%3C/svg%3E)
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
In short - Azure Batch does not support using a storage account with Hierarchical Namespace (i.e. ADLS Gen2) for certain features. According to Microsoft Learn (https://free.blessedness.top/en-us/azure/batch/accounts), you can't use the Application Packages or Azure storage-based virtual file system mount features with Azure Storage accounts configured with firewall rules, or with Hierarchical namespace set to Enabled.
If a storage account has Hierarchical Namespace enabled, certain Batch features are not supported (namely Application Packages and the virtual file system mount). However, a storage account with HNS enabled can still be used for storing input, output, resource files etc., except for those unsupported features.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin