Tracks Case, Contract, Queue, and Service entity activity. Tracks sales-related entities like Competitor, Opportunity, Invoice, Order, and Quote. Tracks common entities like Account, Contact, Goal, Product, and User. To start or stop auditing on specific entities, select or clear the following check boxes: Select System Settings, and then select the Auditing tab. In the web app, go to Settings ( ) > Advanced Settings. More information: Dataverse developer guide: Configure auditing > Configure organization settings Set specific areas of the product to audit Changing the retention period will not change already existing audit logs and is only applied to newly created audit logs. You can also change the audit retention value using the Dataverse Web API.Д®ach audit log is stamped with the currently active retention period. The default audit retention period is 30 days for new environments and existing environments without any audit data. When new features are deployed, the audit retention period is set to Forever for all Dataverse environments with existing audit data. The audit data retention policy will be visible once your environment has been upgraded. Under Retain these logs for, choose the period of time you wish to retain the logs. You can set a retention period for how long audit logs are kept in a Microsoft Dataverse environment. Logs will be sent to the Microsoft 365 Security and Compliance Center Log whenever the system is accessed, generally by signing in Go to Environments > Settings > expand Audit and logs > Audit settings. This task requires the system administrator or customizer security role or equivalent permissions.Д«rowse to the Microsoft Power Platform admin center and sign in using administrator credentials. Start/stop auditing and set retention policy When you start auditing again, the same auditing selection is maintained that was previously used. Stopping auditing stops tracking for the organization during the period until auditing is started again. Additionally, you may want to stop auditing for maintenance purposes.

You can delete audit logs by going to Settings > Auditing > Audit Log Management. System administrators and customizers can start or stop auditing for an organization.ДЇor Customer Engagement (on-premises), you may notice that auditing can significantly increase the size of the organization database over time. For changes made to entity fields that can be localized, such as the Product entity name or description fields, the locale ID (LCID) appears in the audit record.

For example, enabling audit on an entity. Audit changes at the entity, attribute, and organization level.The N:N association or disassociation of records.Changes to the sharing privileges of a record.Create, update, deactivate, and delete operations on records.What locale was used to make the update?.What actions has this user taken recently?.What was the previous field value before it was updated?.Who updated this field value on this record and when?.Which user was accessing the system and when?.

The audit logs help the administrator answer questions such as: The auditing feature is designed to meet the auditing, compliance, security, and governance policies of many regulated enterprises. The auditing feature logs changes that are made to customer records and user access so you can review the activity later.

User logon activity audit