Hello guys,
I’ve posted about a problem I faced when restringing my server into Azure File Sync, the process was failing during the registration for unknown reasons, after a while I’ve found that it’s related to TLS. You can read the full post here
Anyway, I’ve contacted the Azure Files team and they have provided with some information regarding the issue and I want to share it with you.
First, the fix is going to be available with the v7 of the Azure File Sync agent.
Below is the exact reply:
Bassel,
This issue has been fixed in the Azure File Sync v7 release (server registration now uses TLS 1.2). The v7 release should be available by the end of July.
Also they have provided me with a workaround using PowerShell
Bassel,
I forgot to mention you can workaround this issue until v7 releases by using PowerShell to register the server.
Run the following PowerShell command to ensure TLS 1.0 is not used: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12
Then run the following PowerShell command to register the server: Register-AzStorageSyncServer -ResourceGroupName “<your-resource-group-name>” -StorageSyncServiceName “<your-storage-sync-service-name>”
I want to thank Jeff Patterson from Azure File Sync for the his reply and clarification
Be First to Comment