Skip to main content
This guide shows how to back up files and folders from both Azure File Shares and on‑premises Windows servers using Azure Backup. It covers creating the required storage and Recovery Services vault, enabling Azure Files backup, installing and registering the Microsoft Azure Recovery Services (MARS) agent for on‑premises machines, configuring schedules and retention, and performing restores. Key terms: Azure Backup, Recovery Services vault, Azure Files, MARS agent, file‑level recovery, backup policy, retention, offline seeding.
A diagram titled "File and Folder Backup" showing Azure Files on the left and an On‑Premises environment on the right both connected to a central Recovery Services Vault. The on‑premises side includes a MARS agent and Windows Server, illustrating backup flow to the cloud.
Overview
  • Azure Backup stores metadata and recovery points in a Recovery Services vault. The vault provides a single management interface for multiple workloads (Azure VMs, Azure Files, and on‑premises servers).
  • Azure Files backup is an Azure‑native capability you enable by registering the storage account with a Recovery Services vault.
  • On‑premises Windows servers use the MARS agent to register with the vault and upload protected files and folders.
This article walks through both scenarios: backing up an Azure File Share and backing up on‑premises files/folders using the MARS agent. Summary comparison Creating a storage account and file share (Azure Files)
  • In the Azure portal go to Storage accounts and create a new storage account. Select your subscription and resource group (for example, RSV demo), choose performance and redundancy (example: Standard / LRS), then proceed through the creation wizard.
  • After validation completes, create the storage account. Once deployed, open the storage account and go to File shares. Add a new file share (for example, rsvdemo).
Screenshot of the Microsoft Azure portal on the "Create a storage account" page showing the Basics tab with fields for subscription, resource group, storage account name, region, performance and redundancy. A cursor is clicking the "Next: Advanced >" button at the bottom.
Note: You can enable backup for a file share directly from the Create file share dialog, but this guide demonstrates creating a Recovery Services vault separately and enabling backup from the vault so you see the full workflow.
Screenshot of the Microsoft Azure portal on the "New file share" Backup tab with the "Enable backup" checkbox selected. It shows Recovery Services Vault, vault name, resource group, backup policy and policy details, with a "Review + create" button visible.
  • After the file share is created, browse the share and upload sample files to test backup and recovery (for example, City1.jpg, City2.jpg).
A Microsoft Azure portal screenshot showing an SMB file share named "rsvdemo" with the Browse pane on the left. The right side shows an "Upload files" panel listing uploaded image files (e.g., City1.jpg, City2.jpg, Water10.jpg).
Creating and configuring the Recovery Services vault
  • In the Azure portal go to Recovery Services vaults and create a new vault. Example values: resource group rg-data-protection, vault name rsv-01, Region East US. Review and create the vault.
A screenshot of the Microsoft Azure portal on the "Create Recovery Services vault" page showing the Basics tab with project details (Subscription, Resource group: rg-data-protection) and instance details (Vault name field and Region: East US). The bottom shows action buttons "Review + create" and "Next: Vault properties."
The Recovery Services vault is the central resource for managing backups and recovery points across workloads. One vault can manage backups for multiple services (Azure Files, VMs, and registered on‑premises servers).
Enabling backup for the Azure File Share
  • Open the vault and choose Backup. Select where the workload runs (Azure) and select File share as the workload type. The wizard asks you to pick the storage account that contains the file share. Selecting the storage account registers it with the vault and registers the provider — this can take a short time.
  • After the provider is registered, add the file share to the vault, pick a backup policy (schedule and retention), and enable backup. You can customize schedules (daily/weekly/monthly/yearly) and retention ranges. The default policy retains daily recovery points for 30 days.
Screenshot of the Microsoft Azure portal on the "Configure backup" page for a Recovery Services vault (rsv-01), showing storage account "imgfilessharedemo", a file share "rsvdemo", and backup policy details. A blue "Enable backup" button is visible at the bottom.
  • Example configuration: set a daily backup at 7:30 PM (UTC) and retain daily recovery points for 30 days. Save the policy and click Enable Backup.
Screenshot of the Microsoft Azure portal showing Configure backup and Create policy panels for an Azure File Share. The policy is set to run daily at 7:30 PM (UTC) with daily backups retained for 30 days.
  • After enabling backup, go to Backup Items in the vault to monitor the protected file share. Trigger an initial backup with Back up now if you want to create the first recovery point immediately.
A Microsoft Azure portal screenshot showing the "Backup Items (Azure Storage (Azure Files))" page with one listed item (rsvdemo) under storage account imgfilessharedemo and resource group rg-data-protection. The item's last backup status is "Success" with a latest restore point timestamp.
Restoring files from an Azure File Share backup
  • Once recovery points exist you can restore the entire share or perform file‑level recovery. In the vault open the backup item, select Restore, choose a recovery point, and pick either original or alternate restore location.
  • For file‑level recovery, choose the files/folders to restore and start the restore operation. Restored files will appear in the target file share location after the job completes.
