IT systems · Practical guide

Dataverse auditing for GxP: tables, fields and retention

Auditing is active in the Dataverse environment, but a critical field still has no history. Align the configuration and data model with the traceability needed, including later display and retention of entries.

Table of contents

At a glance

What do you need to check for GxP auditing in Dataverse?

Check that auditing is enabled at environment, table and column level, relevant critical events are captured and the right people can access the history. Assess administrative changes, retention and review separately. Data-change auditing, access logging and activity logging are different functions and do not collectively demonstrate completeness without assessment.

Consider the data process, not just the audit switch.

The Dataverse can serve as the data platform for a Power Apps application or other Dynamics processes. For GxP evaluation, the relevance depends on the records generated there and the decisions they support. A general CRM dataset and a quality-related test dataset do not require the same assessment.

This guide addresses the current Dataverse Online documentation. Variant products and on-premises versions may feature different functionalities. Document the environment, app type, tables, extensions, and relevant technical identifiers. The actual configuration in use remains the subject of review.

Annex 11 and PIC/S provide the regulatory and data integrity framework. The following configuration and inspection recommendations are derived independently. A manufacturer's note that auditing may support compliance does not constitute confirmation that the specific process meets all requirements.

Sources: [1] [2] [3]

Demonstrate three configuration levels jointly

Microsoft describes activation at environment, table, and column levels. Therefore, for each critical field, it is verified whether the required levels are appropriately enabled. Global environment switching alone is insufficient as a coverage justification.

Prepare a list of technical data including the table and column names with their technical identifiers. Display names may vary and are not always unique. Note whether a field is standard, customer-specific, calculated, or otherwise special. Manufacturer documentation indicates support for custom and highly configurable tables and columns; verify specific support capabilities.

Apply auditing settings consistently across development, testing, and production environments. A successful solution deployment should not be equated with an unverified assumption regarding any environment configuration. Compare the actual target state and generate the necessary evidence where required.

Sources: [3] [4]

Distinguish events from log types

Data change auditing can capture specific creation, modification, deletion, and other supported events. Schema changes and routine retrieval or export operations are not comprehensively covered by the same audit data set. For additional activities, Microsoft provides additional logging functions and prerequisites.

Therefore, each technical question must be linked to a specific source: Who changed the limit value? Who retrieved the data? Who modified a column definition? The answers may originate from different controlled procedures or protocols. Licensing, environment, and technical availability must be explicitly verified.

A change justification is also a standalone requirement. Verify that the application captures it and explicitly links it to the intervention. A separate comment lacking a secure reference to the change does not automatically provide the required rationale.

Example coverage matrix by process question
QuestionPossible source of evidenceAdditional inspection
Who modified a measurement value? Dataverse Data Change Auditing Table, column, old/new value, identity
Who deleted a record? Supported deletion event and its context Historical context remains clear
Who viewed or exported data? Appropriate additional activity logging License, environment, event scope, and objective to be verified
Who modified the data model? Controlled change and appropriate technical justification Not to accept automatically as captured by data audit
Why was it corrected? Functionality for reason of change Unique assignment and review

Sources: [3] [4] [1]

Example: a field remains unobserved outside the history log

In the example, an app stores sample P-31 with measurement value, unit, and decision status. The environment and table are activated for auditing. The decision status column was added subsequently and is not properly configured. A measurement value change appears in the history, but a status change does not. This example does not describe a defect in Microsoft Dataverse and is not a completed product test; the gap arises due to the configuration.

Therefore, field-based verification is performed. A duly authorized user first modifies the measurement value from 9.8 to 10.2 mg and then updates the decision status. A reviewer searches for both events. The example specifies that traceability of both changes must be demonstrated in relation to the sample. The absence of a status event is documented as a specific gap in coverage.

Retest both cases after the correction. Check other relevant fields and all methods used to write data so the cause is addressed wherever it occurs. If the system was already in use, assess the impact of the missing history separately. Enabling auditing now does not create records of past events.

Sources: [3] [1]

Test a change of retention using the actual procedure

The Microsoft documentation distinguishes between configuration paths. For the described setting, which assigns audit record entries with the currently active retention period, a subsequently modified value initially applies only to newly generated entries. Older entries retain their original retention period. At the same time, Microsoft references another configuration option via the Security tab, which enables an application to access existing logs.

Therefore, the general statement "Changes apply exclusively to new logs" is overly broad. Document the actual path, function, and version you are using. Specifically assess the impact on both existing and new entries. A longer visible standard retention period does not automatically confirm that existing data will be retained for a longer duration.

The retention example employs the initially described approach: entries during a short test period and entries following period extension are tracked separately. The required retention is based on the documented function. Such a test is planned in an appropriate test environment using non-critical test data; production-level history is not intentionally deleted.

Worksheet for changing a retention period
Data groupClarifying functionExpected evidence
Entries prior to the change Originally allocated deadline and chosen route of change Actual impact on existing logs
Entries after the switch Active deadline upon occurrence Appropriate treatment of new entries
Alternative Security Configuration Supported application on existing logs Targeted effect instead of assumption
Permission for manual deletion Roles and administrative functions Controlled Access and Intervention
Archived History Context, Readability and Searchability Usability over required duration

Sources: [3]

Test roles, history retrieval and review as a process

An existing audit dataset provides limited value if the responsible reviewer cannot access it or associate it with the correct process. Therefore, verify the actual review role using representative data. Administrator access is not a substitute.

Evaluate separately who can modify data, configure auditing, read history, and delete relevant logs. Technical administrator rights can be extensive. The required authorizations are granted on a controlled basis and their usage is appropriately monitored. A role designation alone does not indicate effective access.

The review considers meaning in the process, such as corrections following a decision or unusual status outcomes. Define the timing, scope, and handling of anomalies based on risk. An exported log file without professional evaluation is not a complete review.

Sources: [1] [2] [3]

Define specific acceptance criteria for the application

For each critical event, the initial state, action, expected history, and actual outcome are documented. Add entries for creation, modification, deletion, and the relevant application and interface pathways. Also verify missing authorizations and retrieval of older entries.

Clearly define boundaries. If an export event is not captured through the used function, the report must not claim complete access logging. Assess whether this statement is required for the specific process and identify an appropriate complementary solution.

Changes to the data model, solutions, roles, or retention settings trigger an impact assessment. Ongoing operations require an owner for audit configuration and a subject-matter responsible party for review. Only in this way is traceability maintained after the first project.

Sources: [1] [3]

Project experience and collaboration

Check the required change history for selected fields

With your application team, we list the changes a future reviewer must be able to explain and compare them against the Dataverse environment, tables and columns. For selected fields, we change a known value and trace it through to the readable history. A missing column may need a targeted configuration fix. Gaps in log types, retention or control of administrative changes may require a wider test and operating plan. We assign separate responsibilities for configuration and review of the records.

Frequent Questions on Dataverse Auditing

Is it sufficient to enable auditing in the Dataverse environment?

For data modifications, the required tables and columns must also be appropriately configured. Verify the actual event scope through targeted changes. A screenshot of the environment switch displays global settings but does not reflect the complete coverage of critical fields.

Sources: [3]

Are data exports recorded within the same audit trail?

Data change auditing is not equivalent to complete read-and-export logging. Microsoft describes additional activity logging functions with distinct prerequisites. Assign the required statement to a specific function and evaluate its scope within your environment.

Sources: [4] [3]

Does a new retention period automatically extend the retention of previous audit data?

Not applicable to every configuration path. For the record-specific deadline assignment described in the article, older data retain their previous deadlines initially. Microsoft also describes an alternative approach via the Security page for existing logs. Therefore, verify the actual impact on both legacy and new audit data, rather than inferring a uniform extension from the visible new value.

Sources: [3]

Can retrospective activation of auditing reconstruct missing history?

It does not generate retrospective audit events for previously unrecorded changes. Assess the significance of the gap and existing alternative reliable evidence. Going forward, configuration and test cases will be corrected; the past requires a dedicated technical evaluation.

Is a system administrator suitable as an audit reviewer?

Critical factors are professional competence, appropriate access, and the necessary independence of the control function. Administrative rights alone do not qualify for professional assessment. Additionally, evaluate potential conflicts of interest when the same individual performs relevant interventions and is responsible for their oversight.

Sources: [1]

Must every event include a reason for change?

For changes or deletions of GMP-related data, Annex 11, Section 9 requires a documented justification. This must be distinguished from arbitrary technical events. Define how the application captures the justification and uniquely assigns it to the relevant change. The presence of an existing standard audit function does not constitute evidence that this business requirement is met in your environment.

Sources: [1]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  3. Microsoft: Manage Dataverse auditingConfiguration, recorded events, limits, and different pathways to storage configuration; reviewed on 14.10.2026.
  4. Microsoft: Dataverse auditing overviewTechnical events and access to audit data.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →