Problem Description

In Dynamics 365 Finance and Operations, Database Log is a critical standard function used to ensure audit trails for data changes, especially in regulated industries such as pharmaceuticals.

Based on confirmation from Microsoft Support, the following behavior currently exists:

• Enabling Database Log settings (turning logging ON) is recorded.
• Disabling Database Log settings (turning logging OFF or deleting log settings) is not recorded in any audit trail or Database Log.

This means that it is technically possible for a user with sufficient privileges to disable logging without leaving any trace, which represents a significant compliance risk.

Business & Compliance Impact

For GxP / CSV-compliant systems, the ability to track who, when, and what was changed is mandatory—not only for business data, but also for audit-relevant configuration such as logging settings themselves.

If configuration changes that disable audit logging are not auditable:

The system cannot fully meet regulatory expectations (e.g., data integrity, ALCOA+).

Companies may be forced to rely on procedural controls only, which are insufficient without technical enforcement.

In the worst case, this may impact the feasibility of using Dynamics 365 FO as an ERP platform in regulated environments.

Requirements

We strongly request that Dynamics 365 Finance and Operations be enhanced so that all Database Log configuration changes, including but not limited to:

• Enabling logging (ON)
• Disabling logging (OFF)
• Deleting Database Log settings
• Adding or removing tracked tables or fields

are fully recorded in an audit trail, including:

• User who performed the action
• Date and time of the change
• Details of the change (e.g., ON → OFF)

Given the critical impact on regulatory compliance and data integrity, we strongly request that this enhancement be implemented within the current fiscal year.

This should be provided as a standard product feature, without requiring custom development.