Backing up on‑premises files and folders with the MARS agent
  • In the vault Backup workflow select On‑premises and choose Files and folders. Click Prepare infrastructure to download the MARS agent installer and the vault credentials file. Copy both to the server you want to protect.
The vault credentials file is time‑limited. Download it just before registering the server — the file typically expires after a short window (for example, 48 hours).
  • On the target Windows Server run the MARS agent installer. During registration browse to the vault credentials file to link the server with the vault. You’ll be prompted to create an encryption passphrase — this passphrase encrypts backups and is required for any future restore. Use a strong passphrase (at least 16 characters) and store it securely, because lost keys cannot be recovered by Microsoft.
A screenshot of the Microsoft Azure portal with a Windows Server Manager window open, showing the "Register Server Wizard" on the "Encryption Setting" step for entering and confirming a backup passphrase. The left side shows Azure Recovery Services instructions and a Download button for the Recovery Services agent.
  • After successful registration, open the Microsoft Azure Backup app installed on the server. Use it to select files and folders to protect (for example, C:\Users\Administrator\Documents). Add exclusions if needed.
Scheduling and initial backup
  • Configure the backup schedule in the Schedule Backup Wizard. You can configure up to three backups per day and set the retention policy to meet your business requirements.
A screenshot of the Microsoft Azure portal with a "Schedule Backup Wizard" dialog from Microsoft Azure Backup open. The wizard shows options to specify a backup schedule for files and folders (daily/weekly) with a time set to 7:30 PM.
  • For the initial backup you can choose an online transfer (over the network) or use offline seeding for very large datasets. Offline seeding options include Azure Data Box or shipping your own disks to speed up the first recovery point creation.
A screenshot of the Microsoft Azure portal showing the "Schedule Backup Wizard" window for choosing an initial backup type (Files and Folders), with options for online transfer or offline seeding using Azure Data Box or own disks.
  • Save the schedule and start the initial backup using Back Up Now. Monitor progress in the Microsoft Azure Backup app on the server or from the Recovery Services vault. If a job fails due to network or configuration issues, review the error, fix the cause, and retry the job.
Monitoring and restoring on‑premises files and folders
  • In the Recovery Services vault, under Backup Items you will see the registered server and available recovery points. Each backup item shows the last backup status and the number of recovery points.
A screenshot of the Microsoft Azure portal showing a backup item for C:\ on a Windows machine (win-bkbran4psd9), with details like recovery services vault, computer name, and item type. The Monitoring pane shows recovery points and a "Last backup status: Success" with timestamps.
  • To restore, open the Microsoft Azure Backup app on the protected server and run the Recover Data wizard. Select the server, recovery location (Primary Region or alternate), and the recovery mode: individual files/folders, full volume, or system state. Choose a recovery point and mount it — mounting exposes the recovery point as a temporary drive letter on the server.
A screenshot of the Microsoft Azure Backup Recovery Data Wizard open on a Windows desktop, showing the "Select Recovery Location" step with "Primary Region" selected and the cursor over the Next button. The Azure portal and backup item details are visible behind the wizard window.
  • After mounting, browse the mounted volume with File Explorer, copy the required files back to their original or alternate locations, then unmount the recovery volume when finished.
A screenshot of the Microsoft Azure Backup interface with the Recover Data Wizard "Browse And Recover Files" dialog open, showing recovery volume details and mount status. The Azure portal backup item page and backup actions (Browse, Unmount, Back Up Now) are visible in the background.
  • Use the mounted drive to drag-and-drop recovered files (for example, copy City1.jpg and City2.jpg back into Documents). When finished, unmount the recovery session.
A screenshot of the Microsoft Azure portal showing an Azure Backup / Recover Data Wizard window. In front is a Windows File Explorer listing user Documents with several image files (City1–City8 and Colour1–...) selected.
Best practices and tips
  • Use a centralized Recovery Services vault per region to simplify management and reduce overhead.
  • Choose retention policies that meet compliance and business continuity requirements while balancing storage costs.
  • Keep the encryption passphrase safe; without it you cannot restore encrypted backups.
  • For large initial data sets, consider offline seeding (Azure Data Box) to reduce network transfer times and cost.
  • Monitor backup job history regularly and set up alerts for failed jobs.
Conclusion
  • Azure Backup with a Recovery Services vault provides a consistent, managed solution to protect Azure File Shares and on‑premises Windows files/folders.
  • Azure Files backup is configured by registering the storage account with the vault and selecting file shares to protect.
  • On‑premises systems are protected by registering servers with the vault using the MARS agent and configuring backup schedules and retention.
  • Restores support file‑level recovery, share‑level restore (Azure Files), volume recovery, and system state recovery depending on the protected workload.
Links and references

Watch Video