This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(224.00000000000003, 3%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELJ%3C/text%3E%3C/svg%3E)
Hi Team,
I have observed the Naming convention of Azure AD is not replaced with Entra ID. When I am trying download the PIM roles from PIM-> Manage Roles -> Export, the role 'Azure AD Joined Device Local Administrator' is still showing as Azure AD.
The role 'Microsoft Entra Joined Device Local Administrator' showing correctly in Azure Portal.
Please correct the Naming convention from 'Azure AD' to 'Entra ID'.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello Lavanya,
Thank you for posting your query on Microsoft Q&A.
We appreciate your insight; I have replicated the issue in my environment and observe the same behavior.
The role "Azure AD Joined Device Local Administrator" still reflects the old Azure AD naming convention when exporting roles in Privileged Identity Management (PIM). This is indeed due to the ongoing transition from Azure AD to Entra ID.
Currently, certain components and tools, including role exports and role definitions, may not have been fully updated across all areas of the Azure ecosystem. Microsoft is rolling out these updates gradually, which means that while some areas might reflect the new Entra ID naming, others, such as role names in PIM, may still show the older Azure AD terminology for the time being.
If this naming issue is impacting your usage or workflows, we recommend submitting feedback to Microsoft. This will help prioritize the updates to the naming conventions and bring the changes to your environment sooner.
Feedback and ideas:
https://feedback.azure.com/d365community This is something that our product team keeps a close eye on.
Please note that Microsoft is actively working on updating the role names across services, and these updates may take some time to fully propagate across all tools and portals, including PIM.
I hope this explanation helps clarify the situation. If you have any further questions or need assistance with any other issues, feel free to reach out.
Regards,
Sakshi Devkante
Hello Lavanya,
Just making sure if the information above was useful. Please do not hesitate to reply if you have any other information regarding this matter.
Hello Lavanya,
I hope you're doing well! I just wanted to follow up and check if the information above was useful regarding Azure AD is not replaced with Entra ID. If you have any further questions or need additional assistance, please feel free to reach out.
![](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(217.60000000000002, 24%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Hello Lavanya,
Thanks for your observation.
These changes can be rectified by the product team. You can provide a feedback for them. To do this:
Go to Entra Admin center with administrative credentials.
In the lower-right corner of the portal, select the Help & Support icon and then choose Give feedback.
You can then proceed to provide the team with this feedback
You can mark it 'Accept Answer' and 'Upvote' if this helped you
Regards,
Abiola