A sandbox copied from production carries every customer's, vendor's and employee's personal data to consultants, testers and trainers. Sandbox Data Masker replaces it with consistent fictional values from a field map you control. It runs only in sandbox environments, works through the data in the background and never logs the original values.

Sandbox Data Masker illustration. Sandbox · copy of production. Before: Real customer names and bank accounts. After: 18,400 records masked · nothing logged. — Sandbox · copy of production. Before: Real customer names and bank accounts. After: 18,400 records masked · nothing logged. An illustration, not a Business Central screen.

What it does

Sandbox only: Refuses to run in a production environment.
Field map: Choose a masking method per field: fake name, company, address, e-mail, phone, blank, fixed text or hash, seeded from the fields' data classification.
The usual suspects: Customers, vendors, contacts, employees, bank accounts, ship-to and order addresses, salespeople and resources, and optionally posted documents.
Background runs: Masks in chunks from the job queue, with a run log of tables, records and duration, and an option to run on the first open after a copy.

What it does

Get Sandbox Data Masker when it launches