CRM 2013 – MB2-703 – Quick Overview of Auditing

Auditing was added to CRM in version CRM 2011, it was a good move from Microsoft because this was a much requested feature and in CRM 4 it was mainly done using a auditing plugin.

Auditing is one of the straight forward features in Microsoft which does a good job of just working, doing what you need and rarely going wrong.

Auditing is set at various levels

Global settings – do you want to audit

Entity level – what entities do you want to audit

Field Level – what fields on the enabled entities to Audit

You can also audit users, when they log into CRM, when security roles are assigned to the user.

The auditing functionality can be found by going to

Settings – Auditing

Then you can click Global Audit settings

This allows you to start auditing, notice there is also a section for user auditing.

User auditing can be turned on or off, you can change what is audited.

Enabling auditing in the common areas is a way to turn auditing on for groups of entities and fields.

Once you have turned on auditing you can then choose to audit individual fields

Auditing Table

After you have enabled auditing all the auditing changes will be  held in the audit tale in CRM Database.  It will store the user who triggered the event, what type of event and the date of time.

Auditing Key Features:

Any entity can be audited

if auditing is not enabled at organisational level, it doesn’t matter if auditing is turned on at an entity level, nothing will be audited.

audit logs are partioned every 3 months.  These can be  deleted in the audit log management screen

User has to have the View Audit History privilege

when you turn on auditing for an entity, all the available fields are enabled for auditing

Some System fields are not applicable for auditing

• CreatedOn
• CreatedBy
• ModifiedOn
• ModifiedBy
• Owning Business Unit
• Owning User
• Customer AddressId

To see a detailed list of is audited go the CRM SDK Auditing Overview