Generate and manage fake data in M365 for mockups, demos, or technical testing.
[Post updated on January 23rd]As a Solution Engineer, I never demo or validate a solution in production, and I shouldn’t. MS Dev tenants are the standard: isolated, safe, and disposable.On paper, they’re ideal: all M365 services are provisioned, licensed, and ready.In reality, they’re empty shells. Blank mailboxes. Empty SharePoint sites. Silent Teams. No data, no history, no behavior. And without behavior, I can’t properly demonstrate, test, or stress a solution.That’s the real issue: I don’t need just a tenant, I need a living environment. One that reflects real-world structures, volumes, permissions, and inconsistencies. Without that, demos feel artificial, performance tests are misleading, and edge cases only appear in production.I started by building scripts to automate content creation in M365. It worked, up to a point.As soon as I needed randomness in the assets, multiple item types, and all their specific behaviors, the setup became increasingly hard to manage. Too many scripts
