Study guide
10.2 Selecting and Configuring Access to Azure Files
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
10.2 Selecting and Configuring Access to Azure Files
Key Takeaways Explain This Topic AI
Identity-based SMB authentication comes in three flavours: on-premises AD DS, Microsoft Entra Domain Services, and Microsoft Entra Kerberos for hybrid accounts.
Share-level permissions are Azure RBAC roles; directory and file permissions are Windows NTFS ACLs enforced inside the share.
Storage File Data SMB Share Elevated Contributor is the role that grants NTFS permission modification, not just read and write.
NFS 4.1 shares have no identity-based authentication, require premium FileStorage, and cannot use the secure transfer required setting.
SMB 3.x channel encryption protects data in transit, and Azure Files rejects unencrypted SMB when secure transfer is required.
Last updated: August 2026
Choosing an Access Method
Azure Files is the only Azure Storage service where the protocol determines the security model, so start there.
Protocol Authentication options Encryption in transit Notes
SMB 3.x Storage account key, or identity-based (AD DS, Microsoft Entra Domain Services, Microsoft Entra Kerberos) SMB channel encryption (AES-128/256-GCM) The mainstream choice for Windows and modern Linux
NFS 4.1 None — no identity-based authentication Not supported by the protocol as used here Premium FileStorage only; security is network-based
REST / SDK Microsoft Entra ID (RBAC), account key, SAS HTTPS Programmatic access; different RBAC roles than SMB
The decision tree the exam expects:
Windows file shares that need per-user permissions → SMB with identity-based authentication .
Lift-and-shift Linux workloads needing POSIX semantics → NFS 4.1 on premium , secured with private endpoints and network rules because there is no user identity.
Applications rather than users → REST with a managed identity and the data-plane RBAC roles.
Identity-Based Authentication over SMB
Using the storage account key for SMB means every user who mounts the share is the same super-user. Identity-based authentication replaces that with real principals.
Source Requirement Best for
On-premises AD DS Domain-joined clients with line of sight to a domain controller; the storage account is registered as a computer account in AD Hybrid environments with existing NTFS ACLs
Microsoft Entra Domain Services A managed domain in the same tenant Cloud-only environments that still need Kerberos
Microsoft Entra Kerberos Microsoft Entra joined clients using hybrid user accounts Modern Entra-joined desktops, notably Azure Virtual Desktop FSLogix profiles
The two-layer permission model
This is the part candidates get wrong.
Share-level permissions = Azure RBAC. Assigned on the file share (or storage account) scope:
Storage File Data SMB Share Reader — read.
Storage File Data SMB Share Contributor — read, write, delete.
Storage File Data SMB Share Elevated Contributor — read, write, delete plus modify NTFS ACLs .
You can also set a default share-level permission on the storage account so all authenticated identities receive a baseline role instead of assigning each one.
Directory and file permissions = Windows NTFS ACLs , set from a domain-joined client with icacls or File Explorer, and preserved through robocopy migrations.
Effective access is the intersection : RBAC must let you onto the share, and the NTFS ACL must let you touch the file. A user with Elevated Contributor but a Deny NTFS ACL still cannot read the file.
For REST/SDK access the roles are different again — Storage File Data Privileged Contributor / Reader bypass NTFS ACLs for administrative tooling, which is why they should be tightly held.
NFS 4.1 Shares
NFS shares behave differently in ways that show up as exam discriminators:
Require the premium FileStorage account kind with the NFS protocol chosen at share creation; you cannot switch protocols later.
No identity-based authentication. Access control is entirely network-based: place the account behind a private endpoint or restrict it to selected virtual networks, then rely on POSIX UID/GID inside the share.
The "Secure transfer required" setting must be disabled for the account, because the NFS 4.1 configuration used by Azure Files does not carry the encryption that setting enforces. This makes network isolation mandatory rather than optional — the traffic is not encrypted in transit.
Public network access should be disabled outright.
If a scenario says "Linux workload, must be encrypted in transit, must authenticate users" the answer is SMB with identity-based authentication , not NFS.
Network, Encryption, and Data Protection
Private endpoints give the share a private IP and a privatelink.file.core.windows.net DNS record. Combine with public network access disabled .
Service endpoints plus firewall rules are the lighter-weight alternative when a private endpoint is not viable.
Port 445 egress is blocked by many ISPs and corporate firewalls — the standard cause of "cannot mount from home". Azure File Sync or a VPN/ExpressRoute path is the remediation, not opening 445 to the internet.
SMB security settings on the account let you restrict allowed SMB versions, authentication mechanisms (Kerberos only), and channel encryption strength. Requiring AES-256-GCM and disabling SMB 2.1 is the hardened baseline.
Encryption at rest is always on with Microsoft-managed keys; switch to customer-managed keys in Key Vault when policy demands, and enable infrastructure encryption at account creation for double encryption.
Data protection : enable soft delete for file shares (retention in days) so a deleted share is recoverable, take share snapshots for point-in-time copies, and use Azure Backup for scheduled, policy-driven protection with its own vault-level controls.