Azure Files

Overview

We provision Azure Files shares for workloads that still need SMB or NFS: legacy applications, lift-and-shift VMs, and departments that map a drive. Share size, performance tier, and identity-based authorisation are set from how the share is used, not from a default.

We plan the move from an on-premises file server, including permissions, and we test that mapped drives and backup jobs still behave. Snapshots and Azure Backup are included where the share is a system of record.

What we deliver

• SMB or NFS shares sized for the current file server workload
• Identity-based permissions mapped from the existing share
• Backup or snapshot policy for shares that hold business files
• Cutover plan covering mapped drives, applications, and rollback

Business benefits

• File-share applications move without a rewrite to object storage
• Permissions follow people and groups, not a single admin password
• Restore points exist before the old file server is switched off