OneLake/Fabric and enevironment separation

How do you separate dev, test and prod data in OneLake? So far we have had separate Azure subscriptions and separate databases ans lakes for each, but you can only have one OneLake per tenant...

We are under strict regulation, and must have low level segregation of duties and environments and it must not be possible to access both test and production by the same person or from the same workstation. Multiple tenants is not tempting...