How many Dataverse environments is too many for a 200 maker org?

Question

We're at 340 Power Apps signed in over the last quarter and I count 60 something Dataverse environments, half of them default or personal dev environments nobody cleaned up. The CoE toolkit is flagging duplicate table names across environments and I can't tell which one is actually in use anymore. I'm looking at collapsing down to a hub and spoke model with maybe 8 environments total, but I'm worried about breaking existing connections in the process. Has anyone done a real environment consolidation on Power Platform without a big outage window?

Marcus T. · Accepted Answer

Did this at a previous job, went from about 90 environments down to 12. Inventory every environment with the admin center export first, then use the CoE toolkit's app and flow inventory to see what's actually got users in the last 90 days, anything with zero usage gets archived rather than migrated. The connections are the painful part, we rebuilt them manually in the target environment instead of trying to move connection references, took two weekends but no outage during business hours.

Ben L. · Answer

We did something similar but kept a handful of the old environments alive read only for a few months just for reporting. Some of our Power BI datasets were pointed at tables in environments we wanted to retire and we didn't find that out until after the first cutover attempt. Worth checking dataflows and Power BI connections before you touch anything, not just apps and flows.