Implementation guidance for Australian Essential Eight controls in Microsoft environments - ISM controls with PSPF mappings
| 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 |
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]
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.
[!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.
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]
Configure backup frequency and retention to support synchronised restore points; set hourly backups for high-churn data and longer retention per compliance requirements.[^9]
Enable instant restore capability for Windows backups to allow rapid recovery from snapshot-based restore points.[^9]
Configure backup windows to minimize performance impact and ensure backups complete before the next cycle.[^9]
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
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
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):
[!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).
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
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
[!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.
Windows Backup for Organizations overview provides restore process details and configuration steps for Windows backup across devices and Entra ID integration Windows Backup for Organizations overview
Why Pursue ACSC Essential Eight User Backup Guidelines? ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9
Manage automated backups (preview) — SQL Server enabled by Azure Arc ↩ ↩2
Learn about retention for SharePoint and OneDrive — Microsoft Purview ↩ ↩2
Redirect and move Windows known folders to OneDrive (Known Folder Move) ↩ ↩2
Business continuity and disaster recovery options for FSLogix ↩ ↩2 ↩3