Study guide

10.5 Permissions, Network, and Storage Troubleshooting Chain

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

10.5 Permissions, Network, and Storage Troubleshooting Chain

Key Takeaways Explain This Topic AI

Storage troubleshooting should distinguish authentication, authorization, firewall, private endpoint, DNS, SAS, and service feature issues.

A 403 error and a timeout point to different branches of the troubleshooting tree.

SAS tokens must be checked for permissions, services, resource types, start and expiry time, protocol, IP range, and stored access policy behavior.

Private endpoint cases require validating DNS from the client, not just private endpoint approval state.

Remediation should preserve the security intent, especially when public access has been disabled deliberately.

Last updated: May 2026

The storage troubleshooting chain

Storage cases are dense because Azure Storage supports multiple authorization models and multiple network access patterns. A blob read can fail because the user has the wrong role, the managed identity is not assigned, the SAS token expired, the storage firewall blocks the client, the private endpoint DNS is wrong, the container name is wrong, or the blob was moved to an access tier that changes retrieval behavior. The exam will usually give a clue. Your job is to read the clue in the right order.

Start with the operation. Is the caller listing containers, reading a blob, writing a file share, mounting SMB, using AzCopy, or configuring the account? Listing storage account properties is not the same as reading data. Mounting Azure Files over SMB is not the same as downloading a blob over HTTPS.

Then classify the symptom.

Symptom Leading branch Typical evidence

401 or authentication failure Credential missing or invalid Bad token, disabled key, wrong identity, expired SAS

403 authorization failure Permission or policy denies operation Missing data role, SAS lacks permission, firewall may also return authorization style errors

  • Timeout or cannot resolve name Network or DNS NSG, UDR, private DNS, firewall, endpoint path
  • Blob not found Object path or version Wrong container, blob name, snapshot, version, soft delete state
  • Mount fails Azure Files auth and network SMB port, identity/domain configuration, key, share permissions
  • Branch 1: RBAC and managed identity

A managed identity is a principal. It still needs role assignments. For Blob Storage data, management-plane roles such as Reader or Contributor are not enough to read or write blob content. Use data roles such as Storage Blob Data Reader, Storage Blob Data Contributor, or Storage Blob Data Owner depending on the requirement.

Scope matters. Assigning a data role at subscription scope may work, but it is broader than needed if the app only needs one container. Assign at container or storage account scope when that meets the requirement. Also check propagation delay, wrong identity selection, and user-assigned versus system-assigned identity confusion.

A VM or App Service may have multiple identities. The application must request a token as the identity you granted. If a user-assigned identity has the role but the app uses the system-assigned identity, authorization fails. In an exam question, watch for wording such as the identity was created versus the identity was assigned to the app .

Branch 2: SAS tokens

A SAS token is not just a password string. It encodes scope, permissions, service, resource type, start time, expiry time, protocol, signed IP range, and sometimes a stored access policy relationship. When AzCopy fails with a SAS token, inspect these properties.

Common traps:

SAS start time is in the future because of clock skew.

SAS has read permission but the operation is write, create, delete, or list.

SAS is scoped to a blob but the command lists the container.

SAS permits HTTPS only, but the client attempts HTTP.

SAS has an IP restriction that excludes the client or hosted agent.

Stored access policy was changed or deleted, invalidating dependent SAS behavior.

Least privilege applies here too. If the requirement is temporary upload to one container, issue a SAS with only required permissions and a short expiry. Do not regenerate account keys unless the keys are compromised or the scenario specifically requires invalidating key-based access.

Branch 3: Storage firewall and private endpoints

A correct token can still fail when the network path is blocked. Storage firewalls can restrict public endpoint access to selected networks. Private endpoints provide private IP access to storage subresources. Service endpoints can allow VNet subnet traffic to the storage public endpoint with network rules.

For private endpoints, validate DNS from the client machine. The storage account name should resolve to a private IP associated with the private endpoint. If it resolves publicly while public network access is disabled, the connection fails. If it resolves privately but traffic still fails, inspect NSGs, UDRs, peering DNS behavior, and whether the private endpoint subresource matches the service being used, such as blob versus file.

  • Commands to collect evidence: nslookup examstorage104.blob.core.windows.net
  • az storage account show -g rg-data -n examstorage104 --query networkRuleSet
  • az network private-endpoint list -g rg-data -o table
  • az role assignment list --assignee <principal-id> --all -o table
  • Branch 4: Azure Files specifics

Azure Files can use access keys, SAS in some scenarios, identity-based access patterns, snapshots, and backup. SMB access also depends on port 445 availability from the client network unless using supported private connectivity patterns. Corporate networks often block outbound SMB. A blob troubleshooting answer may be wrong for Azure Files because the protocol and authorization model differ.

If a Windows VM cannot mount a file share, check the storage account network rules, private endpoint for file, DNS, port 445 path, share name, key or identity configuration, and NTFS/share permissions when identity-based access is used. If the requirement says avoid account keys, choose identity-based Azure Files access where supported and configured correctly.

Remediation discipline

Never widen access before you know the branch. Publicly enabling a storage account may hide a DNS problem, but it violates a no-public-access requirement. Assigning Owner may hide a missing data role, but it violates least privilege. Regenerating account keys may break other workloads.

Write the fix in this format: Because the symptom is <403/timeout/not found>, and evidence shows <specific setting>, remediate by <specific minimal change>. Example: Because the VM resolves blob storage to a public IP while public access is disabled, fix the private DNS zone link to the VM VNet. Do not enable public network access.

This chain is useful beyond storage. It teaches the AZ-104 habit: classify, prove, then change.