![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 25%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENU%3C/text%3E%3C/svg%3E)
Azure Role-based access control
An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
927 questions
Hi,
User assigned Managed identities (Managed Identities) are standalone Azure resource and when you check that view it shows only those resources. System assigned managed identities are not standalone resource, they are part of the resource to which are created for so they are not visible under Managed Identities. As managed identities are standalone resource they can exists on your own and can be assigned to multiple resources where the system assigned managed identities cannot live on their own and are deleted with the resource as well. They also cannot be assigned to other resources. You can use the following Azure Resource graph query to see resource that have system assigned identity:
resources | where identity.type contains "SystemAssigned"
Note that resources table does not cover all Azure resources. Some resources have their own table so you will need to check if there are other resources in other tables that can have system assigned identities and you are interested into them. Here is another example for policy assignments with system assigned identities:
policyresources
| where type =~ 'microsoft.authorization/policyassignments'
| where identity contains "systemAssigned"
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.