Study guide
13.7 Azure File Sync, Cloud Tiering & Monitoring
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
13.7 Azure File Sync, Cloud Tiering & Monitoring
Key Takeaways Explain This Topic AI
Azure File Sync centralizes file shares in Azure Files while keeping on-premises Windows Servers as local caches, using a Storage Sync Service, sync groups, cloud endpoints, and server endpoints.
A sync group contains exactly one cloud endpoint (an Azure file share) and one or more server endpoints (a path on a registered Windows Server volume).
Cloud tiering replaces the payload of cold files with NTFS reparse points carrying the FILE_ATTRIBUTE_OFFLINE and FILE_ATTRIBUTE_REPARSE_POINT flags, dropping size on disk to near 0 KB while the logical file size is unchanged.
The Volume Free Space policy is always active and tiers the least recently accessed files until the configured percentage of free space is restored; the optional Date policy additionally tiers files untouched for a set number of days.
Monitor Azure File Sync through its Telemetry log: event 9102 records a completed sync session, 9121 records each per-item error, 9302 reports in-progress sync counts, and 9003 reports cloud-tiering error distribution.
Last updated: August 2026
Azure File Sync, Cloud Tiering & Monitoring
Section 13.6 covered the cloud side of the story. Azure File Sync (AFS) is what makes it hybrid : it centralizes an organization's file shares in Azure Files while keeping on-premises Windows Servers in place as high-performance local caches, so users keep their familiar UNC paths and local read speeds while the authoritative copy lives in Azure.
1. Azure File Sync (AFS) Architecture & Components
Azure File Sync (AFS) centralizes organization file shares in Azure Files while preserving local Windows Servers as high-performance local caches. +-----------------------------------------------------------------------------------+
- | AZURE FILE SYNC ARCHITECTURE |
- | |
- | [STORAGE SYNC SERVICE (Azure Resource)] |
- | `-- [SYNC GROUP: CorpDataSync] |
- | |-- [Cloud Endpoint] |
- | | `-- Azure File Share: 'corp-cloud-share' (Central Master Storage) |
- | | |
- | |-- [Server Endpoint 1: NY-FS01] |
- | | `-- Local Path: 'D:\Shares\Corp' (Cloud Tiering Enabled: 20% Free) |
- | | |
- | `-- [Server Endpoint 2: LON-FS01] |
- | `-- Local Path: 'D:\Shares\Corp' (Cloud Tiering Enabled: 15% Free) |
- +-----------------------------------------------------------------------------------+
- Core Terminology
Storage Sync Service: The top-level Azure Resource Manager resource that manages sync relationships.
Registered Server: An on-premises or Azure IaaS Windows Server that has the Azure File Sync Agent installed and has been registered with a Storage Sync Service.
Sync Group: Defines the replication topology. Contains exactly one Cloud Endpoint and one or more Server Endpoints .
Cloud Endpoint: A specific Azure File Share participating in a Sync Group.
Server Endpoint: A specific directory path on a registered Windows Server volume (e.g., D:\Shares\Marketing ).
2. Cloud Tiering Mechanics & Policies
Cloud Tiering is an optional feature of Azure File Sync that transforms local Windows Servers into high-speed caches of the Azure File Share. +-----------------------------------------------------------------------------------+
- | CLOUD TIERING FILE STATES |
- | |
- | [NORMAL FILE (Hot Data)] [TIERED FILE (Cold Data)] |
- | +-------------------------------+ +-------------------------------+ |
- | | Full File Payload on Local Disk| | NTFS Reparse Point (Pointer) | |
- | | Size = Size on Disk | | Size on Disk = 0 KB | |
- | | Attributes: Standard (A) | | Attributes: Offline (O) / Reparse (L) |
- | +-------------------------------+ +-------------------------------+ |
- | | |
- | [User Opens Tiered File] |
- | | |
- | v |
- | [Transparent Recall from Azure Files] |
- +-----------------------------------------------------------------------------------+
- Cloud Tiering File Anatomy
When a file is tiered:
The file content is stored safely in the Azure File Share.
The local file on the Windows Server volume is replaced with an NTFS Reparse Point .
The file's size on disk drops to near 0 KB , while its logical file size remains unchanged.
The file is assigned the FILE_ATTRIBUTE_OFFLINE (attribute O ) and FILE_ATTRIBUTE_REPARSE_POINT (attribute L ) flags.
When a user opens the file, the AFS file system filter driver ( StorageSync.sys ) intercepts the read I/O, recalls the file data from Azure Files across the network, and serves the content transparently.
Cloud Tiering Policies
Volume Free Space Policy (Always Active): Specifies the percentage of free space that must always be maintained on the local volume (e.g., 20% ). When volume utilization exceeds 80%, AFS continuously tiers the least recently accessed files to the cloud until 20% free space is achieved.
Date Policy (Optional): Specifies that files should be tiered if they have not been accessed or modified within a set number of days (e.g., 30 days ). # Register an on-premises Windows Server with Azure File Sync
- Register-AzStorageSyncServer `
- ResourceGroupName 'RG-Storage' `
- StorageSyncServiceName 'CorpStorageSync' `
- TenantId '11111111-2222-3333-4444-555555555555'
- # Create a Server Endpoint with Cloud Tiering enabled (20% Volume Free Space, 60-day Date Policy)
- New-AzStorageSyncServerEndpoint `
- ResourceGroupName 'RG-Storage' `
- StorageSyncServiceName 'CorpStorageSync' `
- SyncGroupName 'CorpDataSync' `
-ServerId (Get-AzStorageSyncServer -ResourceGroupName 'RG-Storage' -StorageSyncServiceName 'CorpStorageSync').ServerId `
- ServerLocalPath 'D:\Shares\Corp' `
- CloudTiering $true `
- VolumeFreeSpacePercent 20 `
- TierFilesOlderThanDays 60
- 3. Monitoring, Troubleshooting & Migration Strategies
- Monitoring & Diagnostics
Event Viewer: Azure File Sync writes to the Telemetry event log under Applications and Services Logs -> Microsoft -> FileSync -> Agent :
Event ID 9102: Logged once a sync session completes. HResult = 0 means the session succeeded, and PerItemErrorCount reports how many individual items failed inside it.
Event ID 9302: Logged every 5-10 minutes while a sync session is active. Compare AppliedItemCount against TotalItemCount to confirm the session is still making forward progress; a session stuck at AppliedItemCount=0 eventually fails and logs a 9102 carrying the error.
Event ID 9121: Logged once per distinct per-item error after a session completes, with PersistentCount and TransientCount . This is where locked files and unsupported characters surface.
Event ID 9003: Cloud tiering error distribution for a server endpoint (Total Error Count plus ErrorCode, one event per error code). The portal's Tiering errors figure is built from this event; 9006 is its recall-error counterpart.
Event ID 9016: Ghosting (tiering) results for a volume - free space percent, number of files ghosted in the session, and number of files that failed to ghost.
Warning
Exam trap: 9003 is a cloud tiering error event, not a sync-session event, and 9102 is the session-level result, not the per-item error. The per-item error event is 9121 . A question that describes "one event logged per error code" is pointing at 9003/9006, while one that describes an HResult for the whole session is pointing at 9102.
Azure Monitor: Track telemetry metrics including Sync Health , Tiering Recall Size , and Server Endpoint Low Disk Space Mode .
Migration Strategies: Moving to Azure File Sync +-----------------------------------------------------------------------------------+
- | AFS DATA PRE-SEEDING WORKFLOW |
- | |
- | [Step 1: Pre-seed to Azure] ---> RoboCopy / Azure Data Box / AzCopy uploads |
- | bulk data directly to Azure File Share |
- | | |
- | v |
- | [Step 2: Server Endpoint] ---> Deploy AFS Agent & Create Server Endpoint |
- | | |
- | v |
- | [Step 3: Fast Cloud Recall] ---> Server downloads lightweight namespace / |
- | reparse points without downloading full data |
- +-----------------------------------------------------------------------------------+
Storage Migration Service (SMS): Automates the discovery, inventory, transfer, and cutover of legacy Windows Server 2008/2012/2016/2022/2025 file servers directly into Azure File Sync endpoints.
RoboCopy Pre-Seeding: For multi-terabyte shares over slow WAN links, administrators pre-seed data to Azure Files, install the AFS agent on the local server, and let AFS reconcile namespaces using hash signatures without transferring full payloads across the WAN: # Multi-threaded RoboCopy command preserving NTFS ACLs, ownership, and timestamps
- robocopy D:\SourceData \\mystorageacct.file.core.windows.net\share\SourceData `
- /MIR `
- /COPY:DATSO `
- /DCOPY:DAT `
- /ZB `
- /MT:32 `
- /R:3 `
- /W:5 `
- /LOG:C:\Logs\Preseed.log