Here we start Auditing and what can be audited.
What is auditing?
In Microsoft Dynamics CRM 2011, the auditing feature logs changes that are made to your customer records so that you can review those changes later. The auditing feature is designed to meet the auditing, compliance, security, and governance policies of many regulated enterprises.
The audit logs help you answer questions such as:
• Who updated this field value on this record, and when?
• What was the previous field value before it was updated?
• What actions has this user taken recently?
• Who deleted this record?
What can be audited?
The following operations can be audited:
• Create, update, and delete operations on records.
• Changes to the sharing privileges of a record.
• The N:N association or disassociation of records.
• Changes to security roles.
• Audit changes at the entity, attribute, and organization level. For example, enabling audit on an entity.
• Deletion of audit logs.
• When (date/time) a user accesses Microsoft Dynamics CRM data, for how long, and from what client. See the Auditing user access section
Limitations on auditing
The auditing feature does not track the read operations, that is, when a user views a record by any means (forms, views, charts, reports, Advanced Find, or Export to Excel), no audit operation is recorded in the audit log.
The audit data is not available for reporting, querying with Advanced Find, or exporting to Excel.
Auditing is available for all custom and most customizable entities, but auditing is not supported on the note and attachment entities.
Auditing is not available for most customization changes such as creating, modifying, or deleting a solution component. Audit Summary View and Audit History View are not customizable.
This lesson is a part of Auditing in CRM 2011 chapter from MB2-866 Microsoft Dynamics CRM 2011 Customization and Configuration Prep course. More lessons in this chapter are
The Practice tests included in this course are: