Question

A retail company is building end-to-end test scenarios for a Copilot Studio agent that spans Dynamics 365 Customer Service and Dynamics 365 Finance. The QA team wants to run realistic multi-app test cases in a non-production environment using representative customer records, but the compliance team flags that the source data contains PII and financial account numbers subject to strict handling rules. The architect must define the test data management approach that enables realistic end-to-end validation while satisfying compliance. What should the architect recommend?

Accepted Answer

Generate a masked/anonymized dataset that preserves referential integrity and realistic distributions across the Customer Service and Finance apps, and use it as the seeded test data in the non-production environment

Answer

Copy the full production Dataverse and Finance data unchanged into the test environment so test cases exercise real edge cases, restricting access to the QA team only

Answer

Skip using representative records entirely and have testers type freeform inputs during each test run to avoid storing any sensitive data

Answer

Point the non-production agent directly at the production data sources during test execution so no sensitive data is duplicated