Azure User-Assigned Managed Identity Regional Scope
You have an Azure subscription that contains a user-assigned managed identity named Managed1 in the East US Azure region. The subscription contains the resources shown in the following table. Which resources can use Managed1 as their identity? - 
Community Votes
55% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the understanding that while user-assigned managed identities are created as regional resources, their associated service principal is available globally for use by any supported resource type.
Determines which Azure resources can utilize a user-assigned managed identity regardless of geographic region, establishing that the identity's scope is global. This page clarifies that VMs, Storage Accounts, and Web Apps all support this feature.
Selecting Option C (VM1 and WebApp1 only) because learners incorrectly assume that Storage Accounts cannot be assigned managed identities or confuse regional creation with usage restrictions.
Community Discussion (17 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Correct answer: D — VM1, storage1, and WebApp1. User-assigned managed identities are Azure resources that can be granted to one or more Azure services. While the managed identity object itself is stored in a specific region (East US), the underlying Microsoft Entra ID service principal it represents is available globally. Therefore, any Azure resource that supports managed identities—such as Azure Virtual Machines (VM1), Azure App Service (WebApp1), and Azure Storage Accounts (storage1)—can be assigned this identity regardless of the resource's own region. The key constraint is resource type compatibility, not geographic proximity.Why the Other Options Are Wrong
Option A is incorrect because both VMs and Storage Accounts can also use managed identities. Option B is incorrect because VMs are fully supported users of managed identities. Option C is incorrect because it excludes Storage Accounts; many learners mistakenly believe storage accounts do not support managed identities, but they do for authentication purposes. The confusion often stems from thinking about RBAC roles versus the identity assignment capability.Community Comment Notes
Community discussion shows a split between options C and D. Several users pointed out that storage accounts cannot be 'actors' in certain contexts, leading them to choose C. However, others cited official Microsoft documentation confirming that user-assigned managed identities are usable across regions and by storage accounts. One commenter noted that the service principal is global, which directly supports the correct answer D. Another user highlighted that the video overview confirms storage account compatibility.Official Reference
Exam Strategy
When analyzing managed identity questions, distinguish between the creation location (regional) and the usage scope (global). Always verify if the target resource type (e.g., Storage, VM, App Service) supports managed identities, as this is the primary filter rather than region matching.
Frequently Asked Questions
Are user-assigned managed identities restricted to the region where they are created?
No. While the identity resource is stored in a specific region, the associated Microsoft Entra ID service principal is available globally.
Can an Azure Storage Account be assigned a user-assigned managed identity?
Yes. Azure Storage Accounts support both system-assigned and user-assigned managed identities for authentication.
Related Analysis
Practice All SC-300 Questions
Access 80 questions with complete answers and detailed explanations.
View Full SC-300 Practice Test →