We have an Azure VM and an Azure file share set up and want to use the file share to store configuration for some COTS applications that run on the VM as services under an Azure AD synced service account.
To acheive this, I beleive the file share needs to be permanently mounted and accessible from the VM, not just for the currently logged in user, but also for the service account that the COTS software is running under.
I have read various posts and have tried several things, including net use commands and powershell (e.g. New-SmbGlobalMapping) in an attempt to permenantly map the file share. However, these only appear to work either within powershell or for the currently logged in user.
This MUST be possible, so can somebody please explain what the best practice way to permanently map an Azure file share on an Azure VM for all users, (including the service account) is?
If mapping the file share as a drive on the VM is not the right solution, please can someone explain what the best practice way to do this is?
The goal is eventually to use the file share across multiple load balanced VMs that all share the same configuration, which is stored on the file share.
Any assistance/experience would be much appreciated.