Question
A company uses Power Apps. You enable auditing in Microsoft Dataverse.
Users report the following issues when viewing the audit logs:
• Unable to view the read access audit logs.
• Unable to view the Account table audit logs.
You need to troubleshoot the issues.
What are the causes of the issues? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Explanation
Unable to view the read access audit logs: Auditing is not enabled at the environment level. Read-access logging (Log access and Read logs) is configured in the environment's auditing settings in the Power Platform admin center and only works when auditing is started for the environment, so read access entries are written only after auditing is turned on at that level. Storage over capacity affects creating and copying environments, not whether existing audit entries can be viewed.
Unable to view the Account table audit logs: Auditing is disabled at the table level. Even with environment auditing on, each table must have auditing enabled in its properties before changes to its rows are recorded, so an Account table with auditing off has no audit history. There is no app-level auditing setting in Dataverse, and read-access auditing does not control whether a table's change history is recorded.
