Unable to Migrate to New Fabric Tenant Due to Power BI Gateway Single-Tenant Limitation

[DeepthiSaranya]

Problem statement:

The current migration is blocked due to a critical technical constraint.The existing production PowerBI reports are hosted in the old tenant, as the source database resides under the same account.These production reports rely on a single on-premises PowerBI gateway to fetch data from the database.

Due to a gateway and tenant limitation, the same gateway cannot simultaneously serve two different tenants. As a result, migrating data or reporting workloads to the new Fabric environment would break the existing production PowerBI reports. This creates a high risk of production disruption and prevents from proceeding with the migration.

Expectation : We need to connect the database in the new Fabric tenant for migrating the data using the sql credentials without the blocker

[v-sshirivolu]

Hi @DeepthiSaranya ,
I would also take a moment to thank @shreya_mandloi , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions

[v-sshirivolu]

Hi @DeepthiSaranya ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[lbendlin]

Most likely your data sources will move to the new tenant as well.

"migration"  is a myth.  In the real world you recreate your setup in the new tenant, and then at some point communicate the new URLs to your users.

[shreya_mandloi · Accepted solution]

Power BI gateways are both machine-bound and tenant-bound, so Microsoft doesn’t support running two Enterprise gateways on the same Windows machine. Have you considered a second VM, if not maybe you can try doing as below.
For zero-downtime migration, you could spin up a small second VM and install a gateway there for the new tenant.
Both gateways can point to the same SQL database — old production keeps running, and the new Fabric tenant can migrate and test. Once you cut over, the old VM can be removed, so the extra cost is only temporary.