Within my orgnaisation we have migrated from on-prem NetApp to Azure Files.  UAT phase was successful for all device/OS types reqiured.  There was a 2/3 week window between the final phase of testing and our go live/migration.

We went live yesterday and had a single report from a Mac user that they could see the file share but it was “empty”.  I jumped on to the share as my domain admin and confirmed data did indeed exist. 

I engaged our Mac team to get on a call with me and the user.  While on the call we established that she was on the latest Mac OS verion (14.5).  The Mac admin was also on the same version and confirmed the same result – share was “empty”.

I had another Mac user working fine and they were on Mac OS 14.3.1.  The Mac admin grabbed a few test Macs on various flavours of OS.  Result is pointing to Mac OS 14.5 being incompatible with Azure Files.  This could be a bug, or by design, I’m not sure at this time.

Highlevel list of testing I have undertaken:

Mac OS 14.5 to Azure Files via DFS – Failed

Mac OS 14.5 to Azure Files via native path – Failed

Mac OS 14.5 to Azure File Sync – Success (appears native Azure Files is part of the issue)

Mac OS 14.5 to vSAN file share – Success

Mac OS 14.5 to NetApp ONTAP – Success

Unfortunately, across the board I cannot offer Azure File Sync to all of our Azure Files storage accounts.  This is due to our vSAN deployment having a smaller data footprint than the Azure Files Storage Accounts combined.

Has anyone else seen similar issues as above?

​Within my orgnaisation we have migrated from on-prem NetApp to Azure Files.  UAT phase was successful for all device/OS types reqiured.  There was a 2/3 week window between the final phase of testing and our go live/migration. We went live yesterday and had a single report from a Mac user that they could see the file share but it was “empty”.  I jumped on to the share as my domain admin and confirmed data did indeed exist.  I engaged our Mac team to get on a call with me and the user.  While on the call we established that she was on the latest Mac OS verion (14.5).  The Mac admin was also on the same version and confirmed the same result – share was “empty”. I had another Mac user working fine and they were on Mac OS 14.3.1.  The Mac admin grabbed a few test Macs on various flavours of OS.  Result is pointing to Mac OS 14.5 being incompatible with Azure Files.  This could be a bug, or by design, I’m not sure at this time. Highlevel list of testing I have undertaken:Mac OS 14.5 to Azure Files via DFS – FailedMac OS 14.5 to Azure Files via native path – FailedMac OS 14.5 to Azure File Sync – Success (appears native Azure Files is part of the issue)Mac OS 14.5 to vSAN file share – SuccessMac OS 14.5 to NetApp ONTAP – Success  Unfortunately, across the board I cannot offer Azure File Sync to all of our Azure Files storage accounts.  This is due to our vSAN deployment having a smaller data footprint than the Azure Files Storage Accounts combined. Has anyone else seen similar issues as above?  Read More

​