Enable custom domains for Azure Files
It would be convenient if custom domains were also supported for Azure Files.
Andrew Iles commented
or if it can also trust connections from the SMB path storage.privatelink.file.core.windows.net at the moment the only way I can connect is by using storage.file.core.windows.net.
Has there been any update to this? Is there no solution to be able to use short names for Azure files instead of having to use the FQDN to access the file share?
Bühler Silvan commented
It would be great, if Azure File Shares would support the use of local CNAME for ADDS authentication. Currently, if we create a CNAME locally (for example share.contoso.local), point it to the Azure File Share (share.file.core.windows.net) and try to access a file share (\\share.contoso.local\share) we get an error when using ADDS authentication. With a storage key it works but this is not practicable for all users.
We are unable to create a CNAME in our on-prem DNS to point to an existing Azure file share e.g <storageaccount>.file.core.windows.net\<shared folder>. This can be done on blobs/containers, but not file shares.
Renato Martins commented
It would be interesting to have a single FQDN for accessing the file share, accessing the local servers when I'm in the corp network, and the cloud files when I'm outside the corp network.
Maybe something along the lines of having some kind of split-DNS, where the corp DNS servers would resolve StorageAccount.file.core.windows.net to an internal server.
The goal is to have local access while logged in to my corp network, and cloud access while away from the office, in a transparent way (i.e. same network drive).
Ayan Mullick commented
The Premium file share storage account should support Azure FireWall integration and custom domain names' with internally-issued SSL certificate support.