Correct resource reference of principalId on Microsoft.ManagedIdentity/userAssignedIdentities

[jonasanker]

Code example incorrectly references the principalId. It's available under properties.principalId

[prmerger-automator]

@jonasanker : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit f65863d:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details
articles/role-based-access-control/role-assignments-template.md	💡Suggestion		Details

• [Error: moniker-range-out-of-scope] Step 'RunPowershellScript' finishedrror

articles/role-based-access-control/role-assignments-template.md

• Line 9, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'rolyonpri' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

Learn Build status updates of commit 444c275:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/role-based-access-control/role-assignments-template.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

This PR corrects a documentation error in an Azure Resource Manager (ARM) template example that shows how to reference the principalId property of a user-assigned managed identity.

• Fixes incorrect property path for accessing principalId in ARM template reference function
• Updates documentation to show the correct nested property path: properties.principalId

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[ttorble]

@rolyon

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team