🛡️ Essential 8 Guide

Implementation guidance for Australian Essential Eight controls in Microsoft environments - ISM controls with PSPF mappings

About
HOME ← ISM-1808
ISM-1811 →

Backups of data, applications and settings are synchronised to enable restoration to a common point in time.

Property Value
ISM Control ISM-1810
Revision 1
Updated Dec-23
Guideline Not provided
Section Data backup and restoration
Topic Performing and retaining backups
Essential Eight ML1, ML2, ML3
PSPF Levels NC, OS, P, S, TS

Summary

Backups of data, applications and settings are synchronized to enable restoration to a common point in time, supporting consistent recovery after data loss or disruption. Implement this requirement using Azure Backup to take application-consistent snapshots for synchronised restore points.1[^9]

Justification

A synchronised restore point is critical for recovery because:

Recovery Point Objective (RPO) guidance:

Data tier Recommended backup frequency Azure Backup feature
Critical databases (SQL, Exchange) Every hour Hourly log backups + full/differential policy
Standard server data Daily with weekly full Standard policy
User device data (OneDrive KFM) Near-continuous (5-minute sync) OneDrive Known Folder Move + Microsoft 365 Backup / OneDrive versioning

Test restore procedures at least quarterly to validate that the backup is restorable and that the synchronised restore point is usable across all dependent services.

Design Decision

[!NOTE] The Azure Backup service will be used to take application-consistent snapshots for synchronised restore points. This approach will be aligned with the control description to enable restoration to a common point in time.

Prerequisites

Implementation Steps

Use Azure Backup for application-consistent snapshots

  1. Enable Azure Backup on all supported resources (VMs, SQL Server, Azure Files, and Azure Disks) to capture application-consistent snapshots for Windows workloads and file-system backups for Linux, aligning with business requirements.[^9]

  2. Configure backup frequency and retention to support synchronised restore points; set hourly backups for high-churn data and longer retention per compliance requirements.[^9]

  3. Enable instant restore capability for Windows backups to allow rapid recovery from snapshot-based restore points.[^9]

  4. Configure backup windows to minimize performance impact and ensure backups complete before the next cycle.[^9]

  5. For Azure Arc-enabled SQL Server deployments, configure backups at the instance level to cover all databases; if you also configure database-level backups, note that database-level settings take precedence over instance-level settings.2

  6. Validate that backups create a common point in time across resources to enable restoration to a synchronised restore point. Where applicable, test restoration as part of disaster recovery exercises.1[^9]

[!NOTE] This approach aligns with guideline requirements for synchronised backups and restores across data, applications, and settings. 1

OneDrive Known Folder Move (KFM) — Workstation Data and Settings Backup

For workstations, the primary mechanism for backing up user data, desktop content, and application settings is OneDrive Known Folder Move (KFM), also called Folder Backup. KFM silently redirects and syncs three Windows known folders — Desktop, Documents, and Pictures (including Screenshots and Camera Roll) — to the user’s OneDrive for Business storage in near real-time.

Why KFM satisfies the synchronised restore point requirement:

Capability Detail
Sync RPO ~5 minutes; files are continuously synced as they are saved — effectively an active/active backup
Versioning OneDrive retains up to 500 versions per file by default; version history is accessible from File Explorer or the web
Files Restore (Point-in-Time) The OneDrive Files Restore feature allows a user or admin to roll back an entire OneDrive or document library to any point in the last 30 days
Recycle Bin retention Deleted files are retained for 93 days in the first- and second-stage recycle bins before permanent deletion
Ransomware recovery Files Restore can roll back all affected files to a pre-encryption point in time; OneDrive detects ransomware activity and prompts users to restore
Cross-device portability When a user signs in on a new device, KFM files are immediately available from OneDrive before any large sync; critical for device failure or replacement scenarios

Microsoft Purview retention policies on KFM files:

Files stored in OneDrive for Business (including KFM-synced folders) can have Microsoft Purview retention policies and retention labels applied. When a retention policy is active:3

Deploying KFM via Intune (Settings Catalog):

  1. In the Microsoft Intune admin center, navigate to Devices > Configuration profiles > Create profile.
  2. Select Platform: Windows 10 and later, Profile type: Settings catalog.
  3. Search for the OneDrive category and add the following settings:4
    • Silently move Windows known folders to OneDrive (KFMSilentOptIn) — set to Enabled; enable sub-settings for Desktop, Documents, and Pictures.
    • Prevent users from redirecting their Windows known folders to their PC (KFMBlockOptOut) — set to Enabled (locks KFM on; prevents users from redirecting back to local disk).
  4. Provide your Tenant ID in the KFMSilentOptIn setting.
  5. Assign the profile to the device group covering all workstations.

[!NOTE] KFM does not backup application install data or application settings stored outside the known folders (e.g., %AppData%, %ProgramData%). For full application settings backup on workstations, supplement with Windows Backup for Organisations (via Intune Settings Catalog) or, for VDI environments, FSLogix Profile Containers (see below).

FSLogix Profile Container Backup — VDI and Azure Virtual Desktop Environments

For Azure Virtual Desktop (AVD) and traditional VDI environments, user profiles (Desktop, AppData, application settings, browser state, Outlook cache) are stored in FSLogix Profile Containers — VHD/VHDX files mounted at login from Azure Files or Azure NetApp Files shares. Backing up these containers provides a synchronised restore point for the full application and settings layer.

Recommended backup architecture:5

Storage backend Backup mechanism Notes
Azure Files (Standard or Premium) Azure Backup — snapshot and/or vault-standard tier Snapshot tier: instant, low-cost; Vault tier: cross-region, ransomware-resistant, long retention
Azure NetApp Files Azure NetApp Files snapshots + ANF Backup Built-in snapshot policy; backup transfers to Azure Blob for long-term retention

[!IMPORTANT] If OneDrive KFM is deployed for AVD users, files in the known folders are backed up independently via OneDrive — meaning the FSLogix profile container only needs to protect the application settings and AppData portion (not user documents). This significantly reduces the backup size and can allow use of a separate, less expensive backup frequency for the Office Data Folder Container (ODFC) which holds cached Teams/Outlook data that can be rebuilt from Exchange Online.5

Steps to configure Azure Backup for FSLogix profile containers on Azure Files:6

  1. In the Azure portal, create or open a Recovery Services vault in the same region as your Azure Files storage account.
  2. In the vault, select Backup > Azure Files (Azure Storage) as the workload.
  3. Select the storage account hosting the FSLogix profile share.
  4. Create a backup policy specifying:
    • Backup tier: Snapshot (daily) for rapid recovery; optionally Vault-Standard for long-term / cross-region retention.
    • Schedule: Daily at a time when no active user sessions are open (e.g., 2:00 AM).
    • Retention: Configure daily, weekly, monthly and yearly retention to match organisational requirements.
  5. Select the file share(s) containing FSLogix containers and confirm protection.
  6. To restore: navigate to Protected items > Azure Storage (Azure Files) > select the share > File Recovery (item-level, for individual VHD/VHDX files) or Restore Share (full share restoration to original or alternate location).

Microsoft 365 Backup for OneDrive for Business

Microsoft 365 Backup is a first-party backup-and-restore service for OneDrive for Business, SharePoint Online, and Exchange Online managed from the Microsoft 365 admin center. It provides fast, admin-managed point-in-time restore with an RPO of 10 minutes for the most recent 14 days, making it the most granular backup available for user data stored in OneDrive.

Recovery Point Objective (RPO) by age:7

Restore point age OneDrive for Business RPO
0–14 days in the past 10 minutes
15–365 days in the past 1 week

Key capabilities:

Steps to configure and restore OneDrive accounts with Microsoft 365 Backup:87

  1. In the Microsoft 365 admin center, navigate to Settings > Microsoft 365 Backup.
  2. Enable OneDrive backup and select the accounts to protect (individual accounts or all accounts).
  3. Microsoft 365 Backup begins capturing restore points automatically at 10-minute intervals for the first 14 days.
  4. To restore a full OneDrive account:
    • On the Microsoft 365 Backup page, in the OneDrive section, select Restore.
    • Select the account(s) to restore and select the date and time to restore from. Choose an express restore point for fastest recovery.
    • Choose the restore destination: Replace accounts with backups (in-place overwrite) or Create new SharePoint sites and restore to them (new URL — recommended for ransomware recovery to avoid overwriting currently healthy data).
    • Review and select Restore OneDrive accounts.
  5. To restore specific files or folders (granular restore):
    • Select Restore > Restore specific files or folders.
    • Select the protected account, choose the restore date, then browse the folder hierarchy to select the files/folders to restore.
    • Select Start restoration.

[!NOTE] Microsoft 365 Backup maintains backup data within the Microsoft 365 data trust boundary and honours your tenant’s data residency configuration. The service complements (but does not replace) OneDrive versioning and Files Restore — which are always available for user-initiated recovery without admin involvement.

HOME ← ISM-1808
ISM-1811 →