Ability to rename EntraID GUID-based NextCloud user groups

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Feature request

Friendly name overlay for GUID-based EntraID to User_OIDC groups mapping.

Which Nextcloud Version are you currently using: (see administration page)
Hub 9 30.0.4

Is your feature request related to a problem? Please describe.
EntraID -> OpenID connect user backend groups mapping is in GUID, cannot rename groups in the Admin GUI.
When we rename the imported groups in NextCloud upon subsequent user login the groups are renamed to their GUID.
We've tried different context, etc. but even with SAM account names, GUID is the default.

Describe the solution you'd like
We'd like a way to maintain the back-end GUID mapping EntraID to User_OIDC by apply a friendly name for use in NextCloud.
it would be best if the group could be renamed as with any other group, but maintain the provisioning with EntraID.

Describe alternatives you've considered
We've tried other OID software but so far this works the best to provision users and groups via EntraID SSO integration.

Additional context
Using friendly names - Folder01 & Folder01-Admin - are easier and less error-prone than using GUID for Administrators.
As users can see what groups they are a member of in their personal settings/profile page they can more easily see what groups they are/are not in using a friendly group name.
Folders have owners, they don't know what a GUID represents, they are used to "friendly" folder names (as with file servers, DropBox, teams, etc.).

We create specific EntraID groups that are specific for nextcloud users.
We map users to these groups in EntraID
The groups are propagated to NextCloud via the User-OIDC integration.
The group names appear in the NextCloud GUI as GUID.
We match GUID to a friendly name, temporarily rename the new group.
We assign that group to a shared groups folder with the correct permissions.
This way we can manage user provisioning in EntraID, have that flow through to NextCloud for user, group and user file group matching.

If this is possible in User-OIDC today please let us know!

No files, tests, or entry points are identified in the issue. Start by tracing User-OIDC group mapping during user login, then determine how EntraID GUIDs are stored and refreshed; done would preserve that provisioning while presenting a stable friendly group name in Nextcloud.