macOS access to Azure Files still has a security tradeoff
macOS devices need access to an Azure File Share in a managed workplace setup. The Macs are managed with Jamf Pro, user identity comes from Entra ID, and Intune is used only as a partner. and Jamf Connect are not in use.
The Azure File Share uses without any on-premises , and the same setup works well on Windows. On macOS, there is no clear path. The plus route exists, but it is still in preview, so it is being avoided for .
The practical question is whether the only generally available option is mounting the share with a through a Jamf Pro script, and whether storing that key as a Jamf Pro script parameter while blocking Keychain caching is the safest workable setup.
Key points
- The setup needs macOS users to access an Azure File Share.
- Jamf Pro manages the Macs, Entra ID handles identity, and Intune is used only for .
- works for Windows but does not give an easy answer for macOS here.
- is avoided because the relevant route is still in preview.
- The fallback being considered is a Jamf Pro script using a while preventing Keychain caching.