Power Platform Governance and Administration

Currently, there is no centralized dashboard available to track audit log settings and retention periods across environments in Power Platform. This creates a visibility gap for administrators who need to monitor and manage data governance effectively.

We’ve observed the following:

• Audit logs can have their retention period set to "forever", which may lead to excessive Dataverse storage usage if not regularly monitored.
• At present, admins must manually access each environment’s settings to review audit log status and retention configuration.
• There is no consolidated view to track Dataverse audit log usage, retention periods, or potential overuse risks.

We propose a feature enhancement to include a dashboard in the Power Platform Admin Center that provides:

• A summary view of audit log status and retention periods for each environment.
• Alerts or indicators for environments with indefinite retention settings.
• Usage statistics showing how much Dataverse space is consumed by audit logs.
• Add two new actions(get audit settings and update audit settings) in the PowerPlatformforAdmins connector.

This would enable admins to take proactive measures for capacity planning and ensure compliance with internal data retention policies.

Thank you for considering this request.

Issue:

Attachments need to be exported separately from their parent records, which requires re-setup of relationships, consumes time, and more often than not, it can mess up data

Suggestion:

Please implement some out-of-box methods to allow attachments to be exported along with the "main" table as one entity. One current suggestion is to make it so that attachments are "bonded" with the records that contain them, as a field instead in addition to being saved in a table and using a pointer.

Benefits:

• Reduce time commitment
• Ensures data integrity
• Frees the relationship to the attachments table
• Eliminates a lot of the requirement to use third party tools

Ideas:

1. Allow administrators to exclude one day per week to accommodate weekly after hours deploys.
2. Shrink the 9 hour requirement or make it variable so customers have more flexibility to install solutions after hours

Currently, the maintenance window settings for production environments require you to have 9 hours available every day of the week for Microsoft-owned solutions to install. Microsoft recommends administrators deploy to prod after hours. However, with the limited maintenance window settings we have access to, if we deploy at 10pm and open for business at 7am, Microsoft's maintenance window gets in the way and blocks us from importing solutions.

Thanks!

When using the API call to "/api/data/v9.0/organizations", the value for "auditretentionperiod" does not reflect the audit retention period setting in admin center. However, the value is updated correctly for "auditretentionperiodv2", which can cause confusion to customers. The "auditretentionperiod" attribute should be removed to avoid confusion.