Study guide
4.4 Identity-Based Access for Azure Files
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.4 Identity-Based Access for Azure Files
Key Takeaways Explain This Topic AI
Azure Files authorization has a share-level control plane and data-plane identity layer, plus Windows file and directory permissions for SMB scenarios.
Microsoft Entra Kerberos, AD DS, and Microsoft Entra Domain Services are different identity integration choices for Azure Files.
Azure RBAC share roles grant access at the share level but NTFS permissions still control file and folder access when SMB identity is used.
Storage account keys bypass identity-based file permissions and should be restricted for production shares.
Troubleshooting Azure Files access requires checking port 445, DNS, identity source, role assignment, share permissions, NTFS ACLs, and network rules.
Last updated: May 2026
Azure Files identity is layered
Azure Files provides fully managed file shares that can be mounted by Windows, Linux, and macOS clients over SMB, and by supported clients over NFS for specific configurations. Identity-based access is most often discussed for SMB. The key idea is that share access is not controlled by only one setting. Network access must allow the request, the user or computer must authenticate through a supported identity source, Azure RBAC must permit share-level access, and file or directory ACLs must permit the operation.
There are several identity source options. Traditional Active Directory Domain Services integration lets domain-joined machines use AD DS identities for SMB access. Microsoft Entra Domain Services can support managed domain scenarios. Microsoft Entra Kerberos for Azure Files supports cloud Kerberos authentication for hybrid identities in supported Windows scenarios and can reduce dependency on line-of-sight to domain controllers for some designs. The exam usually gives clues such as domain-joined Windows clients, hybrid users, existing AD DS, or cloud-only management goals.
Identity option Common client scenario Administrative clue Permission layers
Storage account key Any SMB client that has the key Legacy or simple mount script Full share access through key, bypasses user identity
AD DS authentication Domain-joined Windows clients Existing on-premises Active Directory Azure RBAC share role plus NTFS ACLs
Microsoft Entra Domain Services Managed domain clients No self-managed domain controllers Azure RBAC share role plus NTFS ACLs
Microsoft Entra Kerberos Supported Windows clients with Entra identities Cloud Kerberos requirement Azure RBAC share role plus Windows ACLs
Azure RBAC roles for Azure Files include share-level roles such as Storage File Data SMB Share Reader, Storage File Data SMB Share Contributor, and Storage File Data SMB Share Elevated Contributor. These roles do not replace NTFS permissions inside the share. Think of RBAC as opening the share door and NTFS permissions as controlling rooms and files inside. A user with share Contributor can still be denied by NTFS ACLs on a folder. A user with NTFS Modify but no share-level role can also fail.
Portal path example: Storage account > Data storage > File shares > select share. Use Access Control (IAM) to assign a Storage File Data SMB Share role to a user or group at the storage account or share scope. Use Configuration or File shares identity-based access settings on the storage account to configure the chosen directory service integration. Then manage directory and file ACLs from a mounted Windows client or supported administrative tooling.
- CLI examples for role assignment: STORAGE_ID=$(az storage account show \
- -name staz104files01 \
- -resource-group rg-storage-prod \
- -query id -o tsv)
- az role assignment create \
- -assignee user1@contoso.com \
- -role 'Storage File Data SMB Share Contributor' \
- -scope $STORAGE_ID/fileServices/default/fileshares/projects
Mount examples show the difference between key-based and identity-based thinking. A key-based Windows mount uses the storage account name as the user and the account key as the password. It is easy, but it is broad and difficult to audit by user. Identity-based access allows the user identity to be evaluated and logged more meaningfully, but it requires correct domain or Entra configuration. net use Z: \\staz104files01.file.core.windows.net\projects /persistent:yes
Before assuming permissions are wrong, check connectivity. SMB uses TCP port 445. Some internet providers and corporate networks block outbound 445, which causes mount failures even when identity settings are correct. Private endpoints, VPN, or ExpressRoute can provide a private path, but DNS must resolve the file endpoint to the private IP when public access is disabled. A private endpoint for blob does not help Azure Files; use the file subresource.
Troubleshooting cases:
Symptom Likely cause What to check
Mount fails before credential prompt Network path blocked Port 445, firewall, private endpoint DNS, storage network rules
User authenticates but cannot open share Missing share-level RBAC Storage File Data SMB Share role scope and propagation
User opens share but cannot edit folder NTFS ACL denies write Folder ACLs from Windows security tab or icacls
Key-based mount works but identity mount fails Identity integration issue AD DS, Entra Kerberos, domain join, SPN, synced identity
Access works from Azure VM but not laptop Network or DNS difference Public network access, VPN, private DNS, ISP port blocking
Administrators must also decide how to handle elevated tasks. Storage File Data SMB Share Elevated Contributor can be used for administrative operations that need elevated file permission management. It should not be assigned broadly. For normal user access, assign group-based roles and manage NTFS ACLs through groups. This aligns with the least privilege model and keeps operations maintainable.
Case scenario: a company wants a shared departmental drive in Azure Files for domain users. Users should map the drive with their normal Windows identity, help desk staff should manage folder permissions, and storage keys should not be distributed. The correct design is identity-based SMB access integrated with the appropriate directory service, Azure RBAC file share roles assigned to groups, NTFS ACLs set on directories, storage firewall or private endpoint access for client networks, and a process to restrict or monitor account key usage.
If the problem states that users receive access denied only on one folder, focus on NTFS ACLs. If they cannot mount the share at all, start with port 445, DNS, and network rules.