Dataverse Auditing and Activity Logging for Regulated Record Keeping

Organisations in aged care and government increasingly hold their most sensitive case records inside Dynamics 365 and the Microsoft Dataverse platform that underpins it. These records document decisions about vulnerable people, eligibility determinations, incident handling, and the handling of personal information, all of which may later be examined by regulators, courts, commissions of inquiry, or internal integrity functions. When that scrutiny arrives, the ability to demonstrate who viewed, created, altered, or deleted a record, and when they did so, becomes just as important as the record itself.

Dataverse provides native auditing and activity logging capabilities that can capture this evidence without bolting on third party tooling. Configured correctly, these features help satisfy recordkeeping and evidentiary obligations while remaining within the Microsoft trust boundary. Configured poorly or left at default settings, they can leave gaps that only become apparent when an organisation is asked to produce a reliable audit trail and cannot. Understanding the distinctions between the available mechanisms, and planning for retention from the outset, is therefore essential for any regulated workload.

Why Audit Trails Matter for Sensitive Case Records

Recordkeeping obligations in the Australian public sector and in aged care flow from several overlapping sources, including the Archives Act and associated records authorities, the Privacy Act, sector specific standards, and the evidentiary expectations of tribunals and courts. Many of these frameworks do not merely require that records exist; they require assurance that records are complete, authentic, and have not been altered without a traceable history. An audit trail that records changes to a case record provides exactly this assurance, converting a static dataset into evidence of process and accountability.

For aged care providers managing care plans, clinical notes, and complaint records, and for government agencies managing case files and benefit determinations, the risk is not only external regulatory exposure. Internal integrity depends on being able to identify inappropriate access to sensitive information, detect tampering, and reconstruct the sequence of decisions. A well designed audit capability supports investigations, responds to freedom of information and subject access requests, and demonstrates good faith compliance to oversight bodies that expect organisations to monitor their own systems.

How Dataverse Auditing Works

Dataverse auditing operates through a layered model that must be enabled deliberately at each level. Auditing is first switched on for the environment, which acts as a master control. It is then enabled on individual tables, and finally on specific columns within those tables, so that an organisation can capture changes to the fields that matter without generating noise from fields that do not. Once configured, Dataverse records create, update, and delete operations, including the previous and new values of changed fields, together with the user and timestamp associated with each event.

This granularity allows a thoughtful configuration that balances evidentiary completeness against storage cost and signal clarity. For a clinical or case management table, an organisation might audit status changes, assessment outcomes, and key identifying fields while excluding transient or system managed columns. It is worth noting that standard change auditing captures modifications rather than simple read access, so viewing of a record is handled separately. Planning which tables and columns to audit should be driven by a records authority and a privacy impact assessment rather than enabled indiscriminately across the entire data model.

Activity Logging and Access Tracking

Capturing who read a record, as opposed to who changed it, requires activity logging that surfaces through Microsoft Purview rather than through the Dataverse change audit history alone. This read access logging is particularly relevant for sensitive case records, because unauthorised viewing of personal information can itself constitute a privacy incident even when no data is altered. Activity logging records events such as record access and export, allowing security and compliance teams to investigate patterns of access from within the unified audit experience.

Access to Dataverse activity logging through Microsoft Purview depends on appropriate licensing and configuration, and organisations should confirm their entitlements before relying on it for compliance. Because read logging can generate substantial volumes of events, it benefits from clear scoping and from alerting rules that highlight unusual behaviour rather than requiring analysts to review every event manually. Combining change auditing with access logging gives a more complete picture, covering both the integrity of records and the propriety of access to them.

Retention, Storage, and Evidentiary Integrity

An audit trail only satisfies recordkeeping obligations if it is retained for as long as the underlying records must be kept, which in government and aged care contexts can extend for many years or decades. Dataverse audit data consumes log storage capacity within the environment, so retention planning has a direct cost and governance dimension that should be understood early. Dataverse now provides configurable retention settings for audit logs, allowing organisations to align log retention with their records authorities rather than accepting a single default period.

Where retention requirements exceed what is practical to hold in the live environment, organisations should design an export and archival strategy that preserves the authenticity and integrity of the exported data. This includes controlling who can disable auditing or purge logs, since the value of an audit trail collapses if privileged users can quietly remove it. Applying least privilege to audit administration, documenting the configuration, and periodically verifying that auditing remains enabled all contribute to an evidential chain that will withstand external examination. Treating the audit configuration itself as a governed, reviewed asset is the practical difference between a trail that supports accountability and one that merely appears to.

References

• Manage Dataverse auditing - Microsoft Learn
• Dataverse activity logging - Microsoft Learn