Hi khlee2021 , thanks for your comments.
It's expected that the account Key of Storage account is not shown in the json file because the account key is very sensitive, we need to keep it private.
In the following command, we need to set the storage account key.
$fileShareConfig = New-Object -TypeName "Microsoft.Azure.Commands.Batch.Models.PSAzureFileShareConfiguration" -ArgumentList @("<Storage-Account-name>", https://<Storage-Account-name>.file.core.windows.net/batchfileshare1, "S", "<Storage-Account-key>", "-o vers=3.0,dir_mode=0777,file_mode=0777,sec=ntlmssp")
My suggestions:
- Double confirm the storage account key is provided correctly.
- Find the log file “fshare-S.log” under /mnt/batch/tasks/fsmounts to check the detailed error messages of the failure.
- Create a new pool without mounting any files, and then manually mount the same Azure File Storage to test the connectivity.