Study guide
4.2 Storage Firewalls, Private Access, and Network Rules
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.2 Storage Firewalls, Private Access, and Network Rules
Key Takeaways Explain This Topic AI
Storage network security is controlled by public network access, firewall rules, virtual network rules, service endpoints, private endpoints, and trusted service exceptions.
A private endpoint gives the storage account a private IP in a VNet and usually requires private DNS for clean name resolution.
Service endpoints keep the public storage endpoint but restrict access to selected subnets.
Firewall troubleshooting requires separating DNS resolution, route path, authentication, authorization, and account-level feature restrictions.
Exam questions often ask for the least disruptive way to allow a subnet, block public access, or support on-premises access through private connectivity.
Last updated: May 2026
Network access is not the same as permission
A storage account request must pass network access checks and authorization checks. A user can have Storage Blob Data Contributor and still fail if the account firewall blocks the client IP. A VM can sit in an allowed subnet and still fail if the identity lacks data-plane permissions. This separation is one of the most common AZ-104 troubleshooting patterns.
The storage firewall can allow access from all networks, selected networks, or disabled public network access, depending on the account configuration and service. Selected networks can include public IPv4 address ranges, selected virtual network subnets, and trusted Azure services when the exception is enabled. Private endpoint access is different: it creates a network interface with a private IP address in a VNet for a specific storage subresource, such as blob, file, queue, table, dfs, or web.
Access method Endpoint used Best for Key administration issue
Public access from all networks Public storage endpoint Low restriction test workloads Broad exposure, still requires auth unless public blob is enabled
Firewall IP rule Public storage endpoint Admin workstation or known NAT address Client must appear from allowed public IPv4
VNet rule with service endpoint Public storage endpoint over Azure backbone Azure subnet access without private IP Subnet must enable Microsoft.Storage service endpoint
Private endpoint Private IP and private DNS Private connectivity from VNets and on-premises DNS must resolve account name to private endpoint
Trusted services exception Public service path Azure services that need account access Not all Azure services qualify and identity may still be required
Service endpoints and private endpoints are frequently confused. A service endpoint extends the VNet identity to the Azure Storage public endpoint. You still connect to the public FQDN, but the storage firewall can allow the selected subnet. A private endpoint gives the service a private IP in your VNet. Clients should resolve the normal storage account name to the private IP by using a private DNS zone such as privatelink.blob.core.windows.net for blob or privatelink.file.core.windows.net for file.
Portal path example for a firewall rule: Storage account > Security + networking > Networking > Firewalls and virtual networks. Select Enabled from selected virtual networks and IP addresses, add an existing subnet or public IP range, decide whether trusted Azure services are allowed, and save. For a private endpoint, use Storage account > Networking > Private endpoint connections > Private endpoint, then choose the target subresource and integrate with private DNS if Azure DNS is used.
- CLI examples: az storage account update \
- -name staz104prod01 \
- -resource-group rg-storage-prod \
- -default-action Deny
- az network vnet subnet update \
- -resource-group rg-network-prod \
- -vnet-name vnet-prod \
- -name snet-app \
- -service-endpoints Microsoft.Storage
- az storage account network-rule add \
- -resource-group rg-storage-prod \
- -account-name staz104prod01 \
- -vnet-name vnet-prod \
- -subnet snet-app
- Private endpoint example: az network private-endpoint create \
- -name pe-staz104-blob \
- -resource-group rg-network-prod \
- -vnet-name vnet-prod \
- -subnet snet-private-endpoints \
--private-connection-resource-id /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-storage-prod/providers/Microsoft.Storage/storageAccounts/staz104prod01 \
- -group-id blob \
- -connection-name peconn-staz104-blob
For production, private endpoints are often paired with disabled or tightly restricted public network access. This is common when on-premises users connect through VPN or ExpressRoute and DNS forwards storage names to Azure private DNS. If DNS is wrong, clients may resolve the public endpoint and then fail because public access is disabled. In that case, the authentication token, SAS token, or access key may be fine, but the network path is wrong.
Troubleshooting tree:
Resolve the storage account FQDN from the client. If it returns a public IP when private endpoint access is expected, fix private DNS zone links or conditional forwarding.
Test TCP connectivity to port 443. If DNS is private but connectivity fails, inspect routes, NSGs on the private endpoint subnet, firewall appliances, and peering.
Check the storage account networking page. If default action is Deny, confirm the subnet rule, IP rule, trusted service exception, or private endpoint approval.
Check authentication. A 403 can be a firewall denial, expired SAS, missing RBAC role, disabled shared key, or ACL denial. Use the error text and storage logs where available.
Check subresource. A private endpoint for blob does not provide private access to file. Azure Data Lake Storage Gen2 often needs dfs endpoint behavior as well as blob depending on the tool.
Common cases are easy to recognize. A developer connects from home and fails after selected networks is enabled because their home IP is not in the firewall and may change. A VM in an allowed subnet fails because the Microsoft.Storage service endpoint was not enabled before the VNet rule was added. An on-premises client using VPN fails after private endpoint deployment because DNS still points to blob.core.windows.net public records instead of the privatelink zone.
An Azure service fails even though trusted services is checked because that service is not covered or because the managed identity lacks data-plane access.
Choose the smallest rule that meets the requirement. If only a subnet needs access and public endpoints are acceptable, a service endpoint plus VNet rule can be simple. If traffic must stay on private addressing or on-premises users must use private connectivity, choose private endpoints and design DNS. If a single administrator needs temporary access, an IP firewall rule may be enough, but document the public NAT address and remove it when the task ends.