Microsoft Graph permission GUIDs now resolve in Azure AD assignments
Bug fix: azuread_app_role_assignment resources rendered most Microsoft Graph permission GUIDs raw (e.g. 🛡️ fb221be6-…) because the bundled lookup table only covered 131 of the well-known application permissions. The mapping has been regenerated from the Microsoft Graph permissions reference and now covers all 673 Microsoft Graph application permissions, so common roles such as Policy.ReadWrite.Authorization show by name in both summary lines and attribute tables.
🐛 Bug fixes
- Well-known Microsoft Graph application permissions now resolve to their display name in
azuread_app_role_assignmentsummaries and theapp_role_idattribute row. Previously only 131 GUIDs were recognized; 542 additional Microsoft Graph application permissions (includingPolicy.ReadWrite.Authorization,RoleManagement.ReadWrite.Directory,Sites.FullControl.All, and others) rendered as raw GUIDs. - Corrected entries that pointed at the delegated GUID instead of the application GUID for several roles in the previous hand-curated list (for example
AuditLog.Read.All), so the resolved name now matches what the Azure portal and Graph API report.
📚 Documentation
- New
CONTRIBUTING.mdsection "Maintaining Microsoft Graph App Role Mappings" documents the newscripts/update-msgraph-app-roles.pyregeneration script (stdlib-only,--source/--output/--dry-run). docs/features.mdclarifies the scope of the GUID resolution: Microsoft Graph application permissions only — delegatedoauth2PermissionScopesand non-Graph APIs (SharePoint, Exchange, Office, Intune, ARM, …) are intentionally out of scope.
🔗 Commits
1b7a35edocs: add issue analysis for missing msgraph permission name mappings (#120)157223dchore(scripts): add update-msgraph-app-roles.py generator (#120)7f43e67fix(azure): map well-known Microsoft Graph permission GUIDs to display names (#120)5d54f0edocs: document expanded Microsoft Graph permission mapping (#120)