Question 130
A managed identity has Storage Blob Data Contributor at the correct container scope, but its requests from an unapproved public network are rejected by the storage account firewall. What should you investigate?
Explanation
Correct Answer
Azure Storage evaluates network access controls independently from the caller's Microsoft Entra data-plane authorization. Even an identity with valid Blob Data Contributor permissions can fail when requests originate outside permitted network paths. Inspect storage account public network access, selected network and subnet rules, or the private endpoint and DNS configuration appropriate to the workload. Do not expand the identity's Azure RBAC role merely to overcome a firewall denial; doing so would increase privileges without fixing connectivity.
Incorrect Answers
Data Owner grants more blob permissions and may include ownership and ACL actions, but it does not override storage account firewall restrictions. Subscription scope would also expose unrelated accounts. The current failure is linked to the calling network's eligibility, so the administrator must correct or use an approved network path rather than elevating data permissions.
Resource Owner is a powerful ARM role, but the storage firewall still enforces its network rules on data requests. Broadening management access does not make a disallowed public client become an approved source. Investigate the account's network configuration and client origin while retaining the already adequate blob data role.
Blob versioning records earlier versions of objects; it does not authorize traffic from denied networks or change firewall rules. A configuration that improves recovery of overwritten blobs cannot fix network-level access rejection. Use the approved virtual network, private endpoint, or carefully scoped firewall rule appropriate to the service's design.