Study guide
4.6 Azure Files, Snapshots, File Sync, and AzCopy
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
4.6 Azure Files, Snapshots, File Sync, and AzCopy
Key Takeaways Explain This Topic AI
Azure Files shares support snapshots for point-in-time recovery, but snapshots are not a substitute for a full backup and retention strategy.
Azure File Sync extends Azure Files to Windows Server with cloud tiering, sync groups, server endpoints, and Storage Sync Service.
AzCopy is a practical transfer tool for blobs and files, with support for SAS, Microsoft Entra authorization, sync, copy, and recursive operations.
File share performance, quota, protocol, identity, and network path should be checked before blaming the application.
Exam scenarios often ask you to choose between direct file share mounts, File Sync, snapshots, backup, and bulk transfer tooling.
Last updated: May 2026
Managed file shares and operational tools
Azure Files gives administrators SMB and NFS file shares without managing file servers. Standard shares are capacity based and fit many general workloads. Premium shares are provisioned and often selected when applications need low latency or predictable throughput. Before creating a share, decide protocol, redundancy, quota, identity model, network path, backup or snapshot strategy, and whether clients will mount Azure directly or use a Windows Server cache through Azure File Sync.
- Need Feature or tool Why
- Restore a share to a recent point Share snapshot Point-in-time copy of share contents
- Central cloud share with branch cache Azure File Sync Syncs Azure Files with Windows Server endpoints
- Bulk upload to a container or share AzCopy copy Efficient command-line transfer
- Mirror local folder changes AzCopy sync Compares source and destination and applies changes
- User file restore and policy retention Azure Backup for Azure Files Managed backup policy and restore workflow
- Low-latency file workload Premium file share Provisioned performance model
Share snapshots capture a point-in-time, read-only view of a file share. They are useful before maintenance, migrations, or risky application changes. You can browse snapshot contents and restore files by copying them back. Snapshots consume storage for changed data and must be managed. They are not the same as Azure Backup policy management, which provides scheduled protection, retention, and restore operations through a vault-backed experience.
Portal path for snapshots: Storage account > Data storage > File shares > select share > Snapshots > Add snapshot. To restore, browse the snapshot, select files or directories, and copy them back to the active share. For Azure Backup, use Backup center or Recovery Services vault integration, then configure backup for Azure Files and choose a policy.
Azure File Sync is used when Windows Servers need to keep local access while Azure Files becomes the central cloud endpoint. Core components include Storage Sync Service, sync group, cloud endpoint, registered server, and server endpoint. Cloud tiering can keep frequently used files local while tiering cold file content to Azure, leaving namespace pointers on the server. This helps branch offices with limited disk capacity, but it requires planning for recall behavior, antivirus exclusions, and server health.
A typical deployment sequence is: create a storage account and Azure file share, create a Storage Sync Service in the same region as the storage account where appropriate, install the Azure File Sync agent on Windows Server, register the server, create a sync group, add the Azure file share as the cloud endpoint, and add one or more server endpoints. Do not place overlapping server endpoints on the same server path. Watch sync health, free space, and tiering policy.
AzCopy is a command-line tool for moving data to and from Azure Storage. It is not limited to one service, and it is common in migration and operations tasks. Authentication can use Microsoft Entra login for supported operations or SAS URLs. For repeatable jobs, avoid long-lived SAS tokens and avoid writing secrets into shell history. Use managed identity where the execution environment supports it and AzCopy supports the target scenario.
AzCopy examples: azcopy login
azcopy copy './reports' 'https://staz104prod01.blob.core.windows.net/reports' --recursive=true
azcopy copy 'https://stsource.blob.core.windows.net/raw?<sas>' 'https://stdest.blob.core.windows.net/raw?<sas>' --recursive=true
azcopy sync './content' 'https://staz104files01.file.core.windows.net/site?<sas>' --recursive=true
Use copy when you want to transfer source objects to a destination. Use sync when the destination should reflect source differences. Be careful with sync delete behavior and test with a small path before running broad jobs. For data migrations, plan permissions, firewall rules, private endpoint routing, throughput, retries, logging, and whether preserved metadata matters.
Troubleshooting Azure Files starts with mount path and protocol. For SMB, confirm TCP 445, DNS, identity or key credentials, storage firewall, private endpoint subresource file, share quota, and NTFS permissions. For NFS, confirm the account and share support NFS, network restrictions are configured because NFS access is network based, and clients mount from allowed networks. For performance issues, inspect share tier, provisioned size for premium, IOPS and throughput limits, client latency, and whether Azure File Sync tiered files are being recalled over a slow link.
Troubleshooting File Sync has its own pattern. If files do not appear in Azure, check agent health, server registration, sync group membership, server endpoint path, conflict files, and errors in the FileSyncSvc event logs. If a user opens a tiered file and it takes a long time, that may be recall from Azure rather than an application defect. If free space keeps dropping, review cloud tiering policy and volume free space policy. If antivirus scans recall every tiered file, configure exclusions according to product guidance.
Case scenario: a branch office has a local Windows file server with 4 TB of files, but only 15 percent is active. Users need LAN-speed access at the branch, headquarters needs central backup, and the company wants cloud-based disaster recovery. Azure File Sync with cloud tiering is a better fit than asking every user to mount the Azure file share directly across the WAN. Add Azure Backup for the file share, monitor sync health, and test restore. If the scenario instead says a one-time migration of 500 GB of blobs from a local folder is needed, AzCopy is the more direct tool.