Dataverse Long Term Retention

I would like to propose a new feature for the Power Platform Admin Center that enables administrative users to export a comprehensive list of users within a selected environment, along with their:

• Security roles
• Associated licenses
• Environment access
• Other relevant user metadata (e.g., business unit, access mode, etc.)

This feature should include a customizable view, allowing administrators to:

• Select which columns they want to include (e.g., email, roles, license type, etc.)
• Apply filters to narrow down specific user groups
• Export the data into formats like CSV or Excel for audit or reporting purposes

Why this matters:

Today, gathering this type of information involves switching between multiple tools (Admin Center, Dynamics 365 settings, Azure AD, etc.), and often requires technical knowledge or custom scripts. Providing this functionality in a centralized, user-friendly interface would:

• Streamline administrative and audit tasks
• Improve security and compliance visibility
• Save time for administrators and IT teams
• Enhance governance, especially in large or multi-environment tenants

Suggested Features:

• Environment picker to scope the export
• Role-based filtering (e.g., show only users with “System Admin” role)
• Ability to sort and group by user attributes
• Export button with format options
• Scheduled export or API access (optional but very valuable for automation)

If you agree this feature would be helpful, please upvote and comment to show support!

We are using Form Component Control to show a sub-form on the main form. The main form contains a lot of fields, and the sub-form is placed at the end of the main form. We have some mandatory fields on the sub-form, and if the screen is too small, then the mandatory fields validation is skipped on save, thus letting the user save the record without having all the mandatory fields filled in. We noticed that if you scroll the main form a little bit, then the sub-form loads and all the mandatory fields work as expected.

As I understood, this is expected, because the validation is done on the client side and only the visible part is rendered, but I don't think that this is a good design, considering that we can have mandatory fields in the sub-form.

Proposal:

Either don't let makers have mandatory fields in the sub form or make a toggle to forcefully render the sub-form in the UI, so it is properly validated.