Dio Nguyen

Problem Statement:

Currently, the Dataverse Audit table is read-only — audit records can be retrieved and exported but cannot be written or imported into another environment's native audit store. This creates a significant gap for organizations that need to migrate audit history between environments, especially during environment copy, migration, or consolidation scenarios.

If a customer performs an environment copy without enabling the "Copy audit logs" option at the time of the copy, there is no supported way to transfer audit data afterward. This is a critical limitation for organizations with strict regulatory and compliance requirements that mandate full audit trail continuity.

Real-World Scenario:

An organization migrates from a source environment to a new production environment. After the migration, they realize that millions of historical audit records (e.g., for work orders, cases, or financial data) were not carried over. Since the new production environment is already in active use with new transactions, performing another environment copy is not feasible without losing post-migration data.

Current Workarounds:

• None available. The Audit table does not support data import through any supported API, SDK, or manual process.
• Re-performing an environment copy would overwrite all new data created since migration.

Suggested Idea

We recommend Microsoft consider one or more of the following enhancements:

1. Post-Copy Audit Log Transfer Tool: Provide a supported mechanism (via Power Platform Admin Center or API) to transfer audit log data from a source environment to a target environment after the initial environment copy has been completed.
2. Audit Data Import API: Enable a write/import capability for the Audit table in Dataverse, allowing organizations to programmatically migrate historical audit records between environments while preserving data integrity.
3. Selective Audit Log Merge: Allow administrators to merge audit logs from a source environment into an existing target environment without overwriting existing audit data in the target.
4. Enhanced Copy Environment UX Warning :Add a more prominent warning or confirmation step during environment copy to alert administrators about the consequences of not enabling audit log copy, helping prevent accidental omission.

Business Impact

• Compliance Risk: Organizations in regulated industries (healthcare, finance, government) may face audit failures or legal exposure if historical audit trails are lost during migration.
• Data Continuity: Audit history is essential for traceability, accountability, and root cause analysis across environment transitions.
• Customer Confidence: Providing robust audit migration capabilities strengthens trust in the Dynamics 365 / Power Platform ecosystem for enterprise-grade deployments.

Problem

When creating or editing emails in Customer Insights – Journeys, users may experience unexpected loss of cursor focus in the Subject or Preview Text fields—especially when pressing the SPACE key during the initial typing phase.

This occurs because certain background initialization processes (such as enabling/disabling header fields like From Name and From Email) are triggered only after user interaction. As a result, even after clicking into the Subject or Preview fields, the form may still be initializing, causing focus to shift unexpectedly.

Impact

• Disrupts the email authoring experience
• Breaks typing flow and user concentration
• Leads to frustration for users who frequently create or edit emails
• Impacts productivity and perceived stability of the email editor

This behavior is especially noticeable for marketing and operations teams who rely heavily on rapid email creation.

Current Behavior

• Background initialization starts only after field interaction
• No supported way to trigger initialization earlier
• Focus loss can occur even if the user waits briefly before typing
• Behavior stops only after initialization completes

Proposed Improvement

Introduce one of the following enhancements:

• Pre‑initialize background processes automatically when the email form loads, before user input begins
• OR
• Visually indicate form readiness (e.g., temporary loading or disabled input state) until initialization completes
• OR
• Temporarily lock Subject/Preview input until the form is fully initialized

Benefits

• Smooth and predictable typing experience
• Reduced user frustration
• Improved usability and confidence in the email editor
• Better alignment with modern UX expectations