The Dataverse auditing feature is designed to meet the external and internal auditing, compliance, security, and governance policies that are common to many enterprises. Dataverse auditing logs changes that are made to customer records in an environment with a Dataverse database. Dataverse auditing also logs user access through an app or through the SDK in an environment.
Dataverse auditing is supported on all custom and most customizable tables and columns. Audit logs are stored in Dataverse and consume log storage capacity. Audit logs can be viewed in the Audit History tab for a single record and in the Audit Summary view for all audited operations in a single environment. Audit logs can also be retrieved using the web API or the SDK for .NET. Audit logs are created when there are changes to the record on a table where auditing is turned on. Audit logs for updates are created when a new value is different from the old value of a column.
There are three levels of settings to enable / disable Audit feature.
- Global
Audit Setting in System Settings: This is the master switch. If auditing
is off at the system level, no table-specific settings or field settings
will apply. System-level auditing must be enabled for any table or
field-level auditing to work.
Option
1: System setting.
Option 2: Power Platform Admin portal:
- Table-Level
Auditing: When you enable auditing for a table, it initially turns on
auditing for all columns within that table. This provides an easy way to
activate auditing for an entire table, but it can be refined further.
- Field-Level Auditing:
By default, enabling table-level auditing will also enable auditing for all fields in that table. If you only want to audit specific columns, you’ll need to manually disable auditing on each unwanted field, as there’s no bulk “turn off” option for fields in a table.
More detail can refer
to: https://learn.microsoft.com/en-us/power-platform/admin/manage-dataverse-auditing
No comments:
Post a Comment