Private Endpoint Alone Does Not Grant VM Managed Identity Storage Access
Short answer
B No, because creating a private endpoint on storage1 only changes network reachability and does not assign the required Azure RBAC data-plane role to the system-assigned managed identities of VM1 and VM2.
Question
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.
You have an Azure subscription that contains two virtual machines named VM1 and VM2. Each virtual machine has system-assigned managed identity enabled.
You have an Azure Storage account named storage1. Public access from all networks is enabled for storage1.
You need to ensure that VM1 and VM2 can access storage1.
Solution: You create a private endpoint on storage1.
Does this meet the goal?
Key Takeaways
It tests the separation between network reachability and Azure RBAC authorization for storage, and the trap is assuming a private endpoint automatically grants managed identities data-plane access.
This SC-500 scenario tests whether a private endpoint on storage1 is enough for VM1 and VM2 to access it using system-assigned managed identities; the answer is no, because role assignment is still required.
Common mistake: Choosing Yes because a private endpoint makes storage1 reachable ignores that VM1 and VM2 still need an Azure RBAC data-plane role such as Storage Blob Data Reader on storage1.
Expert Analysis
Network reachability is not authorization
Creating a private endpoint on storage1 gives the storage account a private IP address in a chosen subnet, but it does not grant any security principal permission to read or write data. The scenario already says public access from all networks is enabled, so the VMs can reach the public endpoint; the private endpoint changes the path, not the authorization decision. The correct choice is B. No.
The managed identities still need a role assignment
System-assigned managed identities on VM1 and VM2 only create Microsoft Entra service principals. They do not automatically receive Azure RBAC permissions on storage1. To access blob, file, queue, or table data, each identity must be assigned the appropriate data-plane role—for example Storage Blob Data Reader or Storage Blob Data Contributor—on the storage account or a narrower scope. Without that assignment, the VMs can authenticate but the storage service returns an authorization failure. A useful comment on this item makes the same point: the private network may permit traffic, but the managed identity must be assigned to a role in the storage account.
What would flip the answer
The solution would meet the goal if it also assigned a suitable storage data-plane role to both managed identities and, for reliable private endpoint use, configured private DNS so the VMs resolve storage1 to the private IP. If the requirement were only to prevent public network access rather than to authorize the VMs, the analysis would shift toward network controls such as private endpoints, firewall rules, and public network access settings. For this question's wording—ensure that VM1 and VM2 can access storage1—authentication and authorization are both required.
Operational consequence
If you deploy only the private endpoint, the VMs will likely receive HTTP 403 authorization errors even though network connectivity looks correct. Teams then waste time checking NSGs, route tables, and private DNS when the missing piece is an RBAC role assignment. Treat private endpoint and managed identity as separate controls: one controls the route, the other controls the permission.
Official Reference
- https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-access-azure-active-directory
- https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview
- https://learn.microsoft.com/en-us/azure/storage/common/storage-auth-aad
These links open the official vendor documentation in a new tab.
Exam Strategy
When a solution says create a private endpoint or enable managed identity, separate the network path from the authorization path. For Azure Storage, ask who or what is the principal, and whether that principal has been assigned a data-plane RBAC role on the exact resource. A private endpoint never assigns permissions, and enabling an identity never grants it. In Yes/No solution sets, reject any option that stops at connectivity when the requirement says access to data.
Frequently Asked Questions
Does a private endpoint on storage1 grant VM1 and VM2 access to blob data?
What would flip this solution to Yes?
Why does enabling a system-assigned managed identity not grant storage access?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
volto 👍 1 Answered BFor the VM to access the storage, you must assign the system-assigned managed identity to a role in the storeage. The private network applies to the network. Network traffic is now possible.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-500 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SC-500 Practice Test →