Study guide
13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
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.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
Key Takeaways Explain This Topic AI
Azure File Sync works fully with DFS Namespaces: keep DFS-N for the namespace and let AFS handle sync behind each folder target.
The migration starts on the server holding the full data set, creates its server endpoint with cloud tiering off, and lets everything sync to the cloud endpoint before any other server is touched.
DFS-R is disabled after the remaining agents are registered but before their server endpoints are created; creating endpoints while DFS-R still replicates is what produces conflict files.
Cloud tiering may be enabled only at the final step, after DFS-R has been retired and the topology has been tested.
The DfsrPrivate and DFSRoots folders are junctions and are skipped by Azure File Sync, and Sysprep is unsupported on a server after the AFS agent is installed.
Last updated: August 2026
Migrating DFS Namespaces & DFS Replication to Azure File Sync
The AZ-800 blueprint lists "Migrate Distributed File System (DFS) to Azure File Sync" as its own objective inside Configure and manage Azure Files . It is a favourite scenario item because DFS-N and DFS-R behave completely differently when Azure File Sync (AFS) arrives: one is a namespace service that AFS happily lives alongside, the other is a competing replication engine that must eventually be retired. Confusing the two is the single most common mistake on this objective.
1. DFS-N and DFS-R Interoperability, Side by Side
Azure File Sync supports interoperability with both DFS Namespaces (DFS-N) and DFS Replication (DFS-R), but the intent is different in each case.
Technology What it does AFS relationship
DFS-N (Namespaces) Presents a single logical path such as \\contoso.com\public that redirects clients to folder targets Fully supported alongside AFS. Install the AFS agent on one or more file servers to sync data, and keep using DFS-N for the namespace
DFS-R (Replication) Multi-master replication of folder contents between servers using RDC A competing replication solution. In most cases, replace DFS-R with Azure File Sync
Because DFS-N only hands out referrals and never moves file data, it is complementary: users keep hitting \\contoso.com\public , while AFS quietly handles sync and cloud tiering behind each folder target. Migration to AFS therefore usually leaves the namespace untouched, which is precisely why DFS-N is the low-risk half of this objective.
DFS-R is different. Two independent replication engines writing to the same folder produce conflicts, so Microsoft's guidance is to replace it. There are, however, three documented scenarios where DFS-R and AFS legitimately run together :
You are mid-migration from a DFS-R deployment to an AFS deployment.
Not every on-premises server that needs a copy of the data can connect directly to the internet.
Branch servers consolidate data onto a single hub server , and you want AFS on the hub.
Rules for running DFS-R and AFS side by side
When both are running at once, three constraints apply, and each maps directly to an exam distractor:
You must disable Azure File Sync cloud tiering on volumes that hold DFS-R replicated folders.
You shouldn't configure server endpoints on DFS-R read-only replication folders.
Only a single server endpoint may overlap a DFS-R location. Multiple server endpoints overlapping other active DFS-R locations can lead to conflicts.
Warning
The cloud-tiering prohibition is the one candidates miss. Tiering replaces a local file with a reparse point; DFS-R sees a changed file and attempts to replicate a stub, which corrupts the replication group's view of the data. Cloud tiering stays off for the entire coexistence window.
2. The Documented DFS-R to Azure File Sync Migration
Microsoft publishes an ordered procedure. The sequence matters — the exam tests when DFS-R is disabled and when cloud tiering may finally be enabled. +---------------------------------------------------------------------------+
- | DFS-R -> AZURE FILE SYNC MIGRATION SEQUENCE |
- | |
- | 1. Create a sync group representing the DFS-R topology being replaced |
- | 2. Pick the server holding the FULL data set; install AFS on it |
- | 3. Register it, create a server endpoint -- CLOUD TIERING OFF |
- | 4. Let ALL data sync up to the Azure file share (cloud endpoint) |
- | 5. Install + register the AFS agent on the REMAINING DFS-R servers |
- | 6. ---- DISABLE DFS-R ---- |
- | 7. Create a server endpoint on each -- CLOUD TIERING STILL OFF |
- | 8. Let sync finish; test the topology |
- | 9. ---- RETIRE DFS-R ---- |
- | 10. NOW enable cloud tiering on any server endpoint as needed |
- +---------------------------------------------------------------------------+
Written out:
Create a sync group to represent the DFS Replication topology you're replacing.
Start on the server that has the full set of data in the DFS-R topology. Install Azure File Sync on that server.
Register that server and create a server endpoint for it. Don't enable cloud tiering.
Let all of the data sync to your Azure file share (the cloud endpoint).
Install and register the Azure File Sync agent on each of the remaining DFS-R servers.
Disable DFS-R.
Create a server endpoint on each of the DFS-R servers. Don't enable cloud tiering.
Ensure that sync finishes, and test your topology as needed.
Retire DFS-R.
You can now enable cloud tiering on any server endpoint as needed.
Three ordering facts carry the marks:
The authoritative-copy server goes first (step 2). Seeding from a partially-populated DFS-R member risks uploading an incomplete namespace as the cloud master.
DFS-R is disabled at step 6 , after the agents are installed on the remaining servers but before their server endpoints are created. Creating a second server endpoint while DFS-R is still replicating is what produces conflict files.
Cloud tiering is enabled only at step 10 , after DFS-R is retired — never during the migration.
3. Keeping the Namespace Stable with DFS-N
Because DFS-N is fully supported with AFS, the user-visible path survives the migration untouched. A typical hybrid end state: \\contoso.com\public (DFS-N namespace root)
- |
- +--------------+--------------+
- | |
- \\FS-HQ\public \\FS-BR1\public
- (AFS server endpoint) (AFS server endpoint)
- | |
- +---------> Azure file share <-+
- (cloud endpoint)
Both folder targets are now AFS server endpoints syncing to one cloud endpoint, and DFS-N continues to steer clients to the site-local target. If you decommission a branch file server, you retarget or remove its DFS-N folder target; clients following \\contoso.com\public never see a changed path.
For a full lift to the cloud, Azure Files can be surfaced directly under a DFS-N folder target, letting you retire the on-premises server while keeping the namespace.
4. Related Constraints Worth Memorizing
- Item Behaviour with Azure File Sync
- DfsrPrivate and DFSRoots folders Junctions — skipped by AFS and never synced
- Reparse points Skipped
- Alternate Data Streams Preserved on the server, but not synced
- NTFS compression + cloud tiering Don't combine; recall with Invoke-StorageSyncFileRecall then compact /U /S
Sysprep after installing the AFS agent Not supported. Install and register the agent only after image deployment and mini-setup
Other HSM solutions Not supported alongside AFS cloud tiering
Pre-seeding remains available for the bulk data movement itself — RoboCopy with /MIR /COPY:DATSO /DCOPY:DAT , Azure Data Box, or AzCopy — but pre-seeding is a data transfer optimization, not a substitute for the DFS-R retirement sequence above.
5. Exam Traps
- Scenario Correct response
- "We want AFS but must keep \\contoso.com\shared " Keep DFS-N; it is fully supported. Only DFS-R is replaced
Conflict files appear during migration A second server endpoint was created while DFS-R was still enabled — DFS-R must be disabled at step 6
Branch servers have no direct internet access A documented reason to keep DFS-R and AFS running together
Free space is critically low mid-migration Cloud tiering still cannot be enabled until DFS-R is retired; add capacity or finish the sequence
Server was cloned from an image with the AFS agent installed Unsupported — Sysprep after agent installation causes unpredictable results