Contoso configured firewall rules on a storage account in the East US region so that only selected networks can connect. A VM in a virtual network subnet in the same region must read blobs in this account, but its requests are still denied after the VM's public IP address is added to an IP network rule. What should you do to allow access from this VM?
Show answer and explanation
Answer: C
Explanation
IP network rules have no effect on requests that originate from the same Azure region as the storage account. Same-region requests must be allowed with virtual network rules.[2] To allow traffic from a subnet, add a virtual network rule and also enable a service endpoint on that subnet. Microsoft.Storage provides connectivity to storage accounts in the same region as the virtual network.[1]
IP network rules are allowed only for public internet IP addresses, so RFC 1918 private ranges such as addresses that start with 10 can’t be added.[2] The /31 and /32 prefix sizes aren’t supported and must be configured as individual IP address rules, and changing the format doesn’t make IP network rules apply to same-region requests.[2] A trusted service exception is for Azure services that operate from a network you can’t include in virtual network or IP network rules. A VM in a subnet is allowed with a virtual network rule.[1]