The LinkedIn Series here was helpful:
Implement and manage storage (5-10%)
Configure Azure files
Create Azure file shareSimple process if you've done it before, create a storage account > file share > New File Share.
Use connect to mount the share via CMD / powershell / Linux.
Quota is 5 TiB
Powershell you can create this with the key with the cmdlet New-AzureStorageShare after setting the storage context with New-AzureStorageShare
Create Azure File Sync serviceAzure file sync is a "local" Windows Server copy of the Azure file share.
Configure the service from the Azure portal - Create a new Azure File Sync resource from the marketplace.
Configure the on-premise server - disable IE enhanced security. Install the Azure File Sync Agent. Register the server.
Only local non-removable volumes are supported.
Module is named Az.StorageSync
Server 2012 R2 and above (Standard and DC versions) 2GB of memory is required.
DFS - DFS-N good - DFS-R not unsupported - but recommend replacing with Azure File Sync.
Create Azure sync group
Add a new SyncGroup from the portal. Select a storage account. Select a fileshare. Easy.
Add server endpoint from the cloud console.
Cloud tiering (only hot files on the cloud) has a lot of gothcas (no VSS, limited attributes, no system volume, etc).
.SystemShareInformation folder is used like the System Volume Information folder - no touchy.
Troubleshoot Azure File Sync
Don't remove the server endpoint as this could wipe your data.
Agent install troubleshooting: StorageSyncAgent.msi /l*v Installer.log
Changes can take up to 24 hours to in Azure File Sync.
Portal: Sync or Endpoint HealthServer: Applications and Services Logs\Microsoft\FileSync\Agent\Telemetry event logs.
PDC role needs to be Server 2012 R2+
StorageSync.sys and StorageSyncGuard.sys are the two drivers you need to know.