Azure Unblogged - Replace your file server with a serverless Azure file share!

I am prototyping a solution for remote users using Azure Guest accounts to access Azure Storage File shares. The prototype has hit a wall with the P2S VPN. The VPN indicates it is connected but the Test-netconnection fails and I can not ping any IPs on the azure side. In your ignite presentation there was a mention of adding an entry to the host file for the IP of the nic of the Private endpoint. Still no luck. The VPN was created using the Scripts located at:  https://docs.microsoft.com/en-us/azure/storage/files/storage-files-configure-p2s-vpn-windows

On another note the Script for the P2S to complete the Client setup fails when you are running it on the machine you are updating. There is contention on the copy step. That being said the process still created the VPN option and connects. 

One last item to note. for those running the client side script I had to turn off IPv6 to get the New-PSSession cmdlet to complete successfully.

Thanks in advance for your assistance 

Testing this over Expressroute, I have noticed it takes a lot of time to render the window where you assign permissions to folders to On-Prem AD groups. Also, the location keeps on flipping between the On-prem Domain name and Storage Account Name. Is this a limitation of the Preview?

Great !!

Christian Echetto, if one of your storage accounts does not have any storage accounts registered, it won't be in your private DNS, so requests will go through to the public DNS automatically.

Stephane Munger I would recommend that you look at Azure File Sync, to replicate data to an Azure Files share, later you can then remove the Sync and remove the on-prem server. You can find this here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deployment-guide?WT.mc_id=itopstalk-blog-thmaure 

Tim67 Thanks for the question, with the AD integration you should already be able to do that. You will basically add the Azure Files Share in the local AD and you can use DFS-N in front of it.

any plans for DFS on-prem pointing to Azure files

It is mentioned to use DNS forwarding for core.windows.net to be able to get the private IP of a share - however, what happens with the storage accounts and anything else under the core.windows.net namespace that we actually need the public IP resolved? Will the private DNS used for this forward the request to the upper Azure DNS to get a public IP?

Example:

fileshare.file.core.windows.net -- resolved to private IP (which is correct)

anotherstgacc.file.core.windows.net -- resolved to a public IP

Thank you

Hello,

Do you have a tools or script for transfert de data and Security from thé old on-promise serveur to azure file share ? (Ex: Azure migrator)

Thanks !