If I understand this correctly, you won't be able to? The article appears to be referring to Azure domain joined machines, not on-prem machines. Your AzureAD would need a path to get to the on prem machine. That's going to be the issue..
If there is an available path, then it should be possible. The authentication mechanisms are similar enough between a domain authentication and a local authentication. When you authenticate to the local machine, you send the credentials to the local security manager (lsass) instead of the domain. You would supply the credentials as <machinename>\accountname. The machinename becomes the domain.
In the AzureAD situation, the machine is reaching out to Azure to initiate the authentication, and I don't *think* there is a path in the other direction. (I'm not an Azure expert by any stretch). As a sort of example - when you run Citrix Cloud, you install a Cloud Connector service on premises, so you can authenticate to the on prem resources. I don't think AzureAD has anything like that? The main thing is the "client" in this situation must have access to the initiate the connection to the "server".
You can potentially add an NFS share to the same directory.
Coralon