Question 220
An external partner's gateway sends traffic from a stable public IPv4 address to a storage account. Security permits that gateway only and wants every other public source denied. What should be configured?
Explanation
Correct Answer
Storage firewall IP network rules can permit eligible public IPv4 source addresses while the account's default selected-network restriction denies other public origins. Add only the verified partner egress address or smallest supported range, not a broad public CIDR, and keep storage authentication and authorization independently enforced. Review NAT changes with the partner because the firewall evaluates the public source seen by Azure Storage, not necessarily an internal workstation's address.
Incorrect Answers
Allowing every public IPv4 source would remove the requested origin restriction and expose the storage endpoint to other internet clients, even if normal authentication still applies. Use a narrow verified partner egress rule rather than a universal allow range. Authentication is not a replacement for the specified network control.
Azure service endpoints are configured for supported Azure virtual-network subnets, not arbitrary on-premises network adapters. An external gateway using a public egress IP should be covered by an appropriate storage IP firewall rule or another approved private connectivity design. A fictitious endpoint setting cannot authorize its traffic.
Resource-group Reader allows ARM configuration visibility; it does not create a storage firewall IP allowlist entry. The partner needs an approved network path, followed by appropriate storage data authorization, not a generic management role. Add the required public-source network rule instead